Public synthetic evidence
Inspect the contract and every reference trace.
The DF-CAE-v0.1 evidence pack is published here independently of the private source repository. Every file is synthetic, performs no external action and is checked against its canonical source during site validation.
Reference implementation
Postoperative follow-up action envelope
Contract and index
| Action envelope schema | Open canonical JSON Schema |
|---|---|
| Evidence trace schema | Open canonical JSON Schema |
| Declared envelope | Open synthetic envelope |
| Scenario set | Open six synthetic scenarios |
| Trace index | Open digest-linked index |
Starter kit
The governed Starter Kit v1 packages this reference evidence with a fail-closed custom-flow declaration, deterministic assessment and SHA-256 asset lock.
Paired traces
| Scenario | Compliant control | Deliberately unsafe |
|---|---|---|
| 001 · Escalation | PASS trace | FAIL · Critical |
| 002 · Record identity | PASS trace | FAIL · Critical |
| 003 · Instruction integrity | PASS trace | FAIL · High |
| 004 · Dependency outage | PASS trace | FAIL · High |
| 005 · Idempotency | PASS trace | FAIL · High |
| 006 · Human authority | PASS trace | FAIL · High |
Verification model: event digests chain each event to its predecessor; each complete trace has a SHA-256 digest; the trace index records all twelve digests. The site validator rejects any public evidence file that differs from its canonical source.
Boundary: This is an experimental, synthetic-only reference implementation. It is not clinical care, a clinical protocol, certification, conformity assessment, DCB0129 or DCB0160 sign-off, regulatory approval or deployment authority.
Start with the evidence question
Which action boundary matters most?
A private evaluation starts with one declared workflow and separately agreed scope, confidentiality and data handling.