Core concepts
OCP works by keeping states that are often blurred together—source, observation, inference, acceptance, permission, and preservation—separate and inspectable.
Four related views
| View | Carries | Does not imply |
|---|---|---|
| Context | Reviewed statements and preferences | Universal truth or action authority |
| Evidence | Supporting or challenging source records | Acceptance |
| Artifacts | Logical objects and byte representations | Rights or provenance by possession |
| Conversations | Message graphs and content parts | Endorsement of embedded instructions |
Candidate, accepted, disputed, withdrawn
A context_item carries review and lifecycle state. Imported or inferred material starts as candidate. Acceptance is scoped to a context space and requires a decision record. Later evidence can dispute, supersede, or withdraw an item without rewriting history.
References carry revision and integrity
Normative references use an identifier, revision, schema URI, and—where required—a digest. This makes stale or substituted data detectable and allows the same logical object to evolve through explicit revisions.
Provenance is not preservation
- Source authority
- The provider or system that is authoritative for the source record’s original meaning.
- Runtime source
- The software and execution context that produced the current OCP representation.
- Custody
- Who holds a representation, whether it depends on the source, and whether its bytes are independently retrievable.
- Lineage
- Declared transformation and derivation events. Lineage does not itself prove correctness.
Was this page useful?
Feedback is stored in this browser only until a project feedback endpoint is adopted.
Thank you. Your note was saved locally and has not been transmitted.