DisclosureOS documentation · v2 Beta
Check sources and custody
Check synthetic documents, testimony and physical-sample records with the published beta.
Download the examples. The archive contains three complete workflows, each with a claim history, a selection and a small source file. All people, institutions, specimens and events are fictional. No ELDÆON data is included.
Run locally
Unzip the archive and open the provenance folder. With Node.js 22 or newer:
npm install --ignore-scripts
npm startOr run one workflow:
npm run documents
npm run testimony
npm run physical-samplesThe runner imports the published 2.0.0-beta.4 evaluators. It supplies actual local bytes and prints each result's checks and every explicit interpretation limit. No source URL is fetched by an evaluator.
Expected results and their meaning
All three examples return success: true with these checks:
{
"structural": "passed",
"semantic": "passed",
"profile": "passed",
"external": "passed"
}For these profiles, external means selected source-file integrity. A pass says the supplied bytes match their declared digests. It does not authenticate a release, speaker, custody transfer or specimen. Every named interpretation limit printed by the runner remains not_checked, including scientificEligibility, assessmentSupport and redistributionRights.
This differs from the standalone claim-history parser, whose profile and external checks remain unrun, and from the instrument-binding example's external status. Read the scope of the evaluator, not just the word “passed.”
Follow each example
| Workflow | Documents and source | What the example demonstrates |
|---|---|---|
| Documents | History, selection, text | A declared public document release and a directly extracted source statement. |
| Testimony | History, selection, account | Distinct recorder, extractor and pseudonymous speaker labels, with unknown event context. |
| Physical samples | History, selection, custody record | A fictional collector-to-store handoff and a cited record whose bytes match its digest. |
The testimony and specimen histories deliberately contain restricted source labels to test preservation of access declarations. The fixtures themselves are public MIT-licensed examples. A real evaluator result retains the supplied history and selection; it is not a redacted publication view.
Try missing or contradictory information
Run either exercise from the extracted folder:
npm run documents -- --missing
npm run documents -- --changed--missing supplies no source bytes. The profile and external checks remain not_checked. --changed alters one byte in memory; those checks become failed because the bytes no longer match their declared digest. Both return success: false, print diagnostics and exit with status 1. Structural and semantic checks still pass.
Use the same flags with npm run testimony or npm run physical-samples. The exercises never change the saved fixtures. Run npm start again to confirm that the originals still pass.
These examples show successful checks within bounded scopes. They do not imply complete transcription, a full witness model, full archival metadata or a laboratory-quality specimen record. The workflow guides state the remaining coverage explicitly.
Source and next steps
The example histories, selections and source files are copied unchanged from the canonical released-document, historical-testimony and physical-sample examples. The archive includes their MIT license and the portal's runner.
Continue with Claims, Witnesses and accounts, Documents and custody or Materials and laboratory. For measured data, use the separate instrument example.