DisclosureOS documentation · v2 Beta
Build with DisclosureOS
Create research records that other people can inspect, exchange and build on.
DisclosureOS defines how to describe an observation, connect its source material and keep attributed reviews alongside it. You work with JSON documents and validation tools. Your application chooses how to store the files and display the results.
Start with one record
Create a small observation, run the validator and read its response. You will learn how to represent missing information and what a successful check means before adding instruments or reviews.
Node.js 22 · JavaScript · One package · No account or hosted service
To try a check without installing, open the Document inspector with a fictional example. Your input stays in your browser.
Start from the working viewer
Run the fictional example case locally. Inspect a recording, follow it to a source file, then see how the viewer uses the standard.
Bring your own data
Prepare a small, representative sample from your dataset. Identify its sources, collection details and missing information before mapping it to records.
How the pieces fit
Start with an observation: a record of an event and the sources that describe it. Keep the original files in their native formats. The record identifies those files and connects measurements to their sources. A viewer, archive or analysis tool can use those relationships.
Recordings, accounts, documents and laboratory files.
Source references, measured values and explicit gaps.
A reviewer, a method, supporting inputs and an outcome.
Add only the parts your work needs. These are related parts of the standard, not six required setup steps. A witness account does not need an instrument, and an observation does not need an origin hypothesis or score.
- Records cover observations and their supporting accounts, documents, setting and samples.
- Instruments connect readings to equipment and capture conditions.
- Observables provide terms for characteristics reported or investigated.
- Claims keep interpretations tied to a reviewer, subject and supporting material.
- Origins provide terms for possible explanations.
- Scoring records checks and attributed scores under declared methods.
The standard overview explains these concepts through interactive examples. The guides here cover their implementation.
Find the detail you need
Use a guide to assemble documents and run checks. Use a field reference to look up exact fields, alternatives and constraints. Search includes nested fields, such as pageCount or uncertainty.
| Working with | Implementation guide | Field reference |
|---|---|---|
| An observation | Observation records | Observation fields |
| Equipment and recordings | Equipment and captures | Acquisition and bindings |
| Event descriptions and setting | Event and setting | Event and setting |
| Witness accounts | Witnesses and accounts | Witnesses and accounts |
| Reports and editions | Documents and custody | Editions and custody |
| Specimens and laboratory results | Materials and laboratory | Materials and laboratory |
What you can use today
The guides use the published 2.0.0-beta.4 packages, including the sensor profiles, laboratory records and review APIs demonstrated in the showcase. Each guide names the packages it needs. The working viewer is available as a separate source download.
Installation and availability · Viewer and format support
Validation checks document structure and declared relationships. It does not establish source authenticity or a scientific conclusion. A check that has not run stays not_checked.
DisclosureOS is in beta. The ELDÆON partner preview uses a partial native mission archive, with source-intake checks and known limitations visible. Additional files, clock alignment and calibration context remain outstanding. Independent exchange testing, reproducible analysis, scientific review and governance remain stable-release gates.
Read with your tools
Use Copy Markdown or Open at the top of a guide or reference to read that page as text. Field exports include nested definitions and their publication status.
Use individual page exports for focused work. The documentation index lists the main starting paths; the complete V2 text is a large export of all guides and references. Historical V1 guidance is linked separately.