Registry Mandate
Describe the evidenced public-law obligation or authority to maintain a defined register and the limits governing its registrar.
Bundle → Layer → Finding → Questions Filled
7 bundles · 14 layers · 14 findings · 42 questions
Mandate authority Proposed mandate context for mandate authority.
Mandate identity
Give the obligation a stable identity distinct from its instruments, versions and implemented registers.
Mandate identity
Give the obligation a stable identity distinct from its instruments, versions and implemented registers.
- Which authoritative identifier distinguishes this mandate from other obligations in the same legal instrument? identity
- Is this an obligation, a permitted power or a proposed mandate awaiting legal authority? classification
- What evidence establishes that this record describes a mandate rather than a voluntary list? provenance
Legal basis chain
Link the basis and implementing instruments without assuming every mandate originates directly in a constitution.
Legal basis chain
Link the basis and implementing instruments without assuming every mandate originates directly in a constitution.
- Which competent issuer and provision authorize the duty to maintain this register? authority
- Which implementing rules depend on the enabling provision and what limits constrain them? relationship
- Which source version and interpretation support the asserted mandate wording? evidence
Mandate applicability Proposed mandate context for mandate applicability.
Jurisdiction and subject limits
Represent legal reach independently of the location of registry infrastructure.
Jurisdiction and subject limits
Represent legal reach independently of the location of registry infrastructure.
- Which jurisdiction and territorial exceptions delimit this mandate? spatial
- Which subject categories fall within the mandate and which are expressly excluded? constraint
- How are overlapping or contested mandates represented pending competent resolution? exception
Effective scope and change
Keep legal-effect assertions separate from recording time and operational availability.
Effective scope and change
Keep legal-effect assertions separate from recording time and operational availability.
- When does each part of the mandate take effect and what commencement evidence supports that date? temporal
- What is the evidenced current status, including partial suspension or unresolved applicability? state
- Which amendment, repeal or saving provision changes this mandate without erasing prior applicability? lifecycle
Required register definition Proposed mandate context for required register definition.
Register purpose and boundaries
Describe the required register as a defined obligation, with optional links to operational instances.
Register purpose and boundaries
Describe the required register as a defined obligation, with optional links to operational instances.
- What public purpose does the mandate assign to the register? definition
- Which register implementations discharge which parts of the mandate? composition
- What distinguishes a required register from a mirror, index or derived publication? validation
Mandated information and identifiers
Capture data and uniqueness requirements as constraints; entry validation and matching remain external.
Mandated information and identifiers
Capture data and uniqueness requirements as constraints; entry validation and matching remain external.
- Which information classes are required, permitted or prohibited for the stated purpose? requirement
- Which identifier and uniqueness rules are required within the register scope? identity
- Which collection or reuse proposals exceed the evidenced data scope? privacy
Registrar stewardship Proposed mandate context for registrar stewardship.
Registrar designation
Record the accountable role and designation evidence independently of infrastructure custody.
Registrar designation
Record the accountable role and designation evidence independently of infrastructure custody.
- Which office or body is accountable for each mandated register scope? ownership
- Which designation interval applies when a registrar changes or an acting arrangement begins? temporal
- What proves the designation and how is an unresolved vacancy recorded? evidence
Delegation and reserved powers
Distinguish designated responsibilities from delegated or reserved powers; no system role creates legal competence.
Delegation and reserved powers
Distinguish designated responsibilities from delegated or reserved powers; no system role creates legal competence.
- Which powers may the registrar exercise, delegate or only refer to another authority? authority
- What territorial, temporal or subject limits constrain a delegated power? constraint
- What oversight evidence is required to assess delegated performance? quality
Legal effects and remedies Proposed mandate context for legal effects and remedies.
Qualified reliance rules
Treat reliance and legal effect as evidenced rules for specified entry classes, never as a consequence of database presence.
Qualified reliance rules
Treat reliance and legal effect as evidenced rules for specified entry classes, never as a consequence of database presence.
- Which legal effects or evidential presumptions attach to each entry class? decision
- Which defects or exceptions limit reliance on an entry? exception
- What information must accompany a copy or extract to avoid overstating its legal effect? interoperability
Correction and review requirements
Reference correction and challenge rules while keeping adjudication and entry mutation outside the mandate record.
Correction and review requirements
Reference correction and challenge rules while keeping adjudication and entry mutation outside the mandate record.
- Which authority and procedure can correct each category of register error? process
- Who may request correction or review and under what standing requirements? access
- Which time limits, review routes and interim effects apply to a challenge? temporal
Disclosure and exchange Proposed mandate context for disclosure and exchange.
Access and protected information
Separate public mandate metadata, register inspection, certified extracts and restricted personal data.
Access and protected information
Separate public mandate metadata, register inspection, certified extracts and restricted personal data.
- Which audiences may access which information and in which form? access
- What restrictions and redactions apply even when a register has a public purpose? privacy
- How are disclosure exceptions and refusals justified and reviewed? exception
Exchange and service obligations
Represent authorized exchanges, service conditions and fees as obligations rather than executable integrations.
Exchange and service obligations
Represent authorized exchanges, service conditions and fees as obligations rather than executable integrations.
- Which recipient registers or agencies may receive data for which stated purposes? relationship
- Which accessibility, fee and service conditions apply to obtaining registry information? requirement
- Which safeguards constrain cross-register transfer and onward use? security
Continuity and assurance Proposed mandate context for continuity and assurance.
Preservation and transition
Keep mandate history and register preservation duties distinct; closure does not decide record disposal.
Preservation and transition
Keep mandate history and register preservation duties distinct; closure does not decide record disposal.
- Which schedules govern mandate evidence and which separately govern registry records? retention
- What continuity and transfer duties apply when the mandate or registrar is replaced? lifecycle
- What permits disposal or continued preservation after the register closes? constraint
Evidence and alignment assurance
Make coverage, source limitations and mapping loss explicit; structure validation does not certify legality.
Evidence and alignment assurance
Make coverage, source limitations and mapping loss explicit; structure validation does not certify legality.
- Which observations support an assertion that a register complies with its mandate? provenance
- Which obligations remain unassessed or disputed in the latest review? validation
- Which legal-document and provenance mappings preserve meaning and where is information lost? interoperability
Classifiers Filled
- Family
- World Models
- Category
- Society, people and institutions
- Entry kind
- entity
- Navigation path
- NAV.SOC.POL.RGY
- Domain
- SOC.POL.RGY
- Industry
- Cross-industry
- Tags
- registrymandatesoc.pol.rgy
- Also called
- A12
What it is Filled
One persistent registry mandate record, qualified by jurisdiction, legal basis and effective scope. It records register definition, registrar designation, powers and governing rule references. It neither constitutes the operative register nor enacts or executes law. The catalogue of many mandates is a projection.
In scope
- Mandate identity, legal-source citations, asserted authority and uncertainty
- Territorial, subject and temporal applicability of the mandate
- Defined register purpose, data classes and identity rules as obligations
- Registrar designation, delegated powers and accountability requirements
- Qualified reliance, correction, disclosure, retention and transition rule references
Out of scope
- Register entries, registration transactions, database and registry runtime operations belong to the register master and WM-XCT-013
- Lawmaking, public-office and organization lifecycles remain external
- Correction applications, appeals, court decisions and enforcement execution remain separate cases
- Private voluntary lists without a public-law mandate are outside this model; no claim that all registries need a statutory mandate
- Operational identity resolution, synchronization, disclosure enforcement and disposal execution
- Weapons, detention and controlled-item registers beyond their abstract mandate and policy references
Why it exists Filled
Describe the evidenced public-law obligation or authority to maintain a defined register and the limits governing its registrar.
Distinguishing features Derived, awaiting review
- Unlike WM-XCT-013 Registry Pattern: The frozen incoming REFERENCE leaves mandate issuance authority, jurisdiction and lifecycle here. The register master owns entries and operations. A register may cite multiple mandates; this record may bind multiple implementation references without owning them.
- Unlike WM-POL-002 Lawmaking Process: Carry provision and instrument references; do not reproduce enactment workflow. A local assertion of effective status does not enact, repeal or interpret legislation authoritatively.
- Unlike WM-ORG-009 Public Office and WM-ORG-001 Organization: Store evidenced registrar assignment scope and intervals; reference the office or body master rather than owning appointments, staff or institutional lifecycle.
- Unlike WM-POL-017 Administrative Procedure / Case: Store correction and review pathways as governing requirements. Individual disputes, applications and decisions remain external case records.
- Unlike Legacy A12 and unreviewed supplement: Retain the mandate-versus-register distinction; reject universal statutory anchoring, blanket openness, date-only identity, unrestricted append-only personal data and inherited conformance claims.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- A local metadata write cannot enact a mandate, appoint a registrar, correct an entry or determine a legal remedy
- Require local mandate identity, custodian and source references or explicit pending-evidence state; never advertise pending authority as established
- Deny unapproved disclosure of evidence payloads.
May
- Record mandate basis: Proposed, unimplemented local operation. Prepare a local mandate identity and basis assertion.
- Record evidenced scope revision: Proposed, unimplemented local operation. Append a local version describing an evidenced legal change.
- Link registrar designation: Proposed, unimplemented local operation. Record an externally evidenced designation or delegation assertion.
- Assess evidence coverage: Proposed, unimplemented local operation. Compare supplied evidence with the recorded obligation list using a qualified profile.
- Prepare authorized mandate view: Proposed, unimplemented local operation. Construct a local preview of mandate metadata under an approved access profile.
- Record continuity requirements: Proposed, unimplemented local operation. Append a local succession or retirement proposal linked to governing evidence.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Derived, awaiting review
- Apply purpose-limited views and minimum personal data.
- Retain the mandate-versus-register distinction; reject universal statutory anchoring, blanket openness, date-only identity, unrestricted append-only personal data and inherited conformance claims.
Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.
Owners Filled
Steward
Identify the competent public authority and mandate evidence custodian by role and stable reference
Roles
- Competent issuing authority
- Establish mandate and amendment authority outside the local record system
- Mandate evidence custodian
- Maintain stable local identity, source references and version continuity
- Registrar
- Supply designation and scoped accountability evidence without expanding powers
- Legal reviewer
- Assess applicable legal instruments, conflicts, exceptions and remedies
- Access and records officer
- Approve views, schedule bindings, lawful holds and disposition evidence
Links to other meta-models Filled
references
- WM-XCT-013 - Reciprocal instance binding for the frozen incoming registry-to-mandate REFERENCE. Register operations and entries stay in the target; do not infer mandatory runtime dependencies. Pin and validate the binding before operational integration.
- WM-POL-002 - Candidate binding to lawmaking and enactment records; local mandate assertions retain legal-source references only. Pin and validate the binding before operational integration.
- WM-ORG-009 - Candidate public-office master binding for accountable registrar role; appointments and office lifecycle remain external. Pin and validate the binding before operational integration.
- WM-ORG-001 - Candidate organization master binding when the registrar is a body; no institutional lifecycle copied. Pin and validate the binding before operational integration.
- WM-POL-017 - Candidate case reference for correction or review proceedings; no adjudication workflow owned here. Pin and validate the binding before operational integration.
- WM-XCT-035 - Candidate retention/disposition rule binding; disposal execution belongs to the authorized records service. Pin and validate the binding before operational integration.
- WM-XCT-004 - Candidate access-audit evidence link; audit event and log lifecycle stay external. Pin and validate the binding before operational integration.
aligned
- European Legislation Identifier - Optional legal-instrument URI and metadata mapping; the mandate ID is not automatically the act URI. Pin and validate the binding before operational integration.
- Akoma Ntoso 1.0 - Optional provision and document metadata mapping, without wildcard imports or conformance claims. Pin and validate the binding before operational integration.
- PROV-O - Optional provenance mapping for assertion source, agent and revision; attribution does not establish legal authority. Pin and validate the binding before operational integration.
neighbor
- WM-XCT-013 Registry Pattern - The frozen incoming REFERENCE leaves mandate issuance authority, jurisdiction and lifecycle here. The register master owns entries and operations. A register may cite multiple mandates; this record may bind multiple implementation references without owning them.
- WM-POL-002 Lawmaking Process - Carry provision and instrument references; do not reproduce enactment workflow. A local assertion of effective status does not enact, repeal or interpret legislation authoritatively.
- WM-ORG-009 Public Office and WM-ORG-001 Organization - Store evidenced registrar assignment scope and intervals; reference the office or body master rather than owning appointments, staff or institutional lifecycle.
- WM-POL-017 Administrative Procedure / Case - Store correction and review pathways as governing requirements. Individual disputes, applications and decisions remain external case records.
- Legacy A12 and unreviewed supplement - Retain the mandate-versus-register distinction; reject universal statutory anchoring, blanket openness, date-only identity, unrestricted append-only personal data and inherited conformance claims.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier with namespace and revision
- Governed stable IRI with version and provenance
- Local opaque UUID or ULID with reconciliation state
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 Filled
- Record mandate basis: Proposed, unimplemented local operation. Prepare a local mandate identity and basis assertion.
- Record evidenced scope revision: Proposed, unimplemented local operation. Append a local version describing an evidenced legal change.
- Link registrar designation: Proposed, unimplemented local operation. Record an externally evidenced designation or delegation assertion.
- Assess evidence coverage: Proposed, unimplemented local operation. Compare supplied evidence with the recorded obligation list using a qualified profile.
- Prepare authorized mandate view: Proposed, unimplemented local operation. Construct a local preview of mandate metadata under an approved access profile.
- Record continuity requirements: Proposed, unimplemented local operation. Append a local succession or retirement proposal linked to governing evidence.
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
- PROV-O: The PROV Ontology
Context of use required Filled
- UK land legislation is used as a bounded structural example, not a current-law opinion or a rule for other registers
- UN business and civil-registration guidance is nonbinding and sector-specific
- GDPR examples are EU-specific; applicability, exemptions and local access regimes must be independently reviewed
Sources Filled
- UNCITRAL Legislative Guide on Key Principles of a Business Registry - United Nations Commission on International Trade Law
- Land Registration Act 2002 - UK Parliament
- Guidelines on the Legislative Framework for Civil Registration, Vital Statistics and Identity Management Systems - United Nations Statistics Division
- General Data Protection Regulation - European Parliament and Council of the European Union
- Council conclusions on the European Legislation Identifier - Council of the European Union
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Akoma Ntoso Version 1.0. Part 1: XML Vocabulary - OASIS
Open questions
- Verify inaccessible full texts, current consolidated versions, legal applicability, source licensing and claim-level support before any canonical promotion.
- Develop qualified jurisdiction and sector profiles, including contested authority, partial repeal, public-data exceptions and archival continuity.
- Implement and test nested schemas, pinned bindings and mappings with the proposed negative fixtures.
- Restore independent external review before promotion beyond reviewable-draft.
- Independent external provider review is absent; local no-tools self-audit is not independent review
- Current consolidated legal versions, full inaccessible texts, language and licensing checks remain incomplete
- Nested instance schemas, profile-specific required fields, legal-effect evaluation and executable conformance fixtures are not supplied
- Country-specific constitutional hierarchy, fee rules, appeal periods, archival schedules and cross-border recognition need qualified research
- Sensitive-sector, customary-law and non-European mandate profiles are not validated
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-pol-013-registry-mandate/spec.yaml