Inspect the system behind the product
Start with the architecture, then examine the private-runner boundary, tenant isolation mechanism, AI governance posture, framework provenance, and independent verification path.
System architecture
Trace specialist roles, orchestration, evidence collection, persistence, review, and package release as one governed system.
Inspect the architecturePrivate runner boundary
See what crosses the customer boundary, what stays local, which controls operate today, and which activation evidence remains required.
Review the runner boundaryTenant isolation
Review the row-level security design, runtime role constraints, exception ledger, and production verification method.
Inspect tenant isolationResponsible AI
Review prompt provenance, model and tool tracing, evidence restrictions, and the human decision boundary.
Review AI governanceFramework provenance
Inspect current releases, source artifacts, parsed catalog units, and the boundary before project activation.
Open the catalog observatoryOffline verification
Recompute covered hashes and check supplied Ed25519 signatures locally without a ControlFrame callback.
Verify the reference bundleChangelog
Dated release notes: what shipped, when it landed on the main branch, and the pull request behind each change.
Review release history