Verification in progress
No envelope content is presented as verified until all eight digests and the response anchor match.
Product proof room · current public reference
The proof should survive without the pitch.
ControlFrame sits between regulated systems and the audit room. This surface lets a buyer or investor verify the public orchestration record, inspect the product chain, and see exactly where production activation remains gated.
Synthetic reference · private runner not activated · no customer evidence
Recomputing eight envelopes
Chain-of-Proof dossier
Eight archival envelopes expose the ordered custody record. Select a sheet to inspect what entered, what left, and which digest binds it to the chain.
controlframe.reference-orchestration.v1Interactive proof command · browser memory only
Challenge the selected envelope
Alter one displayed output, watch every dependent digest fail closed, then restore the untouched server reference. No write request or server mutation is made.
- Selected envelope
- 01Reference replay opened
Fetching the GET-only reference trace and recomputing its ordered digest chain locally.
01 · One product story
Five surfaces. One governed chain of record.
The demo advances only when each surface adds a different piece of evidence. No duplicated dashboard tour, and no claim that a public replay is a customer run.- 01Inspect governed orchestrationDeclareShipped contract
Scope, source, target, expected proof, freshness, tool boundary, and review policy exist before execution begins.
- 02Inspect the scripted replayExecuteScripted reference replay
A deterministic, truth-labeled playback shows navigation, control-bound assertions, reference capture hashes, and the boundary to a verifiable package.
- 03Trace evidence lineageConnectGoverned evidence graph
Source authority, artifact bytes, validation, mapping candidates, reviewer decisions, and package state stay joined.
- 04Break the evidenceVerifyBuyer-controlled proof
The recipient can re-derive covered hashes and check the supplied Ed25519 proof without a ControlFrame account or callback.
- 05Model the business caseMeasurePilot hypothesis
Adjustable assumptions become an observed baseline only after a scoped pilot measures one evidence lane end to end.
02 · Capability ledger
Shipped, demonstrable, and gated are different states.
Strong diligence starts by separating repository implementation from public proof and production activation.Agentic evidence workflow
ImplementedTyped role contracts, ordered workflow events, persisted run records, and bounded authority.
Private-runner custody
Implemented · activation gatedSigned dispatch, token registry, project scope, failure provenance, and create-once recording paths exist; production enrollment still needs private-network proof.
Review-gated package release
ImplementedSource coverage, freshness, redaction, separation of duties, and human authorization are recomputed before release.
Independent verification
Publicly demonstrableA downloadable bundle and self-contained verifier let a recipient re-check integrity outside the product session.
Enterprise tenant boundary
Diligence openOrganization and project scope exist; production activation remains contingent on evidenced identity, isolation, administration, and key-custody controls.
03 · Defensibility architecture
The moat is the decision trail, not the animation.
The visual layer explains the system. Defensibility grows from connected operational records and customer-authorized evidence decisions that are expensive to recreate.01
The operating graph
Obligation, execution, artifact, mapping, challenge, decision, and release are one versioned record instead of disconnected workflow output.
02
Portable provenance
The evidence package carries its own custody and verification material, reducing dependence on a dashboard as the trust boundary.
03
Decision data
Every accepted, rejected, or conditioned evidence decision can become a proprietary feedback asset once customer-authorized pilots begin.
04
Reuse with memory
Native authority is preserved while reuse stays advisory, allowing accepted mappings and invalidations to compound without pretending frameworks are equivalent.
04 · Claim discipline
Confidence comes from naming the boundary.
Claims safe today
Current- Agentic audit evidence workflow
- Private-runner evidence architecture
- Source-backed CMS EDE evidence coordination
- Review-gated package release controls
- Hash-backed artifact and access-log custody controls
- Controlled pilot and executive proof system for regulated evidence operations
Claims not made yet
Gated- CMS approval, auditor approval, or regulator endorsement
- SOC 2 complete, HITRUST certified, HIPAA certified, or third-party certification
- Guaranteed audit pass, zero-touch compliance, or fully autonomous approval
- Full enterprise production readiness before tenant, identity, network, and key controls are evidenced
- Proprietary deployed weights before model lineage, evaluations, and runtime approval
05 · Next diligence proof
Move one evidence lane from reference to authenticated.
The next material rating increase comes from deployment evidence, not another promise.Private execution boundary
Enroll an approved runner inside the authorized network boundary, bind scoped UAT identities, and retain an authenticated persistence smoke.
Enterprise trust plane
Evidence durable access administration, tenant isolation, identity lifecycle, least-privilege runtime, and managed key custody together.
Real diligence package
Run one authorized audit lane and package its execution, evidence, review, release, security, and measured baseline for investor and buyer review.