Purpose
Purpose explains why Beacon exists, what problem it solves, and how discovery improves visibility across the Satoshium ecosystem.
Open Purpose →Beacon · Discovery & Signals
Satoshium Beacon
Satoshium Beacon is the Satoshium Suite institution for Discovery & Signals. It locates, surfaces, organizes, and preserves relevant discoveries as governed Discovery Signals while maintaining the path to their sources and canonical objects.
Beacon's institutional and production architecture is now defined. The next step is controlled first production: selecting a real discovery candidate and executing the governed path toward the first production Discovery Signal.
Discovery
Discovery is the process of locating, surfacing, organizing, and presenting relevant information that may otherwise remain difficult to find.
Open Discovery →Signals
Discovery Signals are Beacon-owned objects documenting observations, events, changes, indicators, updates, or relationships identified through discovery as potentially relevant.
Open Signals →Sources
Sources provide origin, context, attribution, and traceability for information surfaced through Beacon discovery processes.
Open Sources →Indexes
Indexes organize information to improve discovery, navigation, classification, relationship mapping, and long-term accessibility.
Open Indexes →Queries
Queries express discovery intent and context. They may be received directly by Beacon or supplied through Navigator-defined workflows.
Open Queries →Results
Results are the discoveries generated through Beacon, including surfaced signals, sources, records, relationships, and related context.
Open Results →Trust
Trust defines the boundary between discovery and trust assessment. Beacon may surface trust-related information, but it does not determine trust.
Open Trust →Interoperability
Interoperability explains how Beacon connects discovery across Atlas, Navigator, Certifier, Registry, Chronicle, Anchor, and Attestor.
Open Interoperability →Integration
Integration defines how Beacon connects to Certifier, Registry, Chronicle, Anchor, and the broader Satoshium Suite while publishing discovery signals.
Open Integration →Certification Signals
Certification Signals define the discovery signals Beacon publishes to help users locate certification-related information without becoming the certification authority.
Open Certification Signals →Discovery Metadata
Discovery Metadata defines the structured information Beacon uses to improve searchability, interoperability, filtering, and long-term discoverability.
Open Discovery Metadata →Status
Status provides the current development state, capabilities, limitations, roadmap, and implementation posture of Beacon.
Open Status →FAQ
FAQ answers common questions about Beacon, discovery, signals, sources, indexes, queries, results, verification, and trust boundaries.
Open FAQ →Production Architecture
Phase II defines the canonical Discovery Signal, its institutional rules, public representation, methodology, and controlled path into production.
Entry Model → Signal Types → Lifecycle → Identifier → Schemas → Validation →
Provenance → Authority → Relationships → Versioning → Publication → Records →
Individual Record → Methodology → Production
Discovery Signal Entry Model
Defines the canonical Beacon production object and the institutional components required to represent a Discovery Signal.
Open Entry Model →Discovery Signal Types
Defines Beacon's governed discovery classifications and distinguishes Signal Type from the identity and authority of the referenced source object.
Open Signal Types →Discovery Signal Lifecycle
Defines how a Discovery Signal progresses through Draft, Active, Superseded, Resolved, or Withdrawn while publication remains separately governed.
Open Lifecycle →Identifiers
Defines the permanent BEAC-YYYY-NNNN identifier standard used for canonical Beacon Discovery Signals.
Open Identifiers →Schemas
Defines the structural architecture for canonical Discovery Signals and supporting source, result, and operational representations.
Open Schemas →Validation
Defines Beacon's production-conformance gate for evaluating canonical identity, required structure, provenance, references, relationships, and schema conformity.
Open Validation →Discovery Provenance
Defines how Beacon preserves the evidentiary path from source observation and discovery context to the resulting Discovery Signal.
Open Provenance →Authority & Reference Model
Defines what Beacon owns, what referenced institutions and sources retain, and how discovery preserves authority without absorbing it.
Open Authority →Relationship Model
Defines how Beacon represents meaningful connections among Discovery Signals, Suite objects, workflows, versions, and external sources without merging their identities.
Open Relationships →Versioning & Supersession
Defines how Beacon preserves stable identity, material revisions, supersession, and historical continuity without silent overwrite.
Open Versioning →Publication Model
Defines the governed act that moves an eligible Discovery Signal from Unpublished to Published without changing its underlying authority.
Open Publication →Beacon Records
Provides the human-facing index architecture for published canonical Discovery Signals and their permanent Beacon Record pages.
Open Records →Individual Beacon Record
Defines the canonical public HTML representation of one published Discovery Signal beneath its permanent BEAC identifier path.
Open Record Template →Discovery Methodology
Defines the repeatable institutional process from observation and provenance through canonical creation, validation, publication, representation, and maintenance.
Open Methodology →Production
Defines the controlled path from completed architecture into actual institutional use and the first governed production operation.
Open Production →Beacon Framework
Beacon discovery may begin with a direct query or a Navigator-defined workflow. Beacon locates relevant information, publishes Discovery Signals and metadata, and preserves the path to the referenced source or canonical object.
Workflow / Query → Beacon Discovery → Discovery Signal / Metadata → Result / Referenced Source or Canonical Object
Role Within the Satoshium Suite
Beacon occupies a distinct institutional role within the Suite. Interoperability connects responsibilities while each institution retains authority over its own canonical objects.
Atlas → Authoritative Intelligence
Navigator → Workflow Definition / Orchestration
Beacon → Discovery Signal / Metadata
Certifier → Certification Package
Registry → SREG
Chronicle → Chronicle Entry
Anchor → Integrity Reference
Attestor → Trust Statement
Navigator → Workflow Definition / Orchestration
Beacon → Discovery Signal / Metadata
Certifier → Certification Package
Registry → SREG
Chronicle → Chronicle Entry
Anchor → Integrity Reference
Attestor → Trust Statement
Beacon Authority Boundary
Beacon owns its Discovery Signals, discovery metadata, indexes, and discovery presentations. It may reference canonical objects maintained by other Suite institutions without duplicating them or assuming their authority.
Discovery does not become certification, registration, history, integrity, trust, authoritative intelligence, or workflow orchestration.
Reference does not transfer authority.
Reference does not transfer authority.
Current Beacon Status
Beacon's institutional architecture and Phase II production architecture are now defined. Beacon remains in Continuing Development until the architecture is exercised through a real governed production operation and the resulting evidence supports operational consideration.
Phase I — Institutional Architecture & Alignment → COMPLETE
Phase II — Production Architecture → COMPLETE
First Production Candidate → Not yet selected
BEAC-2026-0001 → Not yet created
First Production Operation → Pending
Production Proof → Pending
Operational → No
Phase II — Production Architecture → COMPLETE
First Production Candidate → Not yet selected
BEAC-2026-0001 → Not yet created
First Production Operation → Pending
Production Proof → Pending
Operational → No
Beacon Workflow
Beacon transforms scattered information into governed discovery references, Discovery Signals, and metadata. It does not replace the institutions that own authoritative intelligence, certification, registration, history, integrity, trust, or workflow orchestration.
Navigator may orchestrate. Beacon discovers and signals. Atlas, Certifier, Registry, Chronicle, Anchor, and Attestor retain authority for their institution-owned canonical objects.
Reference does not transfer authority.
Reference does not transfer authority.
Next Institutional Step
Beacon's next step is no longer another architecture page. It is the controlled selection of a real discovery candidate and execution of the first governed production operation.
Select first real candidate → Execute Discovery Methodology → Create canonical
Discovery Signal → Assign BEAC-2026-0001 at Creation → Validate & Review →
Govern lifecycle → Decide publication → Publish Record when justified →
Preserve production evidence → Conduct operational review
Open Production Model →