ControlFrame
ControlFrame guided tour

Trace one obligation from source requirement to controlled release.

A working reference flow through private collection, artifact custody, GRC mappings, human review, and package release. The data and collection are scripted; the governed operating model is the product.

Start the tourReview platform architecture
Live reference workbench

Inspect the full evidence operating chain.

Switch between the four product stages. In collection, run the deterministic reference job. In the repository, select an artifact to inspect its metadata and custody record.

Evidence operations workbench
CMS EDE reference program · sandbox data
Sandbox runner readyus-east-1
Scripted CMS EDE collection plan

Collect evidence where the source lives.

The sandbox plan binds CMS Y9 · UI-3.2 to the expected workflow proof, artifact contract, control mapping, and custody requirements before work begins.

Swipe horizontally to inspect the complete collection plan.
SourceEvidence taskOutputControlState
CMS source catalogY9 · UI-3.2 enrollment consent flowSource row + contractCF-UI-03ready
Enrollment applicationConsent capture and confirmation pathScreenshot + sidecarCF-UI-03ready
Enrollment APIConsent event and transaction recordJSON + headersCF-AU-11ready
Document repositoryApproved consent and privacy noticePDF + metadataCF-GV-02ready
Signed jobs
—
Artifacts captured
—
Raw data boundary
Sandbox reference
Reference implementation — no production customer data is shown.plan → collect → review → release
The operating model

One proof spine. Five governed stages.

  1. 01

    Collect at the source

    Signed private-runner jobs capture browser, API, configuration, log, and document evidence against a declared evidence contract.

  2. 02

    Govern the repository

    Artifacts retain source, version, checksum, sensitivity, freshness, custody history, and reviewer state.

  3. 03

    Map the control graph

    One source artifact can support multiple framework projections without hiding the original obligation or reuse confidence.

  4. 04

    Hold for human review

    Agents can recommend sufficiency and redaction actions. They cannot approve their own work or release an audit package.

  5. 05

    Release defensible proof

    Approved artifacts, manifests, decisions, and custody records become a controlled package with an offline-verifiable receipt.

Governed agent strategy

Agentic review with human authority

Framework-configured agents can plan evidence work, inspect sufficiency, identify sensitive data, and draft the next review action. Customer policy determines the model boundary; agents do not approve their own output or release packages.

Framework-configured evidence planning and sufficiency review
Customer-controlled or approved inference boundaries when policy requires
Model and tool lineage, evals, custody logs, and human approval gates
Protected product workspace

Bring your own framework, sources, and review authority.

Invited teams can continue into a protected workspace with real project scope, access controls, runner configuration, and review gates.

Verify project access