Problem
#8136's residual gap: hosted ORB reviewing private customer repos cannot publish its corpus for third-party re-runs — that is the case attestation eventually covers. But there is a nearer-term bridge the threat model already endorses: the tenant themselves can hold their own corpus. Reproducibility-for-the-affected-party — a tenant downloads the checksummed corpus slice built from their own repos and re-runs any comparison locally with the public engine — restores the "don't take our word for it" property for exactly the party who needs it, before (and independent of) TEE infrastructure.
Requirements
- Design + implement a per-tenant corpus export: same manifest/checksum shape as
scripts/backtest-corpus-export.ts produces, hard-scoped to the tenant's own repositories — a tenant can never receive another tenant's rows, enforced at the query layer and covered by tests.
- Delivery mechanism fits the hosted control plane (authenticated endpoint or signed artifact download — decide within Cloud Readiness's existing auth patterns; record the decision here).
- The persisted backtest runs a tenant's export corresponds to must be identifiable (corpus checksum matching), so "re-run comparison N against my own history" is a documented, complete procedure.
- Tenant-facing docs section (can live with
/docs/verify-this-review or a hosted-docs sibling) walking the full re-run.
Deliverables
Links & Resources
Boundaries
Read/export only — no gating changes. Raw corpus content goes to its owning tenant exclusively; public surfaces continue to receive aggregates and checksums only.
maintainer-only — tenancy and data-isolation authority.
Problem
#8136's residual gap: hosted ORB reviewing private customer repos cannot publish its corpus for third-party re-runs — that is the case attestation eventually covers. But there is a nearer-term bridge the threat model already endorses: the tenant themselves can hold their own corpus. Reproducibility-for-the-affected-party — a tenant downloads the checksummed corpus slice built from their own repos and re-runs any comparison locally with the public engine — restores the "don't take our word for it" property for exactly the party who needs it, before (and independent of) TEE infrastructure.
Requirements
scripts/backtest-corpus-export.tsproduces, hard-scoped to the tenant's own repositories — a tenant can never receive another tenant's rows, enforced at the query layer and covered by tests./docs/verify-this-reviewor a hosted-docs sibling) walking the full re-run.Deliverables
Links & Resources
scripts/backtest-corpus-export.ts/scripts/backtest-corpus-export-core.ts(the manifest shape to reuse)Boundaries
Read/export only — no gating changes. Raw corpus content goes to its owning tenant exclusively; public surfaces continue to receive aggregates and checksums only.
maintainer-only — tenancy and data-isolation authority.