Overview

@disclosureos/schema is not another part of the standard. It's the contract: the package that takes the records core and the registered slots and makes them one thing — in TypeScript, in JSON Schema, and at runtime.

npm install @disclosureos/schema

Install it whenever a record can carry more than the core lexicon. In practice: always, except in tools that only ever touch core records.

The three things it does

One import, full contract

Importing the package does three things at once:

import { parseEnrichedObservation, type EnrichedObservation } from '@disclosureos/schema';

1. Types — both satellite packages are imported, so observableAssessments and origin are typed on Observation. EnrichedObservation names that complete shape.
2. Runtime — both first-party slots are registered on defaultRegistry.
3. Validation — parseEnrichedObservation is ready to validate the whole enriched record.

const result = parseEnrichedObservation(record);

if (result.success) {
  // result.data — the SAME object you passed in, slots intact
} else {
  // result.issues — [{ path: 'origin[0].confidence', message: '...' }, ...]
}

Why a contract package exists

The records core schema can't know about the slots — records can't depend on its own satellites. That leaves a gap with two failure modes:

• The strip hazard: ObservationSchema.parse() silently drops slot data.
• The portability gap: TS module augmentation is invisible to JSON Schema and non-TS languages.

@disclosureos/schema closes both at the integration layer, by delegation: the core is validated by records' own validator, each slot by its owner package's validator, and the JSON Schemas are merged as plain data. No layer's authority is duplicated; the contract just composes them.

Design properties

• Registry-driven. Validation and schema composition both walk the registry. A newly registered slot is validated and composed with no changes to either code path.
• Closed root, open extension area. Unknown top-level keys are rejected (typo protection); arbitrary third-party data still flows through the extensions bag.
• Reference-equal on success. parseEnrichedObservation returns your object, not a reconstruction — nothing is stripped because nothing is rebuilt.
• Versioned artifact. The composed schema is enveloped with $id and x-schema-version (ENRICHED_OBSERVATION_SCHEMA_VERSION), with drift tests guarding the committed artifact.