v2 Beta / Documents and provenance
Keep the history with the exact copy.
Preserve a document’s edition, release history and digital custody. Follow a citation to the copy it describes, with missing information still visible.
Each edition keeps its own dates, citations and custody history. All documents, people and identifiers in the example below are fictional.
Fictional worked example
One title. Two distinct editions.
Both files are titled Memo A. Their pages, release details and custody histories belong to the specific copy they describe.
A citation stays with its edition
SYNTHETIC passage with redactions.
Edition A, page 2
Attributed to Synthetic memo; extracted by Synthetic curator.
Custody declarations
Declared status: partial. List position alone does not establish chronology.
collection
Unknown → Fictional Archive A
Date: Unknown · Predecessor: Earlier digital custody was not supplied.
storage
Fictional Archive A → Fictional Repository A
Date: Unknown · Predecessor: receive-a
Unavailable original
Original file named by the archive; bytes unavailable.
MD5: 00000000000000000000000000000000
This declared legacy hash has not been verified against either edition.
Identifier checks
Fictional Archive · SYN-17
Recorded access result: accessible
2026-09-10 · Fictional catalog checker
A fictional historical access check. No live URL check or identity match is claimed.
Attributed interpretation
The comparison has a named reviewer.
Different bytes and pagination are declared. This does not establish faithful reproduction or authenticity.
Review outcome: inconclusive · Synthetic reviewer
- Edition A, page 2
- Edition B, page 3
From a source file to an attributable review.
- 01
Identify the edition
Declare the artifact and its SHA-256 in the observation inventory. Give each edition its own identity, metadata and document events.
- 02
Preserve its history
Record digital custody actions, explicit predecessors and unknown gaps. Keep original-file hashes and derived files distinct.
- 03
Cite and review
Bind a citation to the entity snapshot, edition, artifact and locator. Name the reviewer, method and inputs behind an interpretation.
The archival evaluator checks supplied document snapshots and reference consistency. Source artifact integrity, scientific interpretation and profile applicability remain unchecked. The example does not fetch URLs or authenticate source files. Download the example and run it locally using the guide above.
The published document-provenance workflow separately checks release citations and supplied source bytes. Physical sample custody belongs to the material workflow. Public names, URLs and free text must already be approved for publication.
Inside the standard
Explore the structure.
Open a field to see its shape, alternatives and constraints. Required means required within its containing object or selected alternative. A required list can still be empty unless a minimum is specified.
16 top-level fields. Nested fields are included in search.
Editions, artifacts and custody
Sourced edition metadata, document events, digital custody actions and scoped identifier checks.
Implementation guide →Document fields
Published contract and schema export
Fields and constraints above come from the published 2.0.0-beta.3 package. Explanations and grouping are editorial. JSON Schema describes structure; the implementation guide explains semantic and profile checks.
urn:disclosureos:experimental:research-entities:0.2.0
@disclosureos/records/experimental/v2/entities/schema/0.2.0
The schema URN identifies the contract. Read the JSON through the package export above.
Citations and attributable reviews
Cite one exact edition and preserve the reviewer, method and inputs behind an interpretation.
Implementation guide →Document fields
Published contract and schema export
Fields and constraints above come from the published 2.0.0-beta.3 package. Explanations and grouping are editorial. JSON Schema describes structure; the implementation guide explains semantic and profile checks.
urn:disclosureos:experimental:claim-history:0.4.0
@disclosureos/records/experimental/v2/claims/schema/0.4.0
The schema URN identifies the contract. Read the JSON through the package export above.
Trace the released source.
The release-provenance workflow separately checks selected public sources, release citations and supplied source bytes. It uses its own document contracts. Neither check authenticates a release or establishes redistribution rights.
Inside the standard
Explore the structure.
Open a field to see its shape, alternatives and constraints. Required means required within its containing object or selected alternative. A required list can still be empty unless a minimum is specified.
6 top-level fields. Nested fields are included in search.
Document selection
Identify document sources and their declared release context.
Implementation guide →Document identity and scope
Selected material
Published contract and schema export
Fields and constraints above come from the published 2.0.0-beta.3 package. Explanations and grouping are editorial. JSON Schema describes structure; the implementation guide explains semantic and profile checks.
urn:disclosureos:experimental:released-document-selection:0.1.0
@disclosureos/schema/experimental/v2/released-documents/schema
The schema URN identifies the contract. Read the JSON through the package export above.
Research workflows
Follow the source.
Work with an instrument capture, recorded account, released document or collected specimen. Each has a distinct path through the standard.
These beta workflows cover specific provenance checks. Detailed descriptive and forensic coverage is still being completed.
Example source commit: 6fd1fc8e87dfc8676e4c3f1eb36fd6884c81e370. The example presents sourced declarations; it does not calculate authenticity or complete custody.