DisclosureOS · v2 Beta documentation
Build with DisclosureOS
From a working example to the records, contracts and checks behind it.
These docs explain how to assemble, validate and publish a research record. Start from the working viewer, follow a source-specific guide, or open a field reference. For an introduction to what the parts mean, visit the Standard.
Start here
| Your goal | Start here |
|---|---|
| Run a complete example with its viewer | Build the Meridian showcase |
| Validate a first observation | Install the beta, then Records |
| Find a field or constraint | Open a subject in the sidebar, then its field reference, or use search |
| Contribute partner data | Dataset preparation |
Choose your source material
| You have | Guide | Field reference |
|---|---|---|
| Observation sources and measurements | Records | Observation |
| Equipment and time-series data | Instruments and bindings | Acquisition and bindings |
| Descriptions of an event and its setting | Context | Event and setting |
| Witness accounts | Testimony | Witnesses and accounts |
| Reports, editions or archival files | Documents | Editions and custody |
| Specimens or laboratory results | Physical samples | Sample provenance and candidate laboratory contracts |
Interpret and review
Use claim histories to preserve an assessment's author, method, inputs and changes. The observable catalog describes reported characteristics; the origin catalog organizes hypotheses. Assessment and review explains what each validation outcome means.
Release status
The npm beta is 2.0.0-beta.3, available for integration testing and feedback. It is not a stable release. Each field reference identifies its package or candidate status. The showcase guide pins newer source-candidate contracts and provides a reproducible path for using them.
Keep facts and interpretations distinct
An observation holds sources, products, methods, assertions and measurements. A claim history attributes interpretations separately. Instrument context describes declared acquisition and calibration history; it does not independently verify it.
Validation has explicit boundaries: structural, semantic, profile and external checks. A check that has not run remains not_checked. Passing document validation does not establish a scientific conclusion.
What remains under review
The full native ELDÆON archive and partner mapping approval are pending. Independent semantic exchange, real-data reproduction, qualified scientific review and governance remain stable-release gates. The public preview is not a native acquisition dataset.