Changelog

The Instruments layer is now installable. @disclosureos/instruments@1.0.0 is live on npm — the standard's first new foundation package since launch, and its first community-proposed one — alongside the coordinated releases that carry it:

• @disclosureos/instruments 1.0.0 — the SensorManifest document type, the calibration maturity gradient, and validateSensorManifest.
• @disclosureos/records 1.1.0 — SensorReading.sensorRef plus the expanded SensorType and DetectionMethod vocabularies.
• @disclosureos/schema 1.1.0 — the composed enriched-observation contract, re-emitted to carry the records changes.
• @disclosureos/scoring 1.1.0 — the calibrationTrust evaluator-weight hook.
• @disclosureos/cli 1.1.0 — disclosureos manifest validate, and disclosureos validate now warns on malformed sensorRef values.
• @disclosureos/observables 1.0.1 and @disclosureos/origins 1.0.1 — dependency refreshes.

pnpm add @disclosureos/instruments @disclosureos/records @disclosureos/schema

The versioned JSON Schema artifacts behind the release are served from this site — every $id in a published package resolves, including the new sensor-manifest schema. See the Instruments docs to publish a manifest for your own array.

The standard now has a sixth part. Instruments — published sensor manifests describing what an organization's instruments are, how they keep time, and how they are calibrated — lands in the open repository as @disclosureos/instruments, alongside supporting changes across the foundation packages:

• @disclosureos/instruments — the SensorManifest document type with the full companion set: labels, constants, guards, factories, formatters, and validateSensorManifest.
• @disclosureos/records — sensor readings can now cite a manifest entry through the new sensorRef field (<org-slug>:<sensor-id>), and the SensorType and DetectionMethod vocabularies expanded to cover distributed sensor arrays.
• @disclosureos/scoring — the new calibrationTrust hook lets scoring credit claims backed by instruments with published calibration provenance. Defaults are conservative: nothing ever weighs below the baseline.
• @disclosureos/cli — disclosureos manifest validate checks a manifest file against the schema from the command line.

The manifest format was proposed by ELDÆON, the standard's first external contributor, whose published manifest serves as the worked example on the Instruments page. See the Instruments docs to publish your own.

The site grew alongside the standard:

• Instruments is the sixth section of the Standard Explorer — manifest anatomy, the calibration gradient and its scoring multipliers, and ELDÆON's published manifest rendered live as the worked example, with a registry of participating organizations.
• Instruments documentation covers the manifest schema, calibration model, and a step-by-step publishing guide; the quick start, architecture overview, and API reference were updated throughout to reflect six parts.
• Navigation was restructured: the component parts now live in a single Standard dropdown, and the footer moved to a multi-column layout.
• This changelog — a running record of changes to the standard, the packages, and the site.

Three weeks after launch, the standard received its first external contribution. ELDÆON opened pull request #5 proposing a sensor manifest: a published document describing what an organization's instruments are — hardware specifications, detection methods, timing sources, calibration status, and raw-data locators — drawn from their own operating array of 28 sensors across 6 modalities.

The proposal filled a real gap. A case record can say a radar tracked something; nothing in the standard could yet say what that radar is, or how — or whether — it is calibrated. The review that followed shaped the proposal into a full foundation package, which merged the following week.

The DisclosureOS standard is public. Six foundation packages published to npm at 1.0.0, and the full source opened at disclosurefoundation/disclosureos under the MIT license:

• @disclosureos/records — the Observation type and the shared vocabulary every other layer builds on. Depends only on Zod, works standalone.
• @disclosureos/observables — twelve defined anomaly signatures across the Technology and Biologics frameworks, claimed with evidence.
• @disclosureos/origins — the Origin Classification System: a permanent taxonomy of competing explanations, from the mundane to the exotic.
• @disclosureos/scoring — completeness and compellingness as separate measures. There is deliberately no single headline score.
• @disclosureos/schema — the portable contract. Composes every package-owned slot into one enriched, validated record, emitted as JSON Schema (draft 2020-12) for use beyond TypeScript.
• @disclosureos/cli — scaffold, validate, and inspect observations from the terminal.

Design commitments worth noting: evaluative statements are recorded as claims — attributed, evidence-backed, and held in lists so evaluators can disagree without overwriting each other. All packages are ESM-only, require Node 20+, and ship with a runnable golden path that takes the 2004 USS Nimitz encounter through every layer of the standard.

Alongside the v1 packages, this site launched as the human-readable rendering of the standard:

• The Standard Explorer — a guided walk through each component part (Records, Observables, Origins, Claims, and Scoring), written to be readable without a technical background. Every field list, enum, and definition on these pages is generated from the packages themselves, so the site can never drift from the code.
• Documentation — a quick start, the full golden path, concept guides for the mental model, and migration guides for bringing existing datasets onto the standard.
• API Reference — browse every exported type, its properties, and its companion guards, formatters, and factories, extracted directly from the package sources.
• Onboarding workspace — map your CSV, JSON, or database fields onto Observation records, validate the output, and see what is missing before you commit to a migration.