What is proven—and what is not
The 0.4 release package is internally consistent and publication-ready as an editor’s working draft. It is not yet an adopted standard or independent interoperability result.
Verified locally
| Layer | Result |
|---|---|
| Schemas catalogued and compiled | 37 / 37 |
| Positive examples valid | 32 / 32 |
| Negative examples rejected at intended rule | 45 / 45 |
| Semantic reference vectors | 243 / 243 |
| Registry, OpenAPI, and evidence gates | 29 / 29 |
| Portable AI History cases | 25 / 25 |
| Assertions with exactly one result row | 134 / 134 |
| Assertions passed against an identified implementation | 0 |
Publication gates
- Complete public deployment and live readback for the
https://opencontinuity.orgnamespace. - Adopt specification and code licenses, contribution/IPR terms, neutral governance, and vulnerability response.
- Complete public review, resolve material issues, and reproduce the release on the pinned toolchain.
- Publish immutable release members, digests, and the public hostile corpus.
Implementation and interoperability gates
- Identify two independent provider adapters, two independent OCP providers, and one independent client.
- Run real, non-personal provider exports through quarantine and declared mapping.
- Demonstrate cross-provider transfer, re-export, semantic graph comparison, and explicit loss handling.
- Demonstrate managed-byte retrievability, re-verification, source loss, changed identifiers/URLs, and recovery.
- Achieve matching graph, custody, mapping, loss, and comparator results across independent languages and codebases.
Security gates
- Exercise hostile archives and portable content against deployed isolated parsers and application control boundaries.
- Complete independent threat and security review for all three Portable AI History profile families.
- Register and test remote and offline authenticity, confidentiality, recipient, and client-instance binding profiles.
- Exercise credential, network denial, resource-limit, supply-chain, recovery, and external-action boundaries in real deployments.
Was this page useful?
Your response is emailed to the Open Continuity maintainers. No account or email address is required.
Thank you. Your feedback was sent to the maintainers.