ControlFrame
Executable evidence assurance infrastructure

See every compliance claim move through custody.

ControlFrame joins source obligations, evidence contracts, custody, review, and release authority. This public instrument verifies one CMS synthetic reference identity; PCI and HITRUST remain explicitly unexecuted candidates.

Inspect the Custody Twin Verify the CMS trace

Synthetic reference · private runner not activated · no customer evidence · zero automated releases

Reference custody section3c1d6f3a797a…
Stages 01–03Authority
  1. 01Authority
  2. 02Contract
  3. 03Warrant
Stages 04–06Custody
  1. 04Boundary
  2. 05Artifact
  3. 06Validation
Stages 07–09Decision
  1. 07Mappings
  2. 08Review
  3. 09Release

Nine declared stages are grouped here. Inspect all eight dependency edges below; stage 09 remains held for human release.

Interactive reference instrument

One obligation. Every consequence.

Inspect the executed CMS Y9 UI-3.2 synthetic reference, revise its source, and watch ControlFrame traverse declared dependency edges to hold reachable claims. PCI and HITRUST remain unexecuted, source-cited candidate lanes—not copied traces.

Custody Twincontrolframe.assurance-graph.v1
Browser recomputing
Declared edges encode dependency Release authority stays human
05

Bounded runtime

Governed evidence object

The executed reference trace records artifact metadata in an ordered SHA-256 event chain.

State
captured
Artifact ID
EV-2048
Provenance
Synthetic CMS reference · trace-event envelope
Observation
Synthetic reference · bounded enrollment consent-flow replay
Trace event digest
8938236a27aeab9dce9292f593db94385fd36f57a590fb4997520dc2653dfbec
Truth boundary

The artifact shown here is synthetic reference data, not customer evidence.

Challenge the executed CMS reference

Change the executed CMS reference obligation in memory. The browser should reject the altered graph and derive affected states from reachable dependency edges.

Published graph anchor3c1d6f3a797abb20ea9537897a4fa868ea1229e238b94a53ebe54bff3e60c685
Observed graph digestRecomputing…
  • Contract: pending
  • Graph digest: pending
  • Compiled anchor: pending
  • CMS trace anchor: pending
  • CMS trace identity: pending
  • Human-held release: pending

Executed CMS reference projection

CMS enrollment consent assurance

Can the CMS Y9 UI-3.2 synthetic consent-flow reference be traced from declared scope to a human-held package?

Synthetic UI-3.2 workflow evidence + three sidecarsEV-2048
CMS EDE reference fixturenative

UI-3.2 · CF-UI-03

The displayed scenario, control, and evidence identifiers match the executed synthetic reference trace; this is not a CMS assessment result.

Native scope preservedCMS Enhanced Direct Enrollment
HITRUST CSFmedium candidate

Access-control candidate family

Exact HITRUST version, requirement statement, healthcare scope, and assessor criteria require validation against licensed catalog content.

Human decision requiredHITRUST Framework
PCI DSSmedium candidate

8.3.1

CDE scope, authentication method, frequency, and sampling must be reassessed.

Human decision requiredPCI SSC document library
SOC 2high candidate

CC6.1

System boundary and operating-period evidence require auditor confirmation.

Human decision requiredAICPA Trust Services Criteria

Only the CMS Y9 UI-3.2 / CF-UI-03 / EV-2048 lane is bound to the published 8-event reference trace. PCI and HITRUST remain unexecuted, source-cited candidates requiring qualified human approval. For the CMS revision exercise, affected states come only from nodes reachable through declared invalidation edges; the proof room independently verifies that CMS reference trace.

What compounds

The graph is not a picture of the product. It is the product.

Framework catalogs and AI assistants will commoditize. The harder asset is a living record of what was authorized, what actually ran, what proof survived challenge, and what an assessor ultimately accepted.

01

Assurance Compiler

Turns cited obligations into versioned evidence contracts: scope, acceptance criteria, authorized collection, freshness, redaction, and review policy.

02

Private Assurance Runtime

Is designed to execute scoped jobs where customer credentials and sensitive systems live; the public reference does not activate that runtime.

03

Custody Twin

Keeps obligation, execution, artifact, validation, mapping, challenge, decision, and release joined as one dependency graph.

04

Portable Evidence Passport

Carries hashes, authority, observation window, reviewer disposition, expiry, and independent verification outside the dashboard.

Why this is different

Compliance software records answers. ControlFrame preserves how the answer became defensible.

Version the obligation

In this reference graph, a source change traverses declared invalidation edges and marks only reachable stages affected.

Verify the CMS reference

The visitor's browser recomputes the graph digest and confirms that its scenario, control, and evidence identity matches the published CMS reference trace.

Preserve accountable authority

Agents propose and challenge. A human owns acceptance and package release.

Production activation path

Turn the reference instrument into your controlled evidence lane.

The public experience demonstrates a deterministic CMS reference graph, semantic trace-identity checks, edge-derived source-change impact, and a human-held release state. A paid pilot must separately establish private execution, durable custody, and assessor acceptance for an authorized enterprise workflow.

Compare deployment models
01
Open activation gate

Private-network execution

Enroll an approved runner inside the authorized network and retain an authenticated persistence smoke.

02
Open activation gate

Managed signing identity

Pin a durable customer or KMS-backed signing key with rotation, revocation, and independent custody evidence.

03
Open activation gate

Assessor acceptance loop

Capture a real, authorized accept/reject/remediate cycle without relabeling synthetic reference data.

Executable Assurance Graph | ControlFrame