Beacon · Sources

Sources

Sources provide the origin, authority, context, attribution, and provenance behind information surfaced through Beacon.

Discovery becomes more valuable when users and systems can understand where information originated, which institution remains authoritative, and how it connects to Discovery Signals, canonical objects, and related sources.

Atlas Sources

Authoritative intelligence, jurisdiction information, media intelligence, profiles, and related information originating from Atlas. Atlas retains authority over the intelligence it maintains.

Certifier Sources

Certification Packages, certification status, evidence references, and verification metadata maintained by Certifier. Certifier retains certification authority. SC-CERT-2026-0001 is Beacon's first production-proven primary source.

Registry Sources

SREG records, metadata, identifiers, relationships, and lifecycle information maintained by Registry. Registry retains authority over its registered records.

Chronicle Sources

Chronicle Entries, qualifying Occurrences, source references, timelines, and preserved historical context maintained by Chronicle. Chronicle retains authority over its historical record.

Anchor Sources

Integrity References, anchoring relationships, integrity evidence, and related metadata maintained by Anchor. Anchor retains authority over its Integrity References.

Attestor Sources

Trust Statements, attestation context, supporting references, and trust metadata maintained by Attestor. Attestor retains authority over its Trust Statements.

External Sources

Government records, research publications, public datasets, media organizations, open-source repositories, and other third-party references. External discovery does not make an external source a Suite institution or Suite-authoritative object.

First Production Source

Beacon's source architecture has now been exercised in production. SC-CERT-2026-0001, the canonical Satoshium Certifier Certification Package for the Atlas Jurisdiction Record — El Salvador, is the primary source for BEAC-2026-0001.

Source Institution → Satoshium Certifier
Source Object → SC-CERT-2026-0001
Source Object Type → Canonical Certification Package
Source Version → 1.1
Observation Method → Direct review of the published canonical source
Provenance Type → Direct
Beacon Discovery Signal → BEAC-2026-0001

Registry object SREG-2026-0001, Chronicle object CHR-2026-0001, and Anchor object ANCH-2026-0001 provide related context. They are not intermediate sources in Beacon's direct provenance for this signal.

SC-CERT-2026-0001 → direct Beacon observation → BEAC-2026-0001
Open BEAC-2026-0001 →

Source Authority Boundary

Beacon owns the Discovery Signals and discovery metadata it publishes. It does not become authoritative for the sources or canonical objects those Beacon-owned objects reference.

Reference does not transfer authority.

Why Sources Matter

Information without attribution is difficult to evaluate.

Source / Canonical Object → Discovery → Discovery Signal / Metadata → Result

Sources help users understand where information originated, who maintains authority over it, and how the information can be reviewed or followed through stable references.

Source Principles

Attribution
Provenance
Transparency
Traceability
Stable References
Institutional Authority
Accessibility
Neutrality

Beacon seeks to preserve source visibility, canonical identifiers, provenance, discovery context, and institutional authority throughout the discovery process.

Source Philosophy

Beacon does not replace sources or assume their authority.

Its purpose is to help users and Suite workflows discover, organize, and navigate information while preserving its connection to the original source or institution-owned canonical object.

Discovery should illuminate origins, not obscure them.
Reference does not transfer authority.
Back to Beacon →

Discovery reveals relationships. Sources preserve origin. Authority remains with the source.