# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T15:19:52Z", "synthesisSha256": "e87a2dd12f682d5a0ac455a2ae99437e5474a1d877a0dc8f5a30edfb0d6c4b47", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-ORG-009", "registryId": "vr.wm-org-009", "name": "Public Office", "version": "0.3.0-reviewable-draft", "previousVersions": [ { "version": "0.2.0-legacy", "url": "https://github.com/ver-cy/world-models/blob/feat/mega-model-registry/models/polity/A11-public-office-and-official.md" } ], "entryKind": "entity", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.ORG.OFF" ], "tags": [ "public", "office", "soc.org.off" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-org-009-public-office/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-org-009", "model": { "registry_id": "vr.wm-org-009", "model_id": "WM-ORG-009", "name": "Public Office", "entry_kind": "entity", "purpose": "Describe one enduring public office, its evidenced authority and its qualified links to holders, tenure and accountability records.", "scope_statement": "One jurisdiction-qualified office instance, possibly vacant or jointly held, with stable identity across holder changes. The root is a position of public authority, not its incumbent, employing body, building, election or register. Office-specific assertions link to separate person, institution and legal-record masters. Local records describe evidence and uncertainty; they do not create public powers or determine legal validity.", "in_scope": [ "Office identity, classification, establishing basis, body and territory references, nonphysical properties and continuity", "Office-specific competence assertions, selection and tenure links, vacancy and acting arrangements with temporal evidence", "Applicable accountability duties, declaration and oversight references, restricted views, provenance and authorized record maintenance" ], "out_of_scope": [ "Person biographies, employment/payroll, institution governance, election administration, lawmaking and general legal-document masters", "Making appointments, removing holders, exercising or delegating powers, issuing sanctions or deciding the validity of official acts", "A universal definition of public official, a complete national office register, or an executable legal-authority engine" ], "boundary_notes": [ { "neighbor": "WM-ORG-004 Position", "distinction": "Conceptual specialization candidate only. This root adds public-law basis and office-specific context without ratifying generic Position inheritance or duplicating its operational machinery.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "WM-PER-001 Person and tenure relationship", "distinction": "A person is externally mastered; tenure is a separately identified qualified link, not a second person master. Office identity survives succession and vacancy.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "WM-POL-016 Public Authority / Institution", "distinction": "The body containing or supporting an office is externally referenced. The legacy self-reference for the branch body is rejected; a post is not automatically the institution itself.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-POL-003 Election and WM-ORG-007 Mandate / Charter", "distinction": "Election outcomes and competence instruments are referenced, not authored or validated here. Nomination, election, appointment and assumption of duties can have different effects.", "source_refs": [ "SRC-004", "SRC-005" ] }, { "neighbor": "WM-POL-013 Registry Mandate", "distinction": "A mandate may govern an adopting register; it does not make every office record or declaration public. Public projections require an evidenced disclosure rule.", "source_refs": [ "SRC-004" ] } ] }, "sources": [ { "id": "SRC-001", "title": "The Organization Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-org/", "version_or_date": "Recommendation 2014-01-16; sections 2.2 and 5.3", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:18:31Z", "relevance": "Post, Membership, Role and Organization distinctions inform the conceptual boundary. Multiple holders are possible. ORG alone neither establishes public authority nor supplies a complete legal-accountability model." }, { "id": "SRC-002", "title": "Popolo Post specification", "organization": "Popolo project", "url": "https://www.popoloproject.com/specs/post.html", "version_or_date": "Undated web specification accessed 2026-10-06; release pin unresolved", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:18:31Z", "relevance": "Post identity, labels, organization, area and existence dates are candidate interchange concepts. Popolo routes holding through membership instead of direct ORG holds/heldBy; mappings need explicit loss reporting." }, { "id": "SRC-003", "title": "Popolo Membership specification", "organization": "Popolo project", "url": "https://www.popoloproject.com/specs/membership.html", "version_or_date": "Undated web specification accessed 2026-10-06; release pin unresolved", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:18:31Z", "relevance": "A qualified relationship can connect member, organization, post and dates. This is an interchange vocabulary, not evidence that an appointment or term is legally effective." }, { "id": "SRC-004", "title": "United Nations Convention against Corruption", "organization": "United Nations", "url": "https://treaties.un.org/doc/source/RecentTexts/Corruption_E.doc", "version_or_date": "2003 treaty text; selected articles 2, 7, 8, 10 and 11 accessed 2026-10-06", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:18:31Z", "relevance": "Public-official scope, integrity, declarations and transparency have domestic-law qualifications. Article 10 preserves privacy considerations. Extracted DOC text was readable with encoding debris; authentic version, state obligations and domestic implementation remain unverified." }, { "id": "SRC-005", "title": "The Constitution of the United States: A Transcription", "organization": "United States National Archives", "url": "https://www.archives.gov/founding-docs/constitution-transcript", "version_or_date": "Original 1787 text with amendment links; selected Articles I, II, III and VI", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:18:31Z", "relevance": "A jurisdiction-specific example separating office, selection, qualifications, tenure and oath. The original transcription is not a current consolidated legal profile; amended election and succession provisions must not be treated as current rules." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:18:31Z", "relevance": "Entity, activity, attribution and derivation support assertion provenance. Provenance is not proof of a lawful appointment, delegation, sanction or authoritative source." }, { "id": "SRC-007", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002, section 5.6", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T15:18:31Z", "relevance": "Timestamp syntax with seconds and offset. Date-only and uncertain legal times remain distinct local fields; this syntax supplies no tenure or succession rule." } ], "structure": { "bundles": [ { "id": "bundle-foundation", "name": "Office identity and basis", "description": "Establish the enduring subject and its qualified legal context.", "rationale": "Authored grouping informed by cited concepts, not a hierarchy mandated by any external source.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-identity", "name": "Office identity", "description": "Resolve one office independently of holders, titles and physical premises. Seat or joint-office granularity must be explicit; neither a name match nor a shared holder authorizes merging records.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "finding-identity", "name": "Persistent office and aliases", "description": "Resolve one office independently of holders, titles and physical premises. Seat or joint-office granularity must be explicit; neither a name match nor a shared holder authorizes merging records.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "q-identity-1", "text": "Which qualified master identifier resolves this office and its historical aliases?", "kind": "identity", "answer_data": [ "master namespace, office identifier, alias, valid interval, reconciliation status", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-identity-2", "text": "Does the record denote a single seat, a joint office or an office class, and what distinguishes it from a body or person?", "kind": "classification", "answer_data": [ "granularity, class code, seat reference, distinguishing evidence, excluded interpretation", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-identity-3", "text": "What evidence supports continuity when a title or identifier changes?", "kind": "validation", "answer_data": [ "former identifier, change evidence, continuity decision, reviewer, unresolved match", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-identity-1", "name": "Office identity field group 1", "description": "Candidate nested group: master namespace, office identifier, alias, valid interval, reconciliation status. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-identity-2", "name": "Office identity field group 2", "description": "Candidate nested group: granularity, class code, seat reference, distinguishing evidence, excluded interpretation. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-identity-3", "name": "Office identity field group 3", "description": "Candidate nested group: former identifier, change evidence, continuity decision, reviewer, unresolved match. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Office identity register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-basis", "name": "Establishment and profile", "description": "Bind the office to a cited establishment basis and adopting jurisdiction profile. Constitutional, statutory or other recognized bases require evidence; creation by a new enactment is not universal. Keep uncertain existence claims reviewable.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-basis", "name": "Office existence and legal context", "description": "Bind the office to a cited establishment basis and adopting jurisdiction profile. Constitutional, statutory or other recognized bases require evidence; creation by a new enactment is not universal. Keep uncertain existence claims reviewable.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-basis-1", "text": "Which instrument or recognized legal basis establishes this office under the applicable profile?", "kind": "authority", "answer_data": [ "basis reference, provision, authority, jurisdiction, profile version, assessment", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-basis-2", "text": "When is that basis asserted to take effect, change or cease, and at what time precision?", "kind": "temporal", "answer_data": [ "effective date or timestamp, end boundary, precision, amendment reference, uncertainty", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-basis-3", "text": "Which evidence and reviewer support the current existence status?", "kind": "evidence", "answer_data": [ "evidence locator, status, observation time, reviewer, contrary assertion", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-basis-1", "name": "Establishment and profile field group 1", "description": "Candidate nested group: basis reference, provision, authority, jurisdiction, profile version, assessment. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-basis-2", "name": "Establishment and profile field group 2", "description": "Candidate nested group: effective date or timestamp, end boundary, precision, amendment reference, uncertainty. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-basis-3", "name": "Establishment and profile field group 3", "description": "Candidate nested group: evidence locator, status, observation time, reviewer, contrary assertion. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-basis", "name": "Establishment and profile register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-authority", "name": "Context and authority", "description": "Locate the office within institutions and bounded competence assertions.", "rationale": "Authored grouping informed by cited concepts, not a hierarchy mandated by any external source.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-context", "name": "Institution and territorial context", "description": "Keep public body, constituency, jurisdiction, site and contact references distinct. A geographical area describes context; it does not by itself prove territorial competence or supply physical measurements for this abstract office.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "finding-context", "name": "Body and area relationships", "description": "Keep public body, constituency, jurisdiction, site and contact references distinct. A geographical area describes context; it does not by itself prove territorial competence or supply physical measurements for this abstract office.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "q-context-1", "text": "Which institution contains or supports the office during the relevant interval?", "kind": "relationship", "answer_data": [ "institution master reference, relationship type, interval, source, uncertainty", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-context-2", "text": "Which jurisdiction or constituency is associated with the office, and is it different from its working site?", "kind": "spatial", "answer_data": [ "jurisdiction reference, constituency reference, site reference, relation basis, valid interval", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-context-3", "text": "Which labels and official contact channels describe the office without exposing private holder contacts?", "kind": "definition", "answer_data": [ "label, language, official channel reference, publication class, review time", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-context-1", "name": "Institution and territorial context field group 1", "description": "Candidate nested group: institution master reference, relationship type, interval, source, uncertainty. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "data-context-2", "name": "Institution and territorial context field group 2", "description": "Candidate nested group: jurisdiction reference, constituency reference, site reference, relation basis, valid interval. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "data-context-3", "name": "Institution and territorial context field group 3", "description": "Candidate nested group: label, language, official channel reference, publication class, review time. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "artifact-context", "name": "Institution and territorial context register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-powers", "name": "Competence and constraints", "description": "Record sourced competence and limitation assertions with dates and context. A title, reporting edge or directory entry cannot prove permission to act. Delegation is a referenced instrument with bounded scope, not an inferred transfer of all powers.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-powers", "name": "Qualified authority assertions", "description": "Record sourced competence and limitation assertions with dates and context. A title, reporting edge or directory entry cannot prove permission to act. Delegation is a referenced instrument with bounded scope, not an inferred transfer of all powers.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-powers-1", "text": "Which functions may the office perform according to the cited authority profile?", "kind": "authority", "answer_data": [ "function description, competence provision, territory, conditions, effective interval", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-powers-2", "text": "Which exclusions, consent requirements or joint-action conditions limit an asserted power?", "kind": "constraint", "answer_data": [ "constraint reference, required co-actor, threshold rule reference, exception, unresolved interpretation", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-powers-3", "text": "What evidence bounds an alleged delegation and distinguishes it from acting appointment or ordinary reporting?", "kind": "authority", "answer_data": [ "delegation master reference, delegator, delegate, scope, validity, revocation reference, assessment", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-powers-1", "name": "Competence and constraints field group 1", "description": "Candidate nested group: function description, competence provision, territory, conditions, effective interval. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-powers-2", "name": "Competence and constraints field group 2", "description": "Candidate nested group: constraint reference, required co-actor, threshold rule reference, exception, unresolved interpretation. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-powers-3", "name": "Competence and constraints field group 3", "description": "Candidate nested group: delegation master reference, delegator, delegate, scope, validity, revocation reference, assessment. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-powers", "name": "Competence and constraints register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-holding", "name": "Selection and holding", "description": "Connect separately mastered people to evidenced assumption and tenure assertions.", "rationale": "Authored grouping informed by cited concepts, not a hierarchy mandated by any external source.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-selection", "name": "Selection and assumption", "description": "Reference selection, appointment, election or ex officio basis separately from assumption of duties. Qualification, approval, oath or affirmation requirements are profile-dependent; a missing document means unknown, not automatic invalidity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-selection", "name": "Evidence of taking office", "description": "Reference selection, appointment, election or ex officio basis separately from assumption of duties. Qualification, approval, oath or affirmation requirements are profile-dependent; a missing document means unknown, not automatic invalidity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-selection-1", "text": "Which selection route and competent authority are asserted for this holder link?", "kind": "process", "answer_data": [ "route, holder reference, issuer, instrument or outcome reference, review state", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-selection-2", "text": "Which eligibility or assumption conditions apply, and what evidence addresses each?", "kind": "requirement", "answer_data": [ "condition reference, applicable version, evidence reference, assessment, exception basis", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-selection-3", "text": "Which observed events distinguish nomination, appointment and assumption of duties?", "kind": "event", "answer_data": [ "event type, event identifier, occurrence time, recorded time, actor, source", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-selection-1", "name": "Selection and assumption field group 1", "description": "Candidate nested group: route, holder reference, issuer, instrument or outcome reference, review state. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-selection-2", "name": "Selection and assumption field group 2", "description": "Candidate nested group: condition reference, applicable version, evidence reference, assessment, exception basis. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-selection-3", "name": "Selection and assumption field group 3", "description": "Candidate nested group: event type, event identifier, occurrence time, recorded time, actor, source. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-selection", "name": "Selection and assumption register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-tenure", "name": "Tenure and holder links", "description": "Give every tenure assertion its own stable identifier. Holder, office and dates are attributes rather than a composite identity. Preserve joint or competing claims and unknown ends without deciding precedence from recency alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-tenure", "name": "Qualified holding intervals", "description": "Give every tenure assertion its own stable identifier. Holder, office and dates are attributes rather than a composite identity. Preserve joint or competing claims and unknown ends without deciding precedence from recency alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-tenure-1", "text": "Which independently identified tenure assertion links which person to this office?", "kind": "relationship", "answer_data": [ "tenure identifier, office reference, person master reference, capacity, evidence", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-tenure-2", "text": "What actual and expected boundaries apply to the holding interval, including uncertainty?", "kind": "temporal", "answer_data": [ "actual start, actual end, expected end, boundary semantics, precision, rule reference", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-tenure-3", "text": "How are concurrent holders or competing tenure claims distinguished for the requested date?", "kind": "exception", "answer_data": [ "joint-holding rule, competing claim references, adjudication reference, query date, unresolved status", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-tenure-1", "name": "Tenure and holder links field group 1", "description": "Candidate nested group: tenure identifier, office reference, person master reference, capacity, evidence. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "data-tenure-2", "name": "Tenure and holder links field group 2", "description": "Candidate nested group: actual start, actual end, expected end, boundary semantics, precision, rule reference. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "data-tenure-3", "name": "Tenure and holder links field group 3", "description": "Candidate nested group: joint-holding rule, competing claim references, adjudication reference, query date, unresolved status. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-tenure", "name": "Tenure and holder links register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity", "name": "Vacancy and continuity", "description": "Describe temporary coverage and evidenced change without inventing legal effects.", "rationale": "Authored grouping informed by cited concepts, not a hierarchy mandated by any external source.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-vacancy", "name": "Vacancy and acting arrangements", "description": "Office existence, occupancy and exercise of particular duties are separate states. Evidence can indicate vacant, unknown, disputed or temporarily covered status. A database gap is not proof of vacancy, and acting authority need not fill the substantive office.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-vacancy", "name": "Continuity without a substantive holder", "description": "Office existence, occupancy and exercise of particular duties are separate states. Evidence can indicate vacant, unknown, disputed or temporarily covered status. A database gap is not proof of vacancy, and acting authority need not fill the substantive office.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-vacancy-1", "text": "What evidence distinguishes a vacant office from missing or disputed occupancy data?", "kind": "state", "answer_data": [ "occupancy state, evidence, assessed interval, observation time, confidence qualifier", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-vacancy-2", "text": "Which instrument supports temporary performance of duties and with what limits?", "kind": "authority", "answer_data": [ "acting person or office reference, instrument, scope, trigger, end condition, unresolved authority", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-vacancy-3", "text": "How does a holder lookup expose temporary or contested status without certifying legal capacity?", "kind": "validation", "answer_data": [ "query interval, candidate links, status labels, omitted evidence, refusal or ambiguity report", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-vacancy-1", "name": "Vacancy and acting arrangements field group 1", "description": "Candidate nested group: occupancy state, evidence, assessed interval, observation time, confidence qualifier. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "data-vacancy-2", "name": "Vacancy and acting arrangements field group 2", "description": "Candidate nested group: acting person or office reference, instrument, scope, trigger, end condition, unresolved authority. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "data-vacancy-3", "name": "Vacancy and acting arrangements field group 3", "description": "Candidate nested group: query interval, candidate links, status labels, omitted evidence, refusal or ambiguity report. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-vacancy", "name": "Vacancy and acting arrangements register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-change", "name": "Change and cessation", "description": "Separate tenure ending from office abolition and from correction of a record. Renaming, merger or reorganization may require a successor reference rather than identity reuse. Do not infer automatic legal effects on prior acts.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-change", "name": "Office and tenure transitions", "description": "Separate tenure ending from office abolition and from correction of a record. Renaming, merger or reorganization may require a successor reference rather than identity reuse. Do not infer automatic legal effects on prior acts.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-change-1", "text": "Which evidenced event ended or changed a particular tenure while leaving the office identity intact?", "kind": "lifecycle", "answer_data": [ "tenure reference, change type, instrument, effective time, assessment", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-change-2", "text": "What basis supports retirement, abolition or succession of the office itself?", "kind": "lifecycle", "answer_data": [ "office state, cessation basis, successor reference, continuity decision, unresolved consequence", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-change-3", "text": "How is a retrospective correction distinguished from the historical event it describes?", "kind": "provenance", "answer_data": [ "superseded assertion, new revision, correction reason, event time, recording time, reviewer", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-change-1", "name": "Change and cessation field group 1", "description": "Candidate nested group: tenure reference, change type, instrument, effective time, assessment. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "data-change-2", "name": "Change and cessation field group 2", "description": "Candidate nested group: office state, cessation basis, successor reference, continuity decision, unresolved consequence. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "data-change-3", "name": "Change and cessation field group 3", "description": "Candidate nested group: superseded assertion, new revision, correction reason, event time, recording time, reviewer. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-change", "name": "Change and cessation register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-accountability", "name": "Accountability and disclosure", "description": "Track duty references and audience-specific information controls.", "rationale": "Authored grouping informed by cited concepts, not a hierarchy mandated by any external source.", "source_refs": [ "SRC-004", "SRC-006" ], "layers": [ { "id": "layer-duties", "name": "Integrity obligations", "description": "Record which duty profile applies and references to evidence or oversight records. Scope may depend on capacity, jurisdiction and dates. Declaration absence, an allegation or a data inconsistency does not establish misconduct.", "source_refs": [ "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-duties", "name": "Applicable accountability duties", "description": "Record which duty profile applies and references to evidence or oversight records. Scope may depend on capacity, jurisdiction and dates. Declaration absence, an allegation or a data inconsistency does not establish misconduct.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "q-duties-1", "text": "Which integrity, incompatibility or recusal rules apply to this office and tenure?", "kind": "requirement", "answer_data": [ "duty reference, capacity, jurisdiction, effective interval, applicability assessment", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-duties-2", "text": "Which filing or recusal evidence is linked to each assessed obligation?", "kind": "evidence", "answer_data": [ "obligation reference, filing identifier, evidence status, received time, reviewer", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-duties-3", "text": "Which competent oversight decision, if any, resolves a disputed compliance assertion?", "kind": "decision", "answer_data": [ "allegation reference, decision master reference, authority, review state, unresolved issue", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-duties-1", "name": "Integrity obligations field group 1", "description": "Candidate nested group: duty reference, capacity, jurisdiction, effective interval, applicability assessment. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "data-duties-2", "name": "Integrity obligations field group 2", "description": "Candidate nested group: obligation reference, filing identifier, evidence status, received time, reviewer. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "data-duties-3", "name": "Integrity obligations field group 3", "description": "Candidate nested group: allegation reference, decision master reference, authority, review state, unresolved issue. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-duties", "name": "Integrity obligations register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-disclosure", "name": "Declarations and permitted views", "description": "Keep accountability metadata separate from declaration contents and private details. Public access requires a specific disclosure basis; restricted fields and third-party information remain protected. This model records a view decision but never publishes automatically.", "source_refs": [ "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-disclosure", "name": "Disclosure boundaries", "description": "Keep accountability metadata separate from declaration contents and private details. Public access requires a specific disclosure basis; restricted fields and third-party information remain protected. This model records a view decision but never publishes automatically.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "q-disclosure-1", "text": "Which audience may access each declaration or office-record field under which rule?", "kind": "access", "answer_data": [ "audience, field selection, rule reference, permission, exception, expiry", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-disclosure-2", "text": "What redactions or data-minimization controls apply to holder and third-party details?", "kind": "privacy", "answer_data": [ "restricted categories, redaction decision, purpose, reviewer, projection identifier", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-disclosure-3", "text": "Which accountable custodian approves and reviews the permitted public projection?", "kind": "ownership", "answer_data": [ "custodian role, mandate reference, approval revision, review date, withdrawal process reference", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-disclosure-1", "name": "Declarations and permitted views field group 1", "description": "Candidate nested group: audience, field selection, rule reference, permission, exception, expiry. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "data-disclosure-2", "name": "Declarations and permitted views field group 2", "description": "Candidate nested group: restricted categories, redaction decision, purpose, reviewer, projection identifier. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "data-disclosure-3", "name": "Declarations and permitted views field group 3", "description": "Candidate nested group: custodian role, mandate reference, approval revision, review date, withdrawal process reference. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-disclosure", "name": "Declarations and permitted views register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-stewardship", "name": "Stewardship and interchange", "description": "Preserve evidence, retention decisions and semantic qualifiers across projections.", "rationale": "Authored grouping informed by cited concepts, not a hierarchy mandated by any external source.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-stewardship", "name": "Evidence and record stewardship", "description": "Maintain source-linked office assertions with integrity checks and lawful correction/disposal controls. Digests detect byte changes but do not authenticate legal authority. Retention and access policies are adopter requirements, not treaty-derived storage periods.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-stewardship", "name": "Assertion integrity and retention", "description": "Maintain source-linked office assertions with integrity checks and lawful correction/disposal controls. Digests detect byte changes but do not authenticate legal authority. Retention and access policies are adopter requirements, not treaty-derived storage periods.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-stewardship-1", "text": "Which source version, assessor and observation support each current office assertion?", "kind": "provenance", "answer_data": [ "assertion identifier, source locator, source version, digest, assessor, observation timestamp", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-stewardship-2", "text": "Which approved retention, hold and disposal rules apply to each local record class?", "kind": "retention", "answer_data": [ "record class, schedule authority, trigger, hold, disposition decision, minimal tombstone", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-stewardship-3", "text": "Which contradictions or stale references require review before an office record is reused?", "kind": "quality", "answer_data": [ "issue type, conflicting references, last review, reviewer, resolution or unknown state", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-stewardship-1", "name": "Evidence and record stewardship field group 1", "description": "Candidate nested group: assertion identifier, source locator, source version, digest, assessor, observation timestamp. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "data-stewardship-2", "name": "Evidence and record stewardship field group 2", "description": "Candidate nested group: record class, schedule authority, trigger, hold, disposition decision, minimal tombstone. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "data-stewardship-3", "name": "Evidence and record stewardship field group 3", "description": "Candidate nested group: issue type, conflicting references, last review, reviewer, resolution or unknown state. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-stewardship", "name": "Evidence and record stewardship register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-exchange", "name": "Interchange and acceptance", "description": "Align office and tenure concepts selectively to ORG and Popolo. Direct current-holder shortcuts can lose temporal or dispute qualifiers. Conversion requires versioned mappings and explicit refusal where the target cannot retain essential meaning.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "findings": [ { "id": "finding-exchange", "name": "Qualified projections and losses", "description": "Align office and tenure concepts selectively to ORG and Popolo. Direct current-holder shortcuts can lose temporal or dispute qualifiers. Conversion requires versioned mappings and explicit refusal where the target cannot retain essential meaning.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "questions": [ { "id": "q-exchange-1", "text": "Which mapping version carries office and tenure identities into the target profile?", "kind": "interoperability", "answer_data": [ "source profile, target profile, mapping version, office key, tenure key", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-exchange-2", "text": "Which authority, time, privacy or dispute qualifiers would a projection lose?", "kind": "exception", "answer_data": [ "field mapping, omitted qualifier, semantic loss, recipient risk, refusal reason", "Record source, assessment status and explicit unknown or not-applicable reason." ] }, { "id": "q-exchange-3", "text": "Which acceptance cases demonstrate that vacancy, joint holding and disputed succession survive the mapping?", "kind": "validation", "answer_data": [ "fixture identifiers, expected assertions, actual result, loss report, unresolved conformance", "Record source, assessment status and explicit unknown or not-applicable reason." ] } ], "data_elements": [ { "id": "data-exchange-1", "name": "Interchange and acceptance field group 1", "description": "Candidate nested group: source profile, target profile, mapping version, office key, tenure key. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "data-exchange-2", "name": "Interchange and acceptance field group 2", "description": "Candidate nested group: field mapping, omitted qualifier, semantic loss, recipient risk, refusal reason. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] }, { "id": "data-exchange-3", "name": "Interchange and acceptance field group 3", "description": "Candidate nested group: fixture identifiers, expected assertions, actual result, loss report, unresolved conformance. A profile-specific schema is required before operational validation.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-exchange", "name": "Interchange and acceptance register", "description": "Versioned local assertion index with references to external authoritative records; does not replace the instrument or master record.", "media_or_form": [ "structured assertion register", "authorized document projection" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus namespace and revision; otherwise governed IRI, then local UUID. Opaque entry IDs survive date corrections; never use holder name or date as identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "resolve-office", "name": "Resolve an office reference", "description": "Proposed operation, not implemented. Resolve a qualified office identifier and aliases without merging by title, holder or site.", "inputs": [ "master namespace", "office reference", "as-of context" ], "outputs": [ "resolved office or ambiguity report" ], "preconditions": [ "Verified role, purpose and field-level permission for every referenced record", "Evidence and applicable profile identified; unresolved write authority causes refusal", "For mutation, expected revision and idempotency key match; otherwise refuse" ], "effects": [ "Read-only resolution; no master identity change" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "record-basis", "name": "Record an office-basis assertion", "description": "Proposed operation, not implemented. Link existing establishment or competence evidence with review status; cannot create an office or grant a power.", "inputs": [ "office reference", "instrument and provision reference", "assessment", "expected revision" ], "outputs": [ "new basis assertion or refusal" ], "preconditions": [ "Verified role, purpose and field-level permission for every referenced record", "Evidence and applicable profile identified; unresolved write authority causes refusal", "For mutation, expected revision and idempotency key match; otherwise refuse" ], "effects": [ "Append a local evidenced assertion only" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "link-tenure", "name": "Link a tenure assertion", "description": "Proposed operation, not implemented. Record independently identified holder and interval evidence, retaining competing assertions; cannot appoint or remove anyone.", "inputs": [ "office and person master references", "tenure identifier", "evidence and interval", "expected revision" ], "outputs": [ "tenure linkage revision or refusal" ], "preconditions": [ "Verified role, purpose and field-level permission for every referenced record", "Evidence and applicable profile identified; unresolved write authority causes refusal", "For mutation, expected revision and idempotency key match; otherwise refuse" ], "effects": [ "Append a qualified local link; no legal effect" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "inspect-occupancy", "name": "Inspect occupancy at a time", "description": "Proposed operation, not implemented. Return qualified holder candidates and vacancy, acting, stale or disputed status. Absence of data returns unknown, not vacant.", "inputs": [ "office reference", "query date or timestamp and precision", "authorized evidence scope" ], "outputs": [ "qualified occupancy report or unresolved result" ], "preconditions": [ "Verified role, purpose and field-level permission for every referenced record", "Evidence and applicable profile identified; unresolved write authority causes refusal", "For mutation, expected revision and idempotency key match; otherwise refuse" ], "effects": [ "Read-only assessment of recorded assertions; no legal-capacity certification" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "record-duty-evidence", "name": "Record accountability evidence", "description": "Proposed operation, not implemented. Link a duty to filing or oversight evidence, preserving allegation versus determination and restricted contents.", "inputs": [ "office and tenure reference", "duty and evidence references", "assessment", "expected revision" ], "outputs": [ "accountability index revision or refusal" ], "preconditions": [ "Verified role, purpose and field-level permission for every referenced record", "Evidence and applicable profile identified; unresolved write authority causes refusal", "For mutation, expected revision and idempotency key match; otherwise refuse" ], "effects": [ "Append a local evidence linkage; no sanction, filing or public disclosure" ], "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "prepare-projection", "name": "Prepare an authorized office projection", "description": "Proposed operation, not implemented. Build a local recipient-scoped view with mapping and redaction records. Refuse unsupported loss of time, authority or dispute qualifiers.", "inputs": [ "office revision", "recipient authorization", "target mapping version", "approved field scope" ], "outputs": [ "local projection and loss report or refusal" ], "preconditions": [ "Verified role, purpose and field-level permission for every referenced record", "Evidence and applicable profile identified; unresolved write authority causes refusal", "For mutation, expected revision and idempotency key match; otherwise refuse" ], "effects": [ "Create a local artifact and access audit; no transmission or access expansion" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] } ], "composition": [ { "target": "WM-ORG-004", "relation": "ALIGN", "purpose": "Candidate Position alignment; boundary and version must be pinned before integration, with no assumed inheritance.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-PER-001", "relation": "REFERENCE", "purpose": "Holder and witness person masters when applicable; do not duplicate biography, identity proofing or person lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-POL-016", "relation": "REFERENCE", "purpose": "Candidate body reference with external institution identity and governance. Replaces the erroneous legacy body self-reference conceptually.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-ORG-007", "relation": "REFERENCE", "purpose": "Candidate authority-instrument binding; competence is an evidenced assertion, not inferred from linking this model.", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] }, { "target": "WM-POL-003", "relation": "REFERENCE", "purpose": "Optional election outcome reference for elected offices; no election administration or assumed mandate validity.", "required": false, "source_refs": [ "SRC-004", "SRC-005" ] }, { "target": "WM-POL-013", "relation": "REFERENCE", "purpose": "Optional adopting register mandate governing access and stewardship; no universal public-register requirement.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "https://www.w3.org/TR/vocab-org/", "relation": "ALIGN", "purpose": "Conceptual Post and Membership alignment; target mapping requires temporal and capacity qualifiers.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "https://www.popoloproject.com/specs/", "relation": "ALIGN", "purpose": "Candidate civic interchange with explicit membership-mediated holding; release pin and loss tests remain outstanding.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Accountable public register custodian and evidence of stewardship mandate, separate from appointing authority and holder", "Office-family and jurisdiction profile with effective versions, authority and disclosure rules", "Master namespaces, reference bindings, retention schedule, review route and incident contact by role" ], "namespace_guidance": "Use a governed jurisdiction and custodian namespace for office IDs; separate namespaces for tenure assertions and record revisions. Titles and dates never define identity.", "registry_links": [ "vr.wm-org-009", "Adopting office master registry and mandate reference", "Version-pinned person, institution and instrument bindings when available" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalization here means a deterministic local projection, not canonical research status or legal authority. Preserve source text locators, uncertainty and competing claims.", "Keep office identity stable through evidenced renaming and holder change; merges or successor substitutions require reviewed basis and reversible mapping." ], "patch_rules": [ "Use typed, attributed patches with expected revision, reason, evidence and idempotency key; reject conflicting revisions.", "A correction appends a superseding assertion with recording time; do not rewrite the historical event time or silently discard contrary evidence." ], "compatibility_rules": [ "Changing office granularity, tenure interval semantics or disclosure defaults is a breaking profile change requiring migration review.", "Reject mappings that flatten disputed or acting capacity into an unqualified current holder; emit losses and preserve stable keys." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with namespace", "Governed global identifier or IRI", "Adopting Dimension UUID or ULID with unresolved-reconciliation status" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z. Keep event/effective time separate from observation and ingestion time. Preserve legal date-only values, precision and unknown bounds separately; do not manufacture midnight timestamps.", "serial_naming_rule": "Use office ID, artifact kind and opaque entry ID; revisions and display dates are metadata, not identity. Never encode personal names or sensitive declaration data in filenames.", "integrity_rule": "Store digest, media type, source version, authorized locator and access class. A matching digest checks bytes, not authenticity or authority; access denial and unavailable evidence remain explicit." }, "policies": [ "Local research and candidate operations are reviewable only. An office entry, temporal match or signed source does not establish legal authority, eligibility or validity of official acts.", "Apply evidenced public-disclosure duties through reviewed views while protecting restricted holder and third-party data. No presumption that an entire office directory or declaration is public.", "Record integrity allegations, findings, appeals and sanctions as separately attributed assertions; do not infer misconduct from missing or late data.", "Weapons, detention and controlled-item authority, if referenced by an office profile, remain at policy level; no operational instructions are included." ], "crud": { "read": [ "Resolve authorized view, purpose, effective context and evidence freshness; show unknown, contested and temporary states." ], "create": [ "Create a local office assertion only with custodian authorization, qualified identity, basis evidence and duplicate-resolution status; this does not establish the office legally." ], "update": [ "Append a versioned patch with source, assessor, reason and concurrency check; do not perform appointments, delegations or removals." ], "delete": [ "Retire obsolete local references with lawful minimal tombstones and successor links where evidenced. Apply custodian-approved retention, legal holds and authorized disposal to payloads and copies; avoid indefinite personal-data history.", "Local deletion cannot abolish an office, erase a tenure's legal effect, remove an external master record or invalidate an official act. Scope any lawful erasure and preserve only justified audit metadata." ] }, "roles": [ { "name": "Register custodian", "responsibilities": [ "Maintain namespace, stewardship mandate and approved record policy" ] }, { "name": "Authority reviewer", "responsibilities": [ "Assess establishment, capacity and jurisdiction-profile evidence without automated legal adjudication" ] }, { "name": "Evidence editor", "responsibilities": [ "Record attributed links and preserve competing assertions under approved access" ] }, { "name": "Disclosure reviewer", "responsibilities": [ "Approve audience-specific projections, redaction and privacy review" ] }, { "name": "Records steward", "responsibilities": [ "Apply retention schedules, legal holds and authorized payload disposal" ] }, { "name": "Read-only auditor", "responsibilities": [ "Inspect permitted provenance, conflicts and review decisions" ] } ], "access": { "default_rule": "Deny access to unclassified payloads; expose only a custodian-approved public or role-specific view grounded in applicable rules. Public title data does not open declarations or person masters.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "A valid disclosure obligation can authorize selected fields after review; log its scope, basis and expiry.", "Exceptional oversight access requires specific authority and purpose; it never becomes a permanent public grant." ], "audit_requirements": [ "Log actor role, purpose, rule, revision, selected view and result for access and mutation decisions; protect the audit metadata itself.", "Capture export selection, redactions, mapping losses and refusal reasons without copying unnecessary sensitive payloads." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Nearest AGENTS.md and owner Dimension policies", "Public Office specification, holds and applicable jurisdiction profile", "Master-system reference bindings and source evidence", "Authorized instance view and current revision" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one enduring public office, with qualified holder, authority and accountability references. A separate local no-tools self-audit found no critical contradiction. The result remains a noncanonical reviewable draft with independent-review, source/version, jurisdiction-profile and executable-conformance holds; it does not certify public authority or universal coverage.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Office, tenure assertion and revision identities are distinct; aliases do not authorize merges." }, { "dimension": "lifecycle", "status": "covered", "notes": "Office existence, tenure, vacancy, temporary coverage and local record retirement remain separate." }, { "dimension": "relationships", "status": "covered", "notes": "Person, institution, instrument, election and registry mandate masters are referenced with candidate bindings." }, { "dimension": "temporal", "status": "covered", "notes": "Expected versus actual boundaries, effective time, observation time and uncertainty are preserved." }, { "dimension": "provenance", "status": "covered", "notes": "Evidence version, locator, attribution, correction and contrary assertion tracking are proposed." }, { "dimension": "ownership", "status": "covered", "notes": "Public custodian stewardship is distinct from appointing authority, holder and source publisher." }, { "dimension": "validation", "status": "gap", "notes": "Research schema can be validated; executable instance conformance and legal-profile certification remain incomplete." }, { "dimension": "access", "status": "covered", "notes": "Public and restricted projections require evidenced rules and field-level review." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Adopter schedules, holds, limited erasure and minimal lawful tombstones control local payloads." }, { "dimension": "interoperability", "status": "gap", "notes": "ORG and Popolo conceptual differences are explicit; release pins and mapping fixtures remain open." }, { "dimension": "direct properties", "status": "covered", "notes": "Title, granularity, legal basis, jurisdiction and state are nonphysical properties. Physical measurements are not applicable to this abstract root." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Source and master references distinguish office, holder, institution and site; a title alone is not recognition evidence." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Competence assertions differ from six proposed local record operations. None performs legally effective actions." }, { "dimension": "context and evidence", "status": "covered", "notes": "Selected standards, treaty concepts and a constitutional example inform an authored schema proposal without universal legal claims." } ], "known_omissions": [ "Independent external review is absent; Claude and Grok are skipped under the owner waiver.", "Direct HTTP checks are unmeasured under the owner-reported sandbox block; browser readings do not close source authenticity, version, currency or applicability verification.", "Nested instance schemas, executable functions, mappings and adversarial fixtures are not implemented.", "Jurisdiction-specific office definitions, tenure rules, delegation powers, judicial independence, records law, accessibility, privacy and disclosure need qualified adoption review.", "No comprehensive treatment of customary, international, hereditary, military, collective or emergency offices; profile-specific legal bases and authority disputes remain research gaps." ], "conflicts": [], "regional_assumptions": [ "UNCAC supplies treaty concepts and qualified state obligations, not a uniform office definition or direct worldwide filing rule.", "The United States constitutional transcription is an illustrative original-text source; current amendments, legislation and other jurisdictions are not operationally validated.", "ORG and Popolo are interoperability resources, not legal authorities. Their differing holder representations require a selected mapping profile." ], "adversarial_checks": [ "A vacant or jointly held office must retain one evidenced office identity without requiring one incumbent.", "Reject dates as tenure identifiers and reject a directory entry as proof of authority to sign.", "Preserve multiple contested tenure claims and distinguish temporary exercise of duties from substantive holding.", "Reject universal public access, mandatory oath or fixed-term requirements imported from legacy material.", "Reject an automatic mapping between ORG direct holder shortcuts and time-qualified Popolo membership." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The enduring office is the subject root across vacancies and holder changes. Tenure assertions qualify external person links; they do not turn the root into a person or a register. The registry standalone-mm value is a record-plane classification, not a subject-kind enum. Institution, instrument, election and person masters remain external." }, "decisions": [ { "concept": "Enduring office root", "disposition": "accepted", "rationale": "Identity and recognition questions distinguish office, class, body, site and person. The class question diagnoses granularity rather than admitting an office classifier as the same instance root." }, { "concept": "Holder and tenure identity", "disposition": "accepted", "rationale": "Every tenure assertion has a stable identifier independent of person, office and date values. This preserves corrected dates, joint holding and competing claims without merging the office or person masters." }, { "concept": "Vacancy and temporary authority", "disposition": "separated", "rationale": "The draft distinguishes office existence, substantive occupancy and temporary exercise of duties. Missing evidence returns unknown; a holder query cannot certify legal competence." }, { "concept": "Universal establishment and tenure rules", "disposition": "rejected", "rationale": "The legacy enactment-only premise, universal oath and fixed-term assumptions are not admitted. The draft asks for evidenced legal basis and applicable conditions without projecting one constitutional example worldwide." }, { "concept": "Composition and legacy body reference", "disposition": "qualified", "rationale": "The frozen relationship ledger has no matching edges. Position alignment and person, institution, mandate, election and register links remain explicit candidates. The legacy body self-reference is rejected without modifying a shared registry." }, { "concept": "Competence and delegation", "disposition": "accepted as assertions only", "rationale": "The power questions require scope, constraints and evidence. A reporting line, title, appointment link or reference to a mandate does not confer authority; disputed legal interpretation stays with qualified review." }, { "concept": "Local record operations", "disposition": "accepted as proposed only", "rationale": "All six functions are unimplemented record operations with role, evidence and concurrency preconditions. None appoints, removes, signs, delegates, sanctions, transmits or publishes on behalf of an office." }, { "concept": "Integrity evidence and adjudicated misconduct", "disposition": "separated", "rationale": "A filing, missing record, allegation, oversight decision and sanction remain distinct attributed records. The proposed index does not infer guilt or legal noncompliance from missing or late data." }, { "concept": "Public register and declaration disclosure", "disposition": "universal openness rejected", "rationale": "The draft replaces the legacy automatic public-directory premise with an evidenced disclosure rule, custodian-reviewed field selection and protection of restricted holder and third-party details." }, { "concept": "Record history and disposal", "disposition": "accepted with adopter policy", "rationale": "Correction provenance coexists with lawful payload disposal, holds and minimal justified tombstones. History does not authorize indefinite personal-data retention; deleting a local record does not abolish an office or annul an act." }, { "concept": "ORG and Popolo holder representations", "disposition": "qualified alignment", "rationale": "The sources' direct-holder and membership-mediated representations are not falsely treated as equivalent. Pinned mappings and loss reports are required, and essential time or dispute qualifier loss causes refusal." }, { "concept": "Source access and legal currency", "disposition": "limited", "rationale": "Browser access supports selected conceptual readings. The treaty DOC has extraction debris, Popolo lacks release pins, and the constitutional source is an original transcription. Zero direct HTTP attempts means status is unmeasured, not seven failed or verified responses." }, { "concept": "Candidate fields and implemented conformance", "disposition": "deferred", "rationale": "Optional nested candidate groups do not enforce runtime identity or cardinality. Research validation establishes dossier structure only; instance schemas, legal profiles, executable mappings and acceptance fixtures remain incomplete." }, { "concept": "Independent review and supplement attribution", "disposition": "waived and held", "rationale": "The unreviewed supplement is a lead and not a provider result. This separate frozen assessment is a local Codex self-audit, not independent external review. No waived-provider findings or functions may be added." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not a second-provider review.", "Live source and version verification remains incomplete. Direct HTTP checks were not attempted under the owner-reported sandbox restriction, so all seven statuses are unmeasured and zero HTTP 200 responses were measured. Browser readings are documented separately; treaty text authenticity, Popolo release pins and current legal applicability remain open.", "Qualified jurisdiction and office-family review is required for establishment, selection, tenure, acting capacity, delegation, integrity, privacy, disclosure and retention rules. The original constitutional transcription and treaty concepts do not supply a current operational legal profile or universal office definition.", "Nested instance schemas, pinned neighbor bindings, ORG/Popolo mappings, executable functions and adversarial conformance fixtures remain incomplete. No implementation, legal-capacity certification or standards-conformance claim is made.", "Coverage of customary, international, hereditary, military, collective and emergency offices remains incomplete; wider applicability, source licensing and profile-specific accessibility requirements need review.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Run the coordinator source checker, then verify authentic source versions, effective law, domestic implementation and permitted source reuse for each adopting profile.", "Implement nested office and tenure schemas and mappings with fixtures for vacancy, joint holding, competing claims, temporary duty performance, date correction, redaction and lawful disposal.", "Validate candidate neighbor bindings and expand specialist office-family coverage without taking ownership of external person, institution, election or instrument masters.", "Restore independent external review before any canonical or publishable-draft promotion." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }