Event and setting

Context preserves the setting of an observation and the different accounts of what happened. It complements the Observation and acquisition documents. Explore the fields or download the fictional example.

Describe the setting

Observation context 0.1.0 provides seven typed entity families:

Each field contains source-attributed assertions. known means a value was supplied, not that it is verified. approximate, unknown, redacted and unmapped preserve distinct limitations. An absent field means it was not supplied. Unmapped terms retain original wording; zero and false remain actual values.

Competing descriptions stay separate. A selection records which assertion a reviewer selected, the alternatives considered, method, time and rationale. It does not create another value or prove an account correct.

Keep quantities in the observation

Context links to existing measurement IDs through defined roles. For example, ambient temperature belongs to an environment entity and requires the appropriate quantity and unit. The evaluator does not infer or convert units. Instrument measurements still use acquisition and measurement bindings.

Calendar quarters and ranges do not become invented instants. Relative temporal anchors must resolve locally without cycles. Timezone declarations do not automatically normalize dates or resolve daylight-saving ambiguity.

Parse a context document

These exports have been available since 2.0.0-beta.1:

import { parseObservationContext } from "@disclosureos/records/experimental/v2";

export function inspectContext(input: unknown) {
  const result = parseObservationContext(input);
  return {
    success: result.success,
    checks: result.checks,
    issues: result.issues,
  };
}

Parsing checks document structure and local relationships. It leaves external snapshot references not_checked. The browser inspector can perform this local parse; it does not load the referenced documents.

Address a specific description

Claim history 0.2.0 declares contextRefs. A context subject identifies an exact { documentId, schemaId, sha256 } snapshot and a target { kind, id, field? }. An assessment may cite an assertion through contextInputRefs, naming its field and assertion ID. IDs are scoped to the referenced document.

Use parseContextClaimHistory for 0.2.0. The existing parseExperimentalClaimHistory and default claims schema export remain 0.1.0. Existing provenance profiles accept their documented history versions; a 0.2.0 history is not automatically supported by those profiles.

A changed context snapshot represents a different subject. A new assessment may cite an earlier claim, but cannot supersede it as though it examined the same bytes. Current claims are those not superseded, not confirmed conclusions.

Review supplied snapshots

import { evaluateContextClaimHistory } from "@disclosureos/schema/experimental/v2";

export async function reviewContext(
  history: unknown,
  documents: ReadonlyMap<string, Uint8Array>
) {
  return evaluateContextClaimHistory(history, { documents });
}

The map is keyed by SHA-256 and contains the exact UTF-8 bytes for each required context, observation and acquisition snapshot. The evaluator copies and hashes supplied bytes, checks IDs and contract versions, and resolves entity, field, assertion and measurement references. It fetches nothing. Missing snapshots cannot pass, and altered bytes fail integrity checks.

A successful result does not certify source authenticity, scientific interpretation, sensor fusion or temporal normalization. Profile validation and source-artifact integrity also remain explicitly unchecked by this evaluator.

Run the example

Download and extract context.zip, then:

cd context
npm install --ignore-scripts
npm start

The fictional optical and radio captures remain separate. Shape accounts conflict; capture alignment and measurement uncertainty are unknown. The runner supplies local snapshot bytes to the published evaluator. None of the example is ELDÆON data.

Schema exports

• @disclosureos/records/experimental/v2/context/schema/0.1.0
• @disclosureos/records/experimental/v2/claims/schema/0.2.0

Package versions and document contract versions are distinct. These schema URNs identify local contracts rather than downloadable HTTP endpoints. Witness, material and case extensions remain separate completion work.