Registry Federation & Mirroring
Reference-not-copy rules between registers
Bundle → Layer → Finding → Questions Incomplete
3 bundles · 6 layers · 0 findings · 0 questions
authority Who is authoritative for which facts
authorityScope
declared subject domains per register, no overlaps unresolved
precedence
which register wins when declarations collide, and how conflicts are settled
linkage Pointing instead of copying
referenceRules
what a cross-register reference must carry to stay resolvable
resolutionRouting
where a consumer resolves a given reference, including fallbacks
mirroring Derived copies under discipline
mirrorProvisioning
when a mirror may exist, its scope and its marking as non-authoritative
freshnessAndDrift
staleness budgets, drift detection and reconciliation duties
Note: Legacy card: layers named, findings and questions never written.
Classifiers Filled
- Family
- World Models
- Category
- Cross-cutting context
- Entry kind
- pattern
- Navigation path
- NAV.XCT.FED
- Domain
- XCT.FED
- Industry
- Cross-industry
- Tags
- registryfederationxct.fed
- Also called
- R6
What it is Derived, awaiting review
The reference-not-copy fabric between registers: which register is authoritative for what, how entries in one register point into another, and under what freshness and drift rules derived mirrors may exist at all.
Note: First sentence of the legacy card introduction.
Why it exists Filled
Reference-not-copy rules between registers
Distinguishing features Missing, in the backlog
Not described yet. This gap is in the card backlog.
What robots and AI may and may not do Missing, in the backlog
Not described yet. This gap is in the card backlog.
Moral aspects Derived, awaiting review
- Access to routes, mirrors and drift data is granted via the S1/S2 access and consent models and audited via S4.
Owners Filled
Steward
Ownership is joint: the registrars party to each federation link own the link, its declarations and its routes, while each mirrored fact remains owned by its authoritative source register.
Links to other meta-models Filled
references
- world.registry - every federated endpoint is a register of the pattern, and authority scopes are expressed over its entry domains
- world.identityRegister - registrar parties to agreements resolve to anchored identities
- world.mandate - a registrar's capacity to enter federation agreements derives from its mandate
composes
- world.eventRegister - mirrors refresh by replaying source event logs, and drift checks compare against sealed checkpoints
- world.audit - provisioning, refresh and reconciliation acts carry the audit facet
imports
- mu-arch-018 - ALIGN: the reference-not-copy doctrine this model operationalizes
- mufp - ALIGN: federation exchange semantics for resolution and synchronization
requires
- vr.wm-per-002
- vr.wm-pol-013
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Derived, awaiting review
- federationEstablished: two registrars concluded an agreement and linked their registers
- authorityDeclared: a register's authoritative scope was declared or adjusted within the federation
- mirrorProvisioned: a derived copy was created under a freshness policy and marked non-authoritative
- mirrorRefreshed: a mirror was brought up to date from its source
- driftDetected: comparison found a mirror diverging from its source beyond tolerance
- driftReconciled: a detected divergence was resolved in favor of the authoritative source
- federationSuspended: a link was taken out of service and its routes disabled
Legacy events listed as state transitions.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- federationAgreement: the registrars' mutual terms for linking registers, declaring authority and honoring references
- mirrorProvisionContract: the conditions under which a consumer may hold a mirror, including scope, marking and refresh duties
- freshnessServiceLevelContract: the staleness budget and refresh guarantees for a mirror class
- resolutionServiceContract: terms of the reference resolution service offered to federation consumers
- federationMapView: the topology of registers, links and authority scopes; omits all entry-level content
- mirrorHealthView: lag, last refresh and open drift per mirror; omits mirrored content itself
- consumerResolutionView: where to resolve which reference class; omits agreement terms and internal routes
Context of use required Filled
- Access to routes, mirrors and drift data is granted via the S1/S2 access and consent models and audited via S4.
Sources Missing, in the backlog
Not described yet. This gap is in the card backlog.
Open questions
- Superseded by a researched world model? Map this legacy card to its successor or retire it.
Machine files
Provenance
legacy MMAS card (world-models v0.2) · legacy
Built from: models/world-r6-registry-federation-and-mirroring/spec.yaml, models/docs/registries-ledgers/R6-registry-federation-and-mirroring.md