Purpose
Discovery Metadata provides structured descriptive information that improves searchability, interoperability, navigation, traceability, and long-term accessibility without replacing institution-owned canonical objects.
BEACON · DISCOVERY METADATA
Satoshium Beacon Discovery Metadata
Discovery Metadata is Beacon-owned supporting structured information used to help users, applications, and workflows locate, organize, filter, interpret, and trace discoverable information across the Satoshium Suite and external sources.
Metadata improves discovery while preserving canonical identifiers, provenance, context, traceability, and the authority of the sources and canonical objects it references.
Institutional Role
Beacon owns its Discovery Signals and the supporting discovery metadata associated with them. It does not acquire authority over the canonical objects or external information that its metadata references.
Searchability
Metadata allows Authoritative Intelligence, Certification Packages, SREG records, Chronicle Entries, Integrity References, Trust Statements, Discovery Signals, and external sources to be located efficiently.
Interoperability
Standardized metadata enables future systems, APIs, search engines, indexes, and discovery services to exchange information consistently.
Discovery Metadata
Discovery metadata describes discovered information and its relationships rather than replacing the referenced source or canonical object. It helps users and systems understand what was discovered, where it came from, and which institution retains authority.
Beacon Identifier
Subject
Primary Signal Type
Source Reference
Provenance
Discovery Character / Domain / Scope
Discovery Relevance / Basis
Canonical References
Relationships
Observed / Created / Published Timestamps
Lifecycle State
Publication State
Version / Supersession
Subject
Primary Signal Type
Source Reference
Provenance
Discovery Character / Domain / Scope
Discovery Relevance / Basis
Canonical References
Relationships
Observed / Created / Published Timestamps
Lifecycle State
Publication State
Version / Supersession
First Production Metadata Example
BEAC-2026-0001 provides Beacon's first real production example of Discovery Metadata applied to a canonical Discovery Signal.
Beacon Identifier → BEAC-2026-0001
Subject → Atlas Jurisdiction Record — El Salvador
Primary Signal Type → Certification
Source Institution → Satoshium Certifier
Source Object → SC-CERT-2026-0001
Source Object Type → Canonical Certification Package
Source Version → 1.1
Provenance Type → Direct
Observation Method → Direct review of published canonical source
Observed → September 13, 2026
Observed Condition → Issued · Active · Operational
Discovery Character → Institutional
Discovery Domain → Certification
Discovery Scope → Existence and current certification condition
Discovery Basis → Direct authoritative source observation
Lifecycle → Active
Publication → Published
Version → 1.0
Subject → Atlas Jurisdiction Record — El Salvador
Primary Signal Type → Certification
Source Institution → Satoshium Certifier
Source Object → SC-CERT-2026-0001
Source Object Type → Canonical Certification Package
Source Version → 1.1
Provenance Type → Direct
Observation Method → Direct review of published canonical source
Observed → September 13, 2026
Observed Condition → Issued · Active · Operational
Discovery Character → Institutional
Discovery Domain → Certification
Discovery Scope → Existence and current certification condition
Discovery Basis → Direct authoritative source observation
Lifecycle → Active
Publication → Published
Version → 1.0
Related canonical references include SREG-2026-0001, CHR-2026-0001, and ANCH-2026-0001. Those relationships provide discovery context while the direct provenance for the signal remains SC-CERT-2026-0001 → Beacon observation → BEAC-2026-0001.
Open BEAC-2026-0001 →Filtering
Metadata supports filtering by status, jurisdiction, institution, canonical object type, classification, source, date, category, relationship, or other governed discovery attributes.
Classification
Metadata helps organize discovered information into meaningful categories without modifying the referenced sources or canonical objects.
Relationships
Metadata preserves relationships among Discovery Signals, Atlas intelligence, Certification Packages, SREG records, Chronicle Entries, Integrity References, Trust Statements, Navigator workflow context, and external sources.
Machine Discovery
Structured metadata enables future machine-readable discovery services, federated search, indexing, APIs, and intelligent assistants.
Relationship to Other Systems
Discovery Metadata may reference canonical objects maintained by Atlas, Certifier, Registry, Chronicle, Anchor, and Attestor, and may preserve context from Navigator-defined workflows and attributable external sources.
Beacon owns the discovery metadata.
Authority for referenced canonical objects remains with the originating institution.
Reference does not transfer authority.
Authority for referenced canonical objects remains with the originating institution.
Reference does not transfer authority.
Metadata Authority Boundary
Discovery Metadata is a Beacon-owned supporting metadata layer. It may describe or reference information maintained elsewhere, but it is not a second canonical Beacon object, does not become the authoritative canonical object of the referenced information, and does not transfer authority to Beacon.
Atlas → Authoritative Intelligence
Navigator → Workflow Definition / Orchestration
Certifier → Operational Certification
Registry → Canonical Registration / Public Catalog
Chronicle → Historical Preservation
Anchor → Integrity Preservation
Beacon → Discovery & Signals
Attestor → Governed Attestation & Rule-Constrained Evaluation
Navigator → Workflow Definition / Orchestration
Certifier → Operational Certification
Registry → Canonical Registration / Public Catalog
Chronicle → Historical Preservation
Anchor → Integrity Preservation
Beacon → Discovery & Signals
Attestor → Governed Attestation & Rule-Constrained Evaluation
Future Metadata Development
Beacon's governed Discovery Metadata architecture, reference conventions, relationship model, provenance model, lifecycle, publication state, and validation expectations are now defined and have been exercised in production through BEAC-2026-0001. Exact machine serialization, frozen machine enums, machine-readable feeds, APIs, broader indexing, automation, and Navigator workflow interfaces remain available for later development.
Current Institutional Status
Beacon Status → Operational · September 2026
Canonical Object → Discovery Signal
Discovery Metadata → Supporting Structure
BEAC-2026-0001 → Active · Published · Version 1.0
Production Evidence Preservation → Complete
Post-Operation Review → Complete
Production Proof → Established
Canonical Object → Discovery Signal
Discovery Metadata → Supporting Structure
BEAC-2026-0001 → Active · Published · Version 1.0
Production Evidence Preservation → Complete
Post-Operation Review → Complete
Production Proof → Established
Beacon's metadata capabilities may continue to evolve without changing Beacon's Operational institutional status or the canonical-object boundary.
Discovery Philosophy
Discovery becomes more useful and reviewable when metadata remains clear, stable, attributable, traceable, portable, versioned, and interoperable across institutional boundaries.
Beacon helps users and workflows discover information. Discovery metadata preserves enough context to understand what was discovered, where it came from, how it relates to other objects, and where authority remains.
Discovery Signals identify relevance.
Metadata preserves context and relationships.
Canonical objects preserve institutional authority.
Reference does not transfer authority.
Back to Beacon →
Beacon Records →
Metadata preserves context and relationships.
Canonical objects preserve institutional authority.
Reference does not transfer authority.