An official website of the Disclosure Foundation

Introduction

Overview

Commands

scaffoldvalidateregistryinfo

registry

Introspect the field, observable, and origin registries from the terminal

disclosureos registry answers "what does the standard define?" without opening an editor — the field lexicon, the twelve observables, and the OCS taxonomy, straight from the packages' own exports.

Usage

Terminal
disclosureos registry <subcommand> [options]

registry fields

The observation field inventory, derived from the records JSON Schema (the same deriveFieldPaths() that powers completeness scoring):

Terminal
disclosureos registry fields
# every schema-derived field path, grouped by top-level domain

disclosureos registry fields --category temporal
# one group, as a path/required table

registry observables

All twelve observables with codes, labels, and descriptions:

Terminal
disclosureos registry observables
disclosureos registry observables --technology   # TO-1 … TO-6 only
disclosureos registry observables --biologics    # BO-1 … BO-6 only
Technology Observables (AATIP-derived)

  TO-1  Anti-Gravity Lift
        Object appears to overcome gravitational force without conventional propulsion…
  TO-2  Instantaneous Acceleration
        …

Assessment Levels: not_indicated → reported → documented → measured → confirmed

registry origins

The OCS taxonomy:

Terminal
disclosureos registry origins
# the full tree: 3 domains, subdomains, and categories

disclosureos registry origins --id 1.1.3
# one node in detail: label, domain, depth, testability, aliases, children

disclosureos registry origins --testable
# only hypotheses with scientificallyTestable: true
ID:          1.1.3
Label:       Extraterrestrial
Domain:      physical
Testable:    Yes
Aliases:     ETH

Children (4):
  • [1.1.3.1] Solar System
  • [1.1.3.2] Interstellar
  • [1.1.3.3] Intergalactic
  • [1.1.3.4] Unknown Region of Space-Time

When to use it

  • Writing a data mapping and need the exact field paths → registry fields
  • Deciding which observable a signature falls under → registry observables
  • Choosing the right OCS node and depth for a claim → registry origins --id
  • Scoping which hypotheses your tool should surface as testable → registry origins --testable

For single-item lookups with ancestry paths, info is the quicker tool.

validate

Validate observation JSON files — core, slots, evidence refs, and semantic checks

info

Quick reference for types, observables, and OCS nodes

On this page

Usage
registry fields
registry observables
registry origins
When to use it