@disclosureos/instruments 2.0.0-beta.3 → 2.0.0-beta.4

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @disclosureos/instruments
 
+## 2.0.0-beta.4
+
+### Patch Changes
+
+- Updated dependencies [0b00be3]
+- Updated dependencies [9580e62]
+- Updated dependencies [559eac9]
+- Updated dependencies [5a686c1]
+- Updated dependencies [813ee2c]
+- Updated dependencies
+  - @disclosureos/records@2.0.0-beta.4
+
 ## 2.0.0-beta.3
 
 ### Patch Changes

package/README.md

@@ -1,5 +1,42 @@
 # @disclosureos/instruments
 
+Describe the equipment and capture context behind a measurement, including exact manifest revisions, instrument instances, deployments, timing and calibration context.
+
+This README describes the **2.0.0-beta.4** API. Use one exact package version
+throughout an application. Check [availability](https://os.disclosure.org/v2/docs/installation)
+before installing; a source branch or packed candidate is not proof of npm
+publication. For a candidate that is not yet published, use the verified local
+tarballs. See the [release notes](https://github.com/disclosurefoundation/disclosureos/blob/codex/beta4-release-closure/docs/releases/2.0.0-beta.4.md)
+for scope and verification. Avoid unversioned installs, which can select a different
+API generation through `latest`.
+
+## V2 entry point
+
+Use `parseAcquisitionContext` from `@disclosureos/instruments/experimental/v2` for V2 captures. Sensor manifests remain available from the package root. Radar, sonar, lidar and satellite product profiles and readers live in `@disclosureos/schema/experimental/v2`. The Sensor Manifest originated with a contribution from ELDÆON.
+
+[Implementation guide](https://os.disclosure.org/v2/docs/instruments) · [Availability](https://os.disclosure.org/v2/docs/installation) · [Example viewer](https://os.disclosure.org/showcase)
+
+## Choose a package version
+
+Once this version is available in the registry, install it explicitly:
+
+```sh
+npm install --save-exact @disclosureos/instruments@2.0.0-beta.4
+```
+
+Use the same exact release for all DisclosureOS packages. Before publication,
+review a verified source checkout or its locally packed artifacts. Packages are
+ESM; Node.js 22 is the documented getting-started runtime.
+
+## Additional API reference
+
+<details>
+<summary>Earlier composition APIs and detailed source-workflow reference</summary>
+
+The following reference retains earlier APIs and source checkpoints. It is not the
+V2 first-record tutorial. Installation commands here describe the candidate API
+set; use the availability guidance above until that version is published.
+
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
 The **UAP Sensor Manifest** — a per-sensor specification standard for detection
@@ -11,22 +48,6 @@ different organizations are comparable, replicable, and verifiable.
 Proposed by [ELDÆON](https://github.com/disclosurefoundation/disclosureos/pull/5)
 and promoted into the framework as a foundation package.
 
-DisclosureOS is a **six-part standard**. Each part answers one question about an
-observation; `@disclosureos/schema` binds the package-owned pieces into one portable
-contract (a single TS type + JSON Schema + non-stripping parse).
-
-| Part | Package surface | Question it answers |
-|---|---|---|
-| **Records** | `@disclosureos/records` | *What was observed?* |
-| **Observables** | `@disclosureos/observables` | *What anomalous characteristics did it show?* |
-| **Origins** | `@disclosureos/origins` | *What might explain it?* |
-| **Claims** | `@disclosureos/records/shared` | *Who assessed it, why, and on what evidence?* |
-| **Scoring** | `@disclosureos/scoring` | *How complete / compelling is the case?* |
-| **Instruments** | `@disclosureos/instruments` | *What hardware produced the data?* |
-
-Supporting packages: **`@disclosureos/schema`** (the portable contract that composes the
-package-owned pieces), **`@disclosureos/cli`** (tooling), and
-**`@disclosureos/examples`** (the runnable golden path). *(You are here: **Instruments**.)*
 
 > **See it end to end.** [`examples/golden-path.ts`](../../examples/golden-path.ts)
 > takes one observation through every part — including a sensor manifest cited via
@@ -79,7 +100,7 @@ The functional hardware context `SensorReading` deliberately does not carry:
 ## Install
 
 ```bash
-pnpm add @disclosureos/instruments zod
+pnpm add @disclosureos/instruments@2.0.0-beta.4 zod
 ```
 
 ## Usage
@@ -112,7 +133,7 @@ formatSensorManifest(manifest);   // "ELDÆON — 1 sensor across 1 modality"
 Validate manifest files from the command line:
 
 ```bash
-pnpm dlx @disclosureos/cli manifest validate ./manifests/eldaeon-sensors.json
+pnpm dlx @disclosureos/cli@2.0.0-beta.4 manifest validate ./manifests/eldaeon-sensors.json
 ```
 
 ## JSON Schema
@@ -133,3 +154,5 @@ MIT © Disclosure Foundation
 ## Experimental acquisition context
 
 `@disclosureos/instruments/experimental/v2` adds pinned manifest, deployment, and channel-calibration history with explicit unresolved states. See the [contract and synthetic example](../../docs/experimental/acquisition-context.md). This additive metadata contract does not change the v1 manifest or certify scientific validity.
+
+</details>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@disclosureos/instruments",
-  "version": "2.0.0-beta.3",
+  "version": "2.0.0-beta.4",
   "description": "UAP Sensor Manifest — per-sensor specification standard for detection hardware in the DisclosureOS ecosystem",
   "license": "MIT",
   "repository": {
@@ -80,7 +80,7 @@
   ],
   "dependencies": {
     "zod": "4.4.3",
-    "@disclosureos/records": "2.0.0-beta.3"
+    "@disclosureos/records": "2.0.0-beta.4"
   },
   "devDependencies": {
     "@types/node": "^20",