Beacon Records is the human-facing register of published canonical Discovery Signals. It provides a stable place to locate Beacon production objects, understand their current institutional state, and follow each record listing to the authoritative individual Beacon record.
Beacon Records answers:
Beacon Records is a public index over Beacon-owned canonical objects.
Beacon Records is intended to expose Beacon Discovery Signals whose Publication State is Published.
Draft, internal, restricted, or otherwise Unpublished signals should not appear in Beacon Records by default.
The Discovery Signal is the institution-owned Beacon production object.
A Record listing is the human-facing index representation used to locate and summarize a published Discovery Signal.
Published Discovery Signals are expected to resolve through stable record paths using their BEAC identifiers.
The first production Discovery Signal now resolves at this stable path, establishing the initial public individual-record pattern for Beacon.
Each public Record listing should expose enough information to identify and distinguish the Discovery Signal without reproducing the entire canonical record.
| Field | Records Purpose |
|---|---|
| BEAC Identifier | Stable canonical identity of the Discovery Signal. |
| Subject / Title | Human-readable indication of what the signal concerns. |
| Signal Type | Primary Beacon discovery classification. |
| Lifecycle State | Current institutional state: Active, Superseded, Resolved, or Withdrawn as applicable. |
| Publication State | Confirms that the public representation is Published. |
| Current Version | Identifies the current governed representation. |
| Source / Source Institution | Provides concise source attribution when appropriate. |
| Published At | Identifies when the Beacon representation became public. |
| Record Link | Resolves to the individual Discovery Signal representation. |
Beacon Records may provide concise discovery context to help users understand why a signal is relevant.
Record summaries should not become independent copies of the canonical Discovery Signal.
Beacon Records should distinguish current published signals from published signals whose lifecycle has later changed.
Active Published signals should be readily discoverable as current Beacon objects.
Superseded Published signals should remain traceable and identify the current replacement when one exists.
Resolved Published signals may remain discoverable as part of Beacon's institutional history.
Previously published Withdrawn signals should preserve the historical fact of publication and governed withdrawal to the extent permitted.
Beacon Records should identify the current version of each listed Discovery Signal without turning every historical version into a separate canonical record.
Records-level source information should preserve attribution without implying that Beacon owns the source object.
Beacon Records indexes Beacon Discovery Signals, even when those signals reference other Suite institutions.
Beacon Records catalogs the Beacon signal. Certifier continues to own the Certification Package, and Registry continues to own the SREG.
Record listings should expose the primary Beacon Signal Type so users can distinguish discovery categories.
Source Object Type remains distinct from Signal Type.
As production volume grows, Beacon Records may support human-facing filtering or organization by governed fields such as:
Initial ordering may be simple and deterministic, such as canonical identifier or publication chronology.
Future search may help locate published signals by subject, identifier, type, or source.
Lifecycle state affects how the signal is represented, not necessarily whether its historical publication remains discoverable.
Unpublished Discovery Signals should not appear in Beacon Records by default.
A valid signal may remain outside Beacon Records when publication or continuing public representation is restricted by governance.
Inclusion in Beacon Records establishes public discoverability within Beacon.
It does not independently establish:
Record listings should remain consistent with the canonical Discovery Signals they index.
If a Record summary is incorrect while the underlying canonical record is correct, the index representation should be corrected without changing the Discovery Signal unnecessarily.
If the Discovery Signal itself changes materially, Versioning & Supersession governs the canonical change and Beacon Records should reflect the resulting current state.
Architectural only. The Record listing is an index representation, not a new canonical object or frozen machine-readable schema.
Beacon Records now contains its first published production Discovery Signal.
Satoshium Beacon identified an active Operational certification for the Atlas Jurisdiction Record — El Salvador, represented by Satoshium Certifier object SC-CERT-2026-0001.
View Beacon Record →Publication determines whether a Discovery Signal is eligible to appear in Beacon Records.
Beacon Records reflects the current version while preserving access to governed historical context through the individual record.
Beacon Records catalogs Beacon-owned objects and preserves the ownership of all referenced endpoints.
Records representation should remain consistent with the validated canonical Discovery Signal it summarizes.
Beacon Records is in active production use as part of an Operational Beacon institution. The first controlled production operation, production evidence preservation, and post-operation review are complete.