Purpose
Beacon Integration establishes the institutional boundary between discovery and authority. Beacon helps information become discoverable while preserving canonical identifiers, provenance, context, ownership, and institutional authority.
Beacon · Integration
Satoshium Beacon Integration
Beacon Integration defines how Beacon connects to the Satoshium Suite by publishing Discovery Signals and discovery metadata without becoming the authority for the canonical objects those signals reference.
Integration answers one fundamental question: how should discovery connect to authoritative information without transferring authority?
Core Distinction
Atlas provides authoritative intelligence. Navigator defines and orchestrates workflows. Beacon publishes Discovery Signals and discovery metadata. Certifier owns Certification Packages. Registry owns SREG records. Chronicle owns Chronicle Entries. Anchor owns Integrity References. Attestor owns Trust Statements.
Discovery Layer
Beacon operates as the Suite institution for Discovery & Signals. It helps users, applications, and Navigator-defined workflows locate information that exists within authoritative Suite institutions and external environments.
Signal Layer
Beacon publishes Discovery Signals and discovery metadata that identify potentially relevant information while preserving stable references, provenance, traceability, context, and the authority of originating sources.
Integration Relationship
Beacon interoperates with Suite institutions by surfacing Discovery Signals, metadata, and governed references rather than reproducing institution-owned 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
Relationship to Certifier
Beacon may publish Discovery Signals referencing Certification Packages, certification status, or related verification metadata while Certifier remains authoritative for certification and verification.
Relationship to Registry
Beacon may surface references to SREG records and Registry metadata to improve discoverability while Registry retains authority over those records and their lifecycle.
Relationship to Chronicle
Beacon may surface references to Chronicle Entries, qualifying Occurrences, and historical context, allowing discovery without replacing Chronicle's authoritative historical record.
Relationship to Anchor
Beacon may publish integrity-related Discovery Signals referencing Anchor Integrity References while Anchor retains authority for integrity preservation and its institution-owned objects.
Relationship to Navigator
Navigator may define and orchestrate workflows that require Beacon discovery. Beacon performs discovery and returns its own Discovery Signals, metadata, source references, and results without assuming Navigator's orchestration role.
Relationship to Attestor
Beacon may discover and signal the relevance of Trust Statements and related trust context. Attestor remains authoritative for Trust Statements and the Suite's trust-assessment function.
Integration Authority Boundary
Interoperability connects institutional responsibilities without collapsing them. Beacon owns its Discovery Signals and discovery metadata. Referenced canonical objects remain under the authority of their originating institutions.
Reference does not transfer authority.
Discovery Philosophy
Beacon exists to make relevant information easier to discover. Discovery does not replace authoritative intelligence, workflow orchestration, certification, registration, historical preservation, integrity preservation, or trust assessment. It connects users and workflows to them.
Beacon does not issue Certification Packages.
Beacon does not create SREG records, Chronicle Entries, Integrity References, or Trust Statements.
Beacon does not independently determine trust.
Beacon publishes Discovery Signals and discovery metadata.
Reference does not transfer authority.
Beacon does not create SREG records, Chronicle Entries, Integrity References, or Trust Statements.
Beacon does not independently determine trust.
Beacon publishes Discovery Signals and discovery metadata.
Reference does not transfer authority.
Future Interoperability
Future Beacon implementations may publish machine-readable Discovery Signals, indexes, APIs, metadata feeds, search interfaces, notification services, and workflow interfaces while preserving canonical identifiers, provenance, and authoritative references back to originating institutions and external sources.
Back to Beacon →