State Registry Mandate
Which registers the state must keep and how
Bundle → Layer → Finding → Questions Incomplete
3 bundles · 7 layers · 0 findings · 0 questions
mandateSource The legal basis of each obligation to keep a register
constitutionalBasis
mandates rooted directly in the constitution
statutoryMandate
mandates created by enacted statute
registerCatalogue The registers themselves as defined obligations
registerDefinition
identity, subject matter, uniqueness rules
dataScope
what each register must and must not record
operation How a mandated register must be run
registrarAssignment
who operates each register
publicFaith
reliance and presumption rules for entries
correction
rectification and appeal procedure
Note: Legacy card: layers named, findings and questions never written.
Classifiers Filled
- Family
- World Models
- Category
- Society, people and institutions
- Entry kind
- standalone-mm
- Navigation path
- NAV.SOC.POL.RGY
- Domain
- SOC.POL.RGY
- Industry
- Cross-industry
- Tags
- registrymandatesoc.pol.rgy
- Also called
- A12
What it is Derived, awaiting review
This meta-model describes which registers a polity must keep, on what legal basis, who is assigned as registrar for each, and which trust rules (public faith, correction, retention, access regime) govern them.
Note: First sentence of the legacy card introduction.
Why it exists Filled
Which registers the state must keep and how
Distinguishing features Derived, awaiting review
- It is its own model because it is the constitutional table of contents of the register landscape: every register-shaped model in the catalogue points here to prove that it exists by mandate rather than by habit, and registrar accountability is only checkable against an explicit mandate record.
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 Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
The constitution-maker and the legislature own the mandate layer; each registrarAssignment then names the operating steward per register.
Links to other meta-models Filled
references
- world.lawmaking - mandates are created, amended and repealed by enactment
- world.publicOffice - registrar assignments name offices as accountable operators
- world.organization - registrars may be bodies rather than single offices
- world.grantedRight - a mandated register whose definition, registrar and public-faith rule live here; the same pattern anchors the other register models of the catalogue
composes
- world.auditTrail - every mandate and assignment change is append-only and traceable
imports
- eli - REFERENCE: durable identifiers for the founding legal acts of each mandate
- akoma-ntoso - ALIGN: document structure of mandate and amendment texts
requires
- vr.wm-org-009
- vr.wm-pol-002
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
- mandateEnacted: a new obligation to keep a register entered into force
- registerEstablished: a mandated register was defined and opened
- registrarAssigned: an operator was designated for a register
- registrarChanged: operation of a register passed to a different registrar
- publicFaithRuleChanged: the reliance rules of a register were amended
- accessRegimeChanged: the openness default of a register was amended
- registerDecommissioned: a register was closed and its retention rule took over
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
- mandateCatalogueAccess: open access to the full list of mandated registers, registrars and trust rules
- registrarConformanceAttestation: a registrar's periodic attestation that a register is operated per its mandate
- interRegisterExchangeAgreement: agreed data flows between two mandated registers, scoped by their access regimes
- registerDirectory: the public map of registers and their registrars; omits operational and conformance detail
- registrarObligations: everything one registrar owes across its assignments; omits other registrars
- publicFaithMap: which registers and entry classes enjoy reliance presumptions; omits procedure detail
Context of use required Filled
- The catalogue of mandates is public; any restricted operational detail is opened only by owner grant through S1 and S2.
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-a12-state-registry-mandate/spec.yaml, models/docs/polity/A12-state-registry-mandate.md