v2 Beta / Testimony
Keep each account connected to its witness.
Preserve who spoke, who recorded the account and what the source actually says. Keep qualifications, uncertainty and interpretation visible.
One witness can give several accounts. Keep each recording distinct, with its own date, recorder and wording. The example below is entirely fictional.
Fictional worked example
One witness, two recorded accounts.
A later retelling remains connected to the same witness. The account dates, source wording and recorder stay distinct.
Recorded 1981 · Recorder A
SYNTHETIC: I saw a light during the third quarter of 1952.
Synthetic account of a light; no sensor measurements supplied.
Summary by Synthetic editor
- Linked speaker
- Witness A
- Given under oath
- Unknown
- Source declaration
- Synthetic interview recorded in 1981
- source:account-1981
Original recording bytes are not supplied in this control.
Procedures remain sourced declarations.
- Polygraph administered
- Unknown
- Polygraph result
- Unknown
Interpretations name their reviewer.
Five years is a source declaration relevant to the event quarter. It does not authenticate the witness or establish independence.
Independence: Unknown
Review by Synthetic reviewer. No credibility score is calculated.
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.
16 top-level fields. Nested fields are included in search.
Witnesses and accounts
Public witnesses, distinct accounts, sourced procedures and aggregate declarations.
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:research-entities:0.1.0
@disclosureos/records/experimental/v2/entities/schema/0.1.0
The schema URN identifies the contract. Read the JSON through the package export above.
Attributable interpretations
Review a particular witness, account or assertion in an exact document version.
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.3.0
@disclosureos/records/experimental/v2/claims/schema/0.3.0
The schema URN identifies the contract. Read the JSON through the package export above.
Trace the preserved account.
The testimony provenance workflow checks recording citations, passage attribution and supplied account bytes. It remains a separate check from the witness and account declarations above. Neither check authenticates a speaker or establishes accuracy, independence or a scientific conclusion.
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.
6 top-level fields. Nested fields are included in search.
Testimony selection
Identify which accounts the provenance check should examine.
Implementation guide →Document identity and scope
Selected material
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:historical-testimony-selection:0.1.0
@disclosureos/schema/experimental/v2/historical-testimony/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.
These beta workflows cover specific provenance checks. Detailed descriptive and forensic coverage is still being completed.
Example source commit: 01d03051c6051c5713f150dd61264854c4214183. Public display fields are not a privacy sanitizer; private identity mappings and contact information belong outside the public record.