← Catalogue
World Models · legacy example

State Registry Mandate

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. 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.

AI YAMLAGENTS.mdSource
IDworld.a12-state-registry-mandate
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainpolity
Tagsstate, registry, mandate
Data structure

Bundles and layers

Bundle

mandateSource

The legal basis of each obligation to keep a register

Layers

constitutionalBasis`: mandates rooted directly in the constitution · `statutoryMandate`: mandates created by enacted statute

Bundle

registerCatalogue

The registers themselves as defined obligations

Layers

registerDefinition`: identity, subject matter, uniqueness rules · `dataScope`: what each register must and must not record

Bundle

operation

How a mandated register must be run

Layers

registrarAssignment`: who operates each register · `publicFaith`: reliance and presumption rules for entries · `correction`: rectification and appeal procedure

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.lawmaking` (A10): mandates are created, amended and repealed by enactment
  • REFERENCE `world.publicOffice` (A11): registrar assignments name offices as accountable operators
  • REFERENCE `world.organization` (O1): registrars may be bodies rather than single offices
  • REFERENCE `world.grantedRight` (R5): a mandated register whose definition, registrar and public-faith rule live here; the same pattern anchors the other register models of the catalogue
  • MIX-IN `world.auditTrail` (S4): every mandate and assignment change is append-only and traceable
  • imports: eli (REFERENCE): durable identifiers for the founding legal acts of each mandate
  • imports: akoma-ntoso (ALIGN): document structure of mandate and amendment texts

Canon, patches & standards

  • REFERENCE `world.lawmaking` (A10): mandates are created, amended and repealed by enactment
  • REFERENCE `world.publicOffice` (A11): registrar assignments name offices as accountable operators
  • REFERENCE `world.organization` (O1): registrars may be bodies rather than single offices
  • REFERENCE `world.grantedRight` (R5): a mandated register whose definition, registrar and public-faith rule live here; the same pattern anchors the other register models of the catalogue
  • MIX-IN `world.auditTrail` (S4): every mandate and assignment change is append-only and traceable
  • imports: eli (REFERENCE): durable identifiers for the founding legal acts of each mandate
  • imports: akoma-ntoso (ALIGN): document structure of mandate and amendment texts

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `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

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The constitution-maker and the legislature own the mandate layer; each registrarAssignment then names the operating steward per register. The catalogue of mandates is public; any restricted operational detail is opened only by owner grant through S1 and S2.

Existing assembly

Objects, relationships, events and projections

Objects

  • `registryMandate`: an obligation of the polity to keep a register; key attributes: legalBasisRef, subjectMatter, since, status
  • `registerDefinition`: the defined register an obligation calls for; key attributes: name, keyedBy, uniquenessRule, mandateRef
  • `registrarAssignment`: the designation of an operator for a register; key attributes: registerRef, registrarRef, since, terms
  • `publicFaithRule`: the reliance rule for entries of a register; key attributes: presumption, goodFaithProtection, exceptions
  • `retentionRule`: how long and in what form entries must be kept; key attributes: period, archivalForm, disposalRule
  • `correctionProcedure`: how erroneous entries are rectified; key attributes: initiators, evidenceRequired, appealPath
  • `accessRegime`: the default openness of a register; key attributes: publicByDefault, gradedClasses, selfAccessRule

Relationships

  • `registryMandate` -> establishedBy -> `enactmentRef` (N:1): every mandate traces to a constitutional provision or enactment in A10
  • `registerDefinition` -> mandatedBy -> `registryMandate` (N:1): a register exists only under an explicit mandate
  • `registrarAssignment` -> assigns -> `registerDefinition` (N:1): each assignment designates the operator of one register
  • `registrarAssignment` -> namesRegistrar -> `officeRef` (N:1): the registrar is an office of A11 or a body of O1
  • `publicFaithRule` -> governs -> `registerDefinition` (N:1): reliance rules attach per register
  • `correctionProcedure` -> appliesTo -> `registerDefinition` (N:1): rectification paths attach per register
  • `accessRegime` -> constrains -> `registerDefinition` (N:1): the openness default attaches per register

Events

  • `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

Projections

  • `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