Tenant Isolation Review with Claude Code: Result JSON Schema

A production playbook for tenant isolation review in cross-industry operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.

Audience: B2B SaaS security teams

The problem

B2B SaaS security teams need tenant isolation review to run repeatedly against tenant IDs, storage paths, logs, credentials, and auth checks. In cross-industry operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.

Implementation path

Define the outer result contract once, let the tenant isolation review skill own body.data, and reject terminal output that does not match the expected schema.

Tradeoffs and failure modes

Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For tenant isolation review, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.

Result shape

{
  "schema_version": "argo.result.v1",
  "summary": "tenant isolation review completed",
  "body": { "type": "tenant_isolation_review", "data": {}, "exceptions": [] },
  "artifacts": []
}

Run this on Argo