Overview

@disclosureos/observables answers the second question the standard asks: what anomalous characteristics did it show?

It defines twelve observables — specific, detectable anomaly signatures, each with a scientific basis, detection signals, and measurement methods — and the claim machinery for asserting them against an observation with evidence.

npm install @disclosureos/observables

The two frameworks

Each observable is a full definition, not just an enum value:

import { TECHNOLOGY_OBSERVABLES } from '@disclosureos/observables';

const def = TECHNOLOGY_OBSERVABLES.instantaneous_acceleration;
def.code;             // 'TO-2'
def.label;            // 'Instantaneous Acceleration'
def.scientificBasis;  // why this is anomalous, with citations
def.detectionSignals; // what to look for
def.methods;          // how to measure it
def.references;       // published analyses

This is what makes the framework auditable: the criteria for "anomalous" are public, specific, and versioned — not vibes.

The slot

Importing the package augments Observation with the observableAssessments slot:

import { createObservableClaim } from '@disclosureos/observables';

observation.observableAssessments = {
  technology: {
    instantaneous_acceleration: [
      createObservableClaim('confirmed', {
        confidence: 0.85,
        rationale: 'Radar tracked descent from ~80,000 ft to sea level in seconds.',
        evidenceRefs: ['sensor:princeton-spy1-radar'],
      }),
    ],
  },
};

Three things to notice:

1. The key carries the observable id — claims in the map don't repeat it.
2. The value is an array — multiple evaluators can claim the same observable, including in opposite directions. Disagreement is data.
3. Claims cite evidence — evidenceRefs point at sensors, media, testimony, or physical evidence inside the record.

Assessment levels

Claims are tiered by how strongly the signal is established — see Assessment:

not_indicated → reported → documented → measured → confirmed

Validation

import { validateObservableAssessments } from '@disclosureos/observables';

const issues = validateObservableAssessments(slotValue); // ValidationIssue[]

For whole enriched records, use parseEnrichedObservation.

In this section

• Technology Observables — TO-1 through TO-6 in full
• Biologics Observables — BO-1 through BO-6 in full
• Assessment — levels, claims, and the slot shape
• Claiming Observables — the working guide