disclosure.org valid

DisclosureOS

An open source data standard for unidentified anomalous phenomena (UAP).

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T11:30:56.147Z. Cached copy · Source on disclosure.org

# DisclosureOS

> An open source data standard for unidentified anomalous phenomena (UAP).
> V2 connects research records, instrument captures, shared terminology and
> attributed reviews. Applications choose how to store and display the data.

## Start here

- [Documentation](https://os.disclosure.org/v2/docs): Choose an implementation path and find guides or exact fields.
- [Your first record](https://os.disclosure.org/v2/docs/quickstart): Install one package, validate a fictional observation and inspect an error. Requires Node.js 22 and npm.
- [Installation and availability](https://os.disclosure.org/v2/docs/installation): Published Beta 4 packages and exact version requirements.
- [Document inspector](https://os.disclosure.org/v2/inspect): Try supported document checks in your browser. Input is not uploaded; profiles and external files are not checked.

## Six areas of the standard

These are related capabilities, not mandatory setup stages.

- [Records](https://os.disclosure.org/v2/docs/records-overview): Observations, accounts, documents, setting and material samples.
- [Instruments](https://os.disclosure.org/v2/docs/instruments-overview): Equipment, captures and the connection from a measured value to its source.
- [Observables](https://os.disclosure.org/v2/docs/observables): Terms for characteristics reported or investigated. A term does not establish that a characteristic occurred.
- [Claims](https://os.disclosure.org/v2/docs/claims): Source statements, unassessed questions and attributed assessments with their supporting inputs.
- [Origins](https://os.disclosure.org/v2/docs/origins): Terms for possible explanations, separate from a reviewer's conclusion.
- [Scoring and checks](https://os.disclosure.org/v2/docs/assessment): Declared scoring methods, validation results and reproduction receipts.

## Build and contribute

- [Run the showcase](https://os.disclosure.org/v2/docs/showcase): Download and run the fictional example viewer as application source.
- [Renderers and support](https://os.disclosure.org/v2/docs/showcase-support): Supported inputs, limits and component implementation notes.
- [Prepare a dataset contribution](https://os.disclosure.org/v2/docs/datasets): Receive a representative source file, check its identity and prepare an integration handoff.
- [Public standard](https://os.disclosure.org/v2/standard): Plain-language explanations and interactive examples.
- [Showcase](https://os.disclosure.org/showcase): The fictional DisclosureOS example case. Source filenames retain the name Meridian.

## Availability and interpretation

The published V2 package set is 2.0.0-beta.4 under npm's beta tag. The latest tag
still selects V1. Pin exact versions; do not use an unqualified install for V2.
Laboratory records, sensor profiles, shared vocabulary references and provider
scoring are included. Exact source revisions remain available for reproducing
the synthetic examples; they are not required to install these APIs.

Package versions,
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=disclosure.org · GET /v1/domain/disclosure.org · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for disclosure.org:
1. POST https://agentwebmap.com/v1/sites/disclosure.org/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://disclosure.org/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/disclosure.org/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/disclosure.org).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.