An official website of the Disclosure Foundation
01RecordsRecord what was measured, who supplied it, and what remains unknown.02InstrumentsConnect measurements to the equipment and conditions that produced them.03ClaimsShow who reached a conclusion and which parts of the record they used.04ObservablesSeparate a reported characteristic from a sensor-supported finding.05OriginsCompare possible explanations while keeping uncertainty visible.06ScoringDistinguish missing documentation from a scientific result.
DatasetsDocsOnboardChangelog

The Standard

01RecordsRecord what was measured, who supplied it, and what remains unknown.02InstrumentsConnect measurements to the equipment and conditions that produced them.03ClaimsShow who reached a conclusion and which parts of the record they used.04ObservablesSeparate a reported characteristic from a sensor-supported finding.05OriginsCompare possible explanations while keeping uncertainty visible.06ScoringDistinguish missing documentation from a scientific result.

Datasets

Explore published data

Docs

Implement the standard

Onboard

Bring your dataset

Changelog

What changed, and when

GitHub

Open standards and tools for UAP research.

The Standard

  • Records
  • Observables
  • Origins
  • Claims
  • Scoring
  • Instruments

Resources

  • Datasets
  • Documentation
  • Onboard your data
  • Changelog

Project

  • GitHub
  • Disclosure Foundation
  • Donate

© 2026 Disclosure Foundation. All rights reserved.

v2 Beta / 03 / Claims

Keep interpretations attributable.

Show who reached a conclusion and which parts of the record they used.

An interpretation belongs to its author. The observation and its claim history remain distinct, so competing explanations can be reviewed without rewriting the underlying record.

What the beta supports

Claim-history validation checks references and document consistency. A valid claim document is not a verified scientific conclusion.

Read the documentationInspect a sample

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.

Claim historyFollow a worked example

6 top-level fields. Nested fields are included in search.

Claim history

An observation with attributed source statements, assessments and revision history.

Implementation guide →

Document identity

Observation and claims

Additional information

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.1.0

@disclosureos/records/experimental/v2/claims/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.

Event and settingPreserve sourced descriptions of objects, places, time and collection conditions.Instrument capturesConnect readings to equipment, channels and capture conditions.TestimonyConnect witnesses, distinct recorded accounts and attributed reviews to their sources.DocumentsPreserve each edition’s release history, digital custody and attributable reviews.Physical samplesConnect a collected specimen to the records describing its collection and handoffs.

These beta workflows cover specific provenance checks. Detailed descriptive and forensic coverage is still being completed.

RecordsInstrumentsClaimsObservablesOriginsScoring