Submission, validation, review, approval, publishing, and monitoring each had different evidence and authority requirements.
From a watched queue to a compiled control system.
This worked example shows the Marketplace template lifecycle from submission through monitoring. It uses representative local fixtures and a shadow-only compiler: no production writes, approvals, rejections, publishing, or credential changes.
- Status Prototype
- Mode Shadow only
- Cases 5 replayed
- Writes None
Operational change
The result is not more activity. It is less reconstruction.
The prototype turns a known operating path into explicit contracts and replayable decisions. These are prototype measurements, not customer ROI claims.
A missing approval, unsupported claim, or unknown action could not safely inherit authority from the surrounding process.
The compiler validates the boundary, generates linked operating artifacts, replays representative cases, and fails closed.
System path
Describe. Map. Compile. Simulate. Pilot.
Each stage narrows uncertainty without silently expanding authority. Operate begins only after a separate live-runtime, approval, rollback, and retention decision.
Name objects, events, states, owners, evidence requirements, and runtime targets.
Atlas-shaped contracts show which work can pass, wait for approval, or stop.
Produce schemas, tool and agent contracts, approval surfaces, evals, receipts, and a read-only console.
Exercise passing, approval-required, blocked, insufficient-evidence, and unknown-action outcomes.
The current prototype stops before deployment, external writes, approvals, publishing, or credential changes.
Compiled package
The map produces artifacts for all three tiers.
The package points to the existing systems that own live state and execution. It does not replace submission, validation, review, Policy OS, Substrate, or Atlas.
Compiled workflow, object and event schemas, workflow map, evidence ledger, and content-hashed manifest.
Runtime inventory, tool and agent contracts, transition replay, evaluation manifest, and operator console.
Decision inventory, autonomy classes, approval surfaces, insufficient-evidence handling, and unknown-action refusal.
Acceptance receipt
The same input produced the same governed bundle twice.
The verifier compiles from clean directories, compares every generated file byte for byte, checks content hashes, and requires explicit outcome coverage.
15
Content-hashed generated artifacts
5
Representative workflow cases
3
Pass, approval-required, and blocked outcome classes
2×
Clean compilations compared byte for byte
CRE-1191 · workflow compiler ok: true · deterministic: true
Pass: 1 · Approval required: 1 · Blocked: 3 · Governance complete: true
Representative fixture evidence. No client outcome or production execution is claimed.Apply the method
Bring the handoff your team still watches by hand.
Atlas can map the systems, owners, decisions, failure points, and proof requirements first. A pilot follows only when the controlled lane is clear enough to test.
- Owner
- Workflow owner
- Authority
- Separate pilot approval
- Proof
- Map + compiled candidate + replay plan
- State
- review