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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,21 @@
1
1
  # Changelog
2
2
 
3
+ ## 2.0.0-beta.4
4
+
5
+ ### Major Changes
6
+
7
+ - Revise the V2 observable definitions and support vocabulary directly, and add shared catalog, immutable revision and term references with supplied-byte validation. Keep the chosen term separate from the subject under review and its supporting sources. Export full observable and attributed OCS origin catalogs with retained methodological context. Update enriched-observation and scoring consumers to the revised definitions. This breaks earlier beta definition and support assumptions; it does not establish an anomalous origin or turn a reported characteristic into a confirmed assessment.
8
+
9
+ ### Patch Changes
10
+
11
+ - Updated dependencies [0b00be3]
12
+ - Updated dependencies [9580e62]
13
+ - Updated dependencies [559eac9]
14
+ - Updated dependencies [5a686c1]
15
+ - Updated dependencies [813ee2c]
16
+ - Updated dependencies
17
+ - @disclosureos/records@2.0.0-beta.4
18
+
3
19
  ## 2.0.0-beta.3
4
20
 
5
21
  ### Patch Changes
package/README.md CHANGED
@@ -1,36 +1,55 @@
1
1
  # @disclosureos/observables
2
2
 
3
+ Name a characteristic that someone reports or investigates. A vocabulary term does not establish that the characteristic occurred, that it is anomalous, or what caused it.
4
+
5
+ This README describes the **2.0.0-beta.4** API. Use one exact package version
6
+ throughout an application. Check [availability](https://os.disclosure.org/v2/docs/installation)
7
+ before installing; a source branch or packed candidate is not proof of npm
8
+ publication. For a candidate that is not yet published, use the verified local
9
+ tarballs. See the [release notes](https://github.com/disclosurefoundation/disclosureos/blob/codex/beta4-release-closure/docs/releases/2.0.0-beta.4.md)
10
+ for scope and verification. Avoid unversioned installs, which can select a different
11
+ API generation through `latest`.
12
+
13
+ ## V2 entry point
14
+
15
+ Use `createObservableCatalog` and `readObservableTermDefinition` from the package root. Pin the catalog, immutable revision, digest and selected term with the shared vocabulary-reference contract in `@disclosureos/records/experimental/v2`. Keep the subject under review and supporting sources separate. The twelve terms cover technology-related and biological/material characteristics, with methods and limits; they are not a reproduction of the original ATIP framework.
16
+
17
+ [Implementation guide](https://os.disclosure.org/v2/docs/observables) · [Availability](https://os.disclosure.org/v2/docs/installation) · [Example viewer](https://os.disclosure.org/showcase)
18
+
19
+ ## Choose a package version
20
+
21
+ Once this version is available in the registry, install it explicitly:
22
+
23
+ ```sh
24
+ npm install --save-exact @disclosureos/observables@2.0.0-beta.4
25
+ ```
26
+
27
+ Use the same exact release for all DisclosureOS packages. Before publication,
28
+ review a verified source checkout or its locally packed artifacts. Packages are
29
+ ESM; Node.js 22 is the documented getting-started runtime.
30
+
31
+ ## Additional API reference
32
+
33
+ <details>
34
+ <summary>Earlier composition APIs and detailed source-workflow reference</summary>
35
+
36
+ The following reference retains earlier APIs and source checkpoints. It is not the
37
+ V2 first-record tutorial. Installation commands here describe the candidate API
38
+ set; use the availability guidance above until that version is published.
39
+
3
40
  [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
4
41
 
5
- Anomaly-detection criteria for the [DisclosureOS](https://github.com/disclosurefoundation)
6
- ecosystem — the **Observables** layer. It answers *"what anomalous characteristics did
7
- the observation show?"* across two domains:
42
+ Descriptive characteristics for the [DisclosureOS](https://github.com/disclosurefoundation) ecosystem. An observable names something reported or investigated. The term does not establish that the characteristic occurred, that it is anomalous, or what caused it. Sources and measurements document the observation; attributed claims evaluate it.
8
43
 
9
- - **Technology** — the six AATIP-derived characteristics (`antigravity_lift`,
10
- `instantaneous_acceleration`, `hypersonic_no_signatures`, `low_observability`,
11
- `transmedium_travel`, `biological_effects`).
12
- - **Biologics** — six indicators for non-human biology (`molecular_complexity`,
13
- `isotopic_provenance`, `non_standard_biochemistry`, `non_phylogenetic_genetics`,
14
- `anomalous_morphology`, `anomalous_bio_interaction`).
44
+ The catalog has twelve terms in two editorial groups:
15
45
 
16
- ## The DisclosureOS model
46
+ - **Technology-related characteristics:** apparent hover, abrupt motion, hypersonic motion and signature discrepancy, sensor detection discrepancy, apparent medium transition, and biological changes around an event.
47
+ - **Biological and material characteristics:** molecular complexity pattern, isotope ratio departure, molecular composition difference, unresolved sequence relationship, unresolved morphological characteristics, and reported biological interaction.
17
48
 
18
- DisclosureOS is a **six-part standard**. Each part answers one question about an
19
- observation; `@disclosureos/schema` binds the package-owned pieces into one portable
20
- contract (a single TS type + JSON Schema + non-stripping parse).
49
+ The category names do not establish a technological or biological origin. Each definition includes relevant observations, methods, interpretation limits and methodological references. This DisclosureOS vocabulary is not a reproduction of the original ATIP framework.
21
50
 
22
- | Part | Package surface | Question it answers |
23
- |---|---|---|
24
- | **Records** | `@disclosureos/records` | *What was observed?* |
25
- | **Observables** | `@disclosureos/observables` | *What anomalous characteristics did it show?* |
26
- | **Origins** | `@disclosureos/origins` | *What might explain it?* |
27
- | **Claims** | `@disclosureos/records/shared` | *Who assessed it, why, and on what evidence?* |
28
- | **Scoring** | `@disclosureos/scoring` | *How complete / compelling is the case?* |
29
- | **Instruments** | `@disclosureos/instruments` | *What hardware produced the data?* |
51
+ ## The DisclosureOS model
30
52
 
31
- Supporting packages: **`@disclosureos/schema`** (the portable contract that composes the
32
- package-owned pieces), **`@disclosureos/cli`** (tooling), and **`@disclosureos/examples`**
33
- (the runnable golden path). *(You are here: **Observables**.)*
34
53
 
35
54
  ## Built on records
36
55
 
@@ -48,16 +67,14 @@ import '@disclosureos/observables'; // `observation.observableAssessments` is no
48
67
  > validated as a whole by `@disclosureos/schema` — in a single type-checked file. Run it
49
68
  > with `pnpm --filter @disclosureos/examples golden-path`.
50
69
  >
51
- > **Migrating an existing dataset?** See [`examples/migration-path.ts`](../../examples/migration-path.ts)
52
- > and the [onboarding workspace](https://os.disclosure.org/onboard).
53
70
 
54
71
  ## Install
55
72
 
56
73
  ```bash
57
- pnpm add @disclosureos/observables @disclosureos/records zod
74
+ pnpm add @disclosureos/observables@2.0.0-beta.4 @disclosureos/records@2.0.0-beta.4 zod
58
75
  ```
59
76
 
60
- ## Quick start
77
+ ## Assessments in an enriched observation
61
78
 
62
79
  ```typescript
63
80
  import { createObservableClaim } from '@disclosureos/observables';
@@ -67,7 +84,7 @@ const observation: Observation = {
67
84
  // ...records core fields...
68
85
  observableAssessments: {
69
86
  technology: {
70
- antigravity_lift: [{ level: 'confirmed', confidence: 1, evaluatedBy: 'AATIP' }],
87
+ apparent_hover: [{ level: 'reported', evaluatedBy: 'Example reviewer', rationale: 'The account describes apparent station keeping; range and support are unresolved.' }],
71
88
  },
72
89
  },
73
90
  };
@@ -80,11 +97,33 @@ same characteristic, and disagreement is first-class rather than overwritten.
80
97
  > `validateObservableAssessments()` (this package) or `parseEnrichedObservation()` from
81
98
  > [`@disclosureos/schema`](../disclosureos-schema).
82
99
 
100
+ ## Shared V2 vocabulary references
101
+
102
+ Export a complete catalog using the shared records-owned envelope:
103
+
104
+ ```typescript
105
+ import { createObservableCatalog, readObservableTermDefinition } from '@disclosureos/observables';
106
+
107
+ const catalog = createObservableCatalog({
108
+ id: 'observables-v2-baseline',
109
+ revision: '2026-10-13.1',
110
+ publishedBy: 'Disclosure Foundation',
111
+ publishedAt: '2026-10-13T00:00:00Z',
112
+ });
113
+ const definition = readObservableTermDefinition(catalog.terms[0]!);
114
+ ```
115
+
116
+ Retain the serialized catalog bytes and hash them before creating a shared reference. A reference identifies the catalog, exact revision, retained bytes and term. It is separate from the subject under review and from supporting source references. See [RFC 0007](../../docs/rfcs/0007-vocabulary-references.md) for the shared contract and binding examples.
117
+
118
+ Core term fields are `id`, `label`, `description`, `code` and `category`. Methodological metadata is retained in the `org.disclosureos.observables` extension. `readObservableTermDefinition()` validates that metadata using the package-owned definition schema and returns `undefined` for unrelated or malformed terms. The shared catalog parser validates generic structure and membership; it does not endorse scientific claims in a third-party extension.
119
+
120
+ The support tiers in the enriched-observation map describe the available information. They are distinct from V2 claim outcomes such as `confirmed`, `absent` and `inconclusive`; there is no automatic conversion between them. Use the shared V2 reference when a definition must be reproducibly identified.
121
+
83
122
  ## Subpath exports
84
123
 
85
124
  | Subpath | Contents |
86
125
  |---|---|
87
- | `@disclosureos/observables` | `ObservableAssessmentMap`, `createObservableClaim`, `validateObservableAssessments` |
126
+ | `@disclosureos/observables` | `ObservableAssessmentMap`, `createObservableClaim`, `validateObservableAssessments`, `createObservableCatalog`, `readObservableTermDefinition` |
88
127
  | `@disclosureos/observables/technology` · `/biologics` | Per-domain observable definitions |
89
128
  | `@disclosureos/observables/assessment` | Assessment levels + claim types |
90
129
  | `@disclosureos/observables/{labels,constants,guards,factories,formatters}` | The DX quintet |
@@ -99,3 +138,5 @@ validator or framework can consume them directly, with no DisclosureOS-specific
99
138
  ## License
100
139
 
101
140
  MIT © [Disclosure Foundation](https://disclosure.org)
141
+
142
+ </details>
@@ -1,5 +1,5 @@
1
- export { A as AssessmentLevel, b as AssessmentLevelSchema, c as ObservableAssessment, d as ObservableAssessmentSchema, e as ObservableBase, f as ObservableBaseSchema, a as ObservableCategory, g as ObservableCategorySchema, O as ObservableClaim, h as ObservableClaimSchema, i as ObservableDefinition, j as ObservableDefinitionSchema } from '../types-gDm-dEvQ.js';
1
+ export { A as AssessmentLevel, c as AssessmentLevelSchema, d as ObservableAssessment, e as ObservableAssessmentSchema, f as ObservableBase, g as ObservableBaseSchema, a as ObservableCategory, h as ObservableCategorySchema, O as ObservableClaim, i as ObservableClaimSchema, b as ObservableDefinition, j as ObservableDefinitionSchema } from '../types-Dx0yl1dG.js';
2
2
  export { ObservableAssessmentMap, ObservableAssessmentMapSchema } from '../constants/index.js';
3
3
  import 'zod';
4
- import '../types-DsfVlej0.js';
5
- import '../types-p_0pgxkz.js';
4
+ import '../types-DNk7V-A1.js';
5
+ import '../types-Dh1p5iPn.js';