Beacon · Discovery Signal Architecture

Authority & Reference Model

The Authority & Reference Model defines precisely what Beacon owns, what Beacon may reference, what authority remains with other Suite institutions and external sources, and what Beacon must never claim merely because it discovered or referenced information.

Reference does not transfer authority.

Purpose

The model answers:

What does Beacon own?
What may Beacon reference?
Who continues to own the referenced object?
What authority, if any, does the reference carry into Beacon?

Core Rule

A Beacon Discovery Signal may point to an authoritative object without becoming that object and without acquiring the originating institution's authority.

Discovery → connection
Reference → attribution
Authority → remains with its institutional owner

Beacon Ownership

Beacon owns the objects and institutional determinations that belong to its Discovery & Signals responsibility.

  • Beacon Discovery Signals
  • Beacon-assigned BEAC-YYYY-NNNN identifiers
  • Discovery Metadata attached to Beacon signals
  • Beacon lifecycle state for Beacon signals
  • Beacon publication state for Beacon signals
  • Beacon version and supersession information for Beacon signals
  • Beacon provenance describing Beacon's observation
  • Beacon-governed relationships represented by its signals
Beacon may authoritatively describe its own object and its own institutional actions.

Beacon Does Not Own

Beacon does not acquire ownership of:

  • Atlas Authoritative Intelligence
  • Certifier Certification Packages
  • Registry SREG records
  • Chronicle Entries
  • Anchor Integrity References
  • Attestor Trust Statements
  • Navigator Workflow Definitions or orchestration authority
  • External records, publications, datasets, or source assertions

Reference Ownership

Beacon owns the fact that its Discovery Signal contains a reference. It does not own the referenced object.

Beacon owns → the reference relationship as represented in BEAC-2026-0001

Source institution owns → the canonical object identified by that reference

Suite Authority Map

InstitutionInstitution-Owned Responsibility / ObjectBeacon MayBeacon May Not
AtlasAuthoritative IntelligenceDiscover, reference, attribute, preserve discovery contextReplace or recreate Atlas authority
CertifierCertification PackageReference certification information and identifiersCertify merely by discovery
RegistrySREGReference registered records and source-owned statusRegister or alter Registry standing
ChronicleChronicle EntryReference qualifying preserved historical objectsDetermine Chronicle preservation authority
AnchorIntegrity ReferenceReference integrity objects and attributable resultsPerform or claim Anchor authority by reference
BeaconDiscovery Signal / MetadataCreate, validate, version, publish, supersede, resolve, withdraw its own signalsUse discovery to absorb another institution's authority
AttestorTrust StatementReference a Trust StatementConvert a Trust Signal into a Trust Statement
NavigatorWorkflow Definition / OrchestrationParticipate in and reference Navigator-directed workflowsRedefine Navigator workflow authority
Atlas

Authoritative Intelligence

Beacon may create a Jurisdiction or Information Discovery Signal based on Atlas Authoritative Intelligence.

Atlas owns → Authoritative Intelligence
Beacon owns → Discovery Signal describing the discovery

Beacon does not make Atlas intelligence authoritative. Atlas supplies that authority within its own institutional role.

Certifier

Certification Authority

Beacon may discover and reference a Certification Package, including through a Certification Signal.

Certification Signal ≠ Certification Package

The existence of a Beacon Certification Signal does not independently certify the subject.

Registry

Registration Authority

Beacon may discover an SREG and preserve its identifier, relationship, and source-attributed status.

Registry Signal ≠ SREG

Beacon cannot create Registry standing or change an SREG lifecycle by referencing it.

Chronicle

Historical Authority

Beacon may discover and reference a Chronicle Entry.

Historical Signal ≠ Chronicle Entry

Discovery does not itself establish Chronicle Preservation Eligibility or historical institutional standing.

Anchor

Integrity Authority

Beacon may reference an Anchor Integrity Reference and preserve the provenance of that observation.

Integrity Signal ≠ Integrity Reference

Beacon does not perform Anchor's integrity function merely by discovering its output.

Attestor

Trust Authority

Beacon may discover and reference an Attestor Trust Statement.

Trust Signal ≠ Trust Statement

Beacon's discovery classification must never be interpreted as a substitute trust determination.

Navigator

Workflow Authority

Beacon may operate within a Navigator-directed workflow and preserve the workflow reference as context or provenance.

Navigator owns → Workflow Definition / Orchestration
Beacon owns → its discovery output and Discovery Signals
External

External Source Authority

External sources retain their own identity, provenance, authorship, status, and whatever authority they legitimately possess outside the Suite.

External discovery ≠ Suite authority

Beacon may attribute an external source. It must not imply that inclusion converts the source into a Suite-authoritative object.

Three-Layer Reference Model

Layer 1 — Referenced Object
The source or canonical object retains its native identity and institutional authority.

Layer 2 — Beacon Reference
Beacon preserves the object's identifier, institution, object type, source location, and relationship where applicable.

Layer 3 — Beacon Discovery Signal
Beacon owns the signal that records why the referenced object is discoverably relevant.

Identity Preservation

Referenced objects retain their native identifiers.

BEAC-2026-0001 → Beacon Discovery Signal
SC-CERT-2026-0001 → Certifier Certification Package

The first production signal preserves SC-CERT-2026-0001 as a Certifier-owned object. Beacon does not rename or absorb it as a Beacon object.

Object-Type Preservation

Beacon should preserve the source object's actual institutional type when known.

Source Object Type → Canonical Certification Package
Beacon Signal Type → Certification

These fields are related, but they are not interchangeable.

Authority Attribution

When Beacon repeats or exposes an institution-owned determination, the determination should remain attributable to that institution.

Correct → Registry reports SREG-2026-0001 as [source-owned status].

Incorrect → Beacon independently assigns Registry standing to SREG-2026-0001.

Beacon may report what the source says. It must distinguish that from what Beacon itself determines.

Beacon-Owned Determinations

Beacon may determine matters within its own institutional domain, including:

  • Whether a Beacon Discovery Signal exists
  • Its Signal Type
  • Its Beacon lifecycle state
  • Its Beacon publication state
  • Its Discovery Metadata
  • Its provenance record
  • Whether it conforms to Beacon Validation
  • Its Beacon version/supersession relationships

Source-Owned Determinations

Beacon must attribute determinations owned elsewhere, including:

  • Atlas intelligence authority
  • Certifier certification decisions
  • Registry registration standing
  • Chronicle preservation decisions
  • Anchor integrity determinations
  • Attestor trust determinations
  • Navigator workflow definitions
  • External source assertions and source-native status

Reference Does Not Equal Endorsement

A Beacon reference means that the source or object is relevant to the discovery represented by the signal.

It does not automatically mean Beacon:

  • endorses the source
  • agrees with every source assertion
  • certifies the source
  • trusts the source
  • guarantees source correctness
  • adopts the source's institutional authority

Reference Does Not Equal Truth

Beacon can accurately record that a source made an assertion even if that assertion later proves incorrect.

Beacon truth claim → “This is what was observed from this source at this time.”

Not automatically → “The underlying assertion is universally true.”

Reference Does Not Equal Validation

Beacon Validation tests whether the Discovery Signal conforms to Beacon production rules.

Valid Beacon signal ≠ validated truth of every referenced source claim

Reference Integrity Requirements

A production reference should preserve, when applicable:

  • Referenced institution or source
  • Native identifier
  • Native object type
  • Source location
  • Relationship to the Beacon signal
  • Observation provenance
  • Source-owned status only with attribution
A reference should contain enough information to identify what is being referenced without reconstructing the referenced object inside Beacon.

No Canonical Duplication

Beacon should not copy another institution's canonical object into a Beacon structure and then treat the copy as independently authoritative.

Reference the canonical object.
Preserve enough context for discovery.
Return to the source for source authority.

No Authority Laundering

Information must not gain an appearance of greater institutional authority merely because Beacon discovered, indexed, published, or linked to it.

Discovery visibility must never be mistaken for institutional elevation.

External Source Boundary

Beacon may preserve external information as discovery evidence or context while clearly distinguishing it from Suite-owned canonical authority.

External Source
↓ observed and attributed
Beacon Discovery Signal

External Source remains external.

If later Suite institutions certify, register, chronicle, anchor, or attest something related to that source, those are separate institutional actions producing separate institution-owned objects.

Source Changes

If a referenced source changes status, content, location, or availability, Beacon may record the new observation.

Beacon may update its understanding of the reference.
Beacon may not rewrite the source institution's authority.

Broken or Unavailable References

Loss of source availability does not automatically erase a Discovery Signal or its historical provenance.

Preserve historical reference.
Record later availability condition.
Apply Beacon lifecycle/version rules when appropriate.

Conceptual Reference Structure

canonical_reference:
  institution
  identifier
  object_type
  source_location
  relationship
  observed_status
  attribution

This is an architectural representation, not a frozen machine-readable property model.

Relationship to Provenance

Authority tells Beacon whose determination it is. Provenance tells Beacon how the referenced information was observed.

Authority → ownership of meaning / determination
Provenance → lineage of discovery

Relationship to Relationships

The Authority Model establishes who owns the endpoints. The Relationship Model defines how Beacon represents governed connections between them.

Authority → endpoint ownership
Relationships → governed connection semantics

What Is Now Established

  • Beacon owns Discovery Signals and Discovery Metadata
  • Beacon owns Beacon lifecycle, publication, validation, provenance, and version determinations about its own signals
  • Referenced canonical objects remain owned by their originating institutions
  • External sources remain external
  • Native source identifiers and object types must be preserved
  • Source-owned status and determinations must remain attributed
  • A Beacon reference does not equal endorsement
  • A Beacon reference does not equal truth
  • A Beacon reference does not equal certification, registration, integrity verification, or trust
  • Beacon must not duplicate another institution's canonical authority
  • Discovery visibility must not be used to launder or elevate authority

What Remains Intentionally Open

  • Exact machine-readable canonical-reference property names
  • Formal authority-attribution field vocabulary
  • Reference resolution behavior
  • Rules for inaccessible or restricted canonical objects
  • External-source authority classifications, if any become necessary
  • Reference correction mechanics
  • Reference-resolution automation
  • Whether some specialized Signal Types require specific source institutions
The institutional authority boundary is defined and production-exercised. These remaining questions concern machine implementation or future specialized cases.

Governing Rule

Beacon may discover.
Beacon may reference.
Beacon may attribute.
Beacon may preserve provenance.
Beacon may create its own Discovery Signal.

Beacon may not acquire another institution's authority merely by doing so.

Reference does not transfer authority.

First Production Authority Exercise

The Authority & Reference Model has now been exercised through BEAC-2026-0001.

Beacon-Owned Object → BEAC-2026-0001
Primary Referenced Object → SC-CERT-2026-0001
Referenced Institution → Satoshium Certifier
Referenced Object Type → Canonical Certification Package
Referenced Certification Condition → Issued · Active · Operational
Underlying Subject → Atlas Jurisdiction Record — El Salvador
Subject Authority → Satoshium Atlas
Related Registry Object → SREG-2026-0001
Related Chronicle Object → CHR-2026-0001
Related Integrity Object → ANCH-2026-0001

Certifier retains authority over the certification decision, class, lifecycle, and status of SC-CERT-2026-0001. Atlas retains authority over the underlying jurisdiction intelligence. Beacon owns only its Discovery Signal, discovery metadata, provenance, lifecycle, publication state, validation determinations, version information, and Beacon-side relationships and references.

Current Status

Beacon Status → Operational · September 2026
Authority & Reference Model → Defined and production-exercised
First Production Authority Review → PASS
Primary Referenced Object → SC-CERT-2026-0001
Certifier Authority → Preserved
Atlas Subject Authority → Preserved
Beacon Authority Boundary → Preserved
Relationship Model → Defined
First Production Discovery Signal → BEAC-2026-0001 · Active · Published

A reference can carry meaning across institutions without carrying ownership with it.