v2 Beta / Event and setting
Give every observation its context.
Describe the setting, preserve what people reported, and connect each interpretation to the detail it examines.
Keep different accounts attributable. A known value records what a source supplied; it does not establish that the description is correct.
Keep the account
Shapes, maneuvers, weather and platform details retain their source and any uncertainty.
Connect the quantity
Measurements remain in the observation. Context identifies what they describe, such as ambient station temperature.
Name the subject
An interpretation can concern a specific object, field or source assertion in an exact document version.
Fictional worked example
One observation. Distinct accounts.
The control includes independent optical and radio captures, two conflicting descriptions and an environmental reading. None of it represents ELDÆON data.
- Station temperature
- 18.2 °C
- Measurement uncertainty not reported.
- Reported shape
- Triangle / Oval
- Both accounts retained. Neither selected.
- Capture alignment
- Unknown
- The two sensor tracks remain separate.
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.
15 top-level fields. Nested fields are included in search.
Event and setting
Sourced descriptions of objects, places, platforms, historical time and environmental conditions.
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:observation-context:0.1.0
@disclosureos/records/experimental/v2/context/schema/0.1.0
The schema URN identifies the contract. Read the JSON through the package export above.
Interpretations with precise references
Claims about a particular context entity or field, tied to the exact document version and source assertions.
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.2.0
@disclosureos/records/experimental/v2/claims/schema/0.2.0
The schema URN identifies the contract. Read the JSON through the package export above.
Fictional example from canonical commit 6451017831cd3859ffe05fcb8cba20908ce12a84. Document integrity does not establish source authenticity, scientific correctness or sensor fusion.
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.