Loop-state legend
Visible state language for reviewer consoleInteractive flow map
scenario selection changes node statesADAPTIVE
SUBSTRATE
Layer responsibilities
each layer keeps its job| Layer | Job | Boundary |
|---|---|---|
| PDF / Adobe-style workflow | Document/media body, creation, edit, export, display context. | Does not by itself settle interpretation. |
| C2PA / Content Credentials | Provenance and content-history signal. | Credential is not unlimited claim validity. |
| Trace Capsule | Carries source, boundary, uncertainty, claim scope, consent/scope, return path. | Bounded interpretation, not ownership. |
| OAM Pressure Engine | Flags overclaim, source loss, authority blockage, false closure, outsourced judgment. | Pressure read, not final authority. |
| Open verification logic | Reproducible local review posture outside closed authority boxes. | Not production forensics in this static demo. |
| Digital Mycelium | Routes strain into repair, grit update, life-first/source-return conditions. | Structural correspondence, not biological life claim. |
What this does not claim
non-claim lockThis simulator does not replace C2PA, Content Credentials, Adobe tools, PDF standards, Linux verification systems, cybersecurity review, journalism, law, science, or human judgment.
It does not prove document truth. It does not certify authenticity. It does not execute uploaded PDF content. It does not claim endorsement, adoption, affiliation, production readiness, or standards-body approval.
Reviewer questions
Where does provenance degrade after it becomes visible? Where does interpretation overclaim the credential? Where does authority block repair? What should be encapsulated instead of forced into output? What can close only for current scope?
Deeper theory note
The substrate is not hardened into brittleness. It preserves invariants while allowing pressure-state movement: HELD, STRAINED, ENCAPSULATED, REPAIRING, REOPENED, FALSE CLOSURE RISK, CLOSED FOR CURRENT SCOPE, or MUST STOP.