Mandate / Charter
Represent one identifiable constitutive or mandate instrument and its provision-grounded assertions of purpose, powers, constraints and accountability across revisions.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 12 findings · 36 questions
Instrument identity Instrument-specific context for instrument identity.
Persistent instrument
Answerable context for persistent instrument.
Persistent instrument
Separate the instrument from its governed subject, versions and copies. Record issuer-scoped identity and the precise instrument class.
- Which master identifies this instrument independently of the organization number and its copies? identity
- Is this record a founding instrument, governing instrument or separately issued mandate? classification
- Which bodies are constituted, governed or assigned responsibilities by this instrument? relationship
Recognized text and interpretation
Answerable context for recognized text and interpretation.
Recognized text and interpretation
Distinguish authoritative text from drafts, templates, translations and editorial consolidations; record unresolved authority or precedence conflicts.
- What evidence establishes the status of the text being relied upon? evidence
- Which language, expression and manifestation were inspected by which reviewer? provenance
- Which competing instruments or interpretations remain unresolved? exception
Adoption and effect Instrument-specific context for adoption and effect.
Adoption and recognition evidence
Answerable context for adoption and recognition evidence.
Adoption and recognition evidence
Record the adopting act and any signature, approval, filing or registration prerequisites selected by the applicable profile. Uploading a copy does not establish adoption.
- Which body had competence to adopt this instrument under the cited basis? authority
- Which adoption prerequisites were met and which remain unconfirmed? process
- What adoption, approval and filing events are evidenced separately? event
Effective scope and temporal status
Answerable context for effective scope and temporal status.
Effective scope and temporal status
Keep recorded status separate from asserted legal effect. Capture provision-level intervals and conditions; a date-only source is not converted to a fabricated midnight instant.
- When does each relevant provision start and stop applying at the stated precision? temporal
- What territorial, organizational and subject scope bounds its application? spatial
- Is the claimed effect draft, pending, effective, suspended, expired or disputed at the requested time? state
Purposes and powers Instrument-specific context for purposes and powers.
Purpose and intended beneficiaries
Answerable context for purpose and intended beneficiaries.
Purpose and intended beneficiaries
Record intended ends separately from means and operational targets. Preserve source wording by reference and identify scope qualifiers without inventing a mission.
- What purpose or charge does the instrument assign? definition
- Which activities are means to that purpose and which belong to another instrument? composition
- How is reported progress related to the purpose without treating a target as authority? measurement
Power assertions and constraints
Answerable context for power assertions and constraints.
Power assertions and constraints
Record an action class, holder capacity, source and limits. Legal effect toward third parties requires separate review; a missing match means unresolved authority, not a universal prohibition.
- Which provision supports the holder capacity and action class of this asserted power? authority
- Which limits, reserved matters and approvals qualify that power? constraint
- What reliance or legal-effect questions require an external decision before this assertion can be used? decision
Governance and delegation Instrument-specific context for governance and delegation.
Constitutive decision rules
Answerable context for constitutive decision rules.
Constitutive decision rules
Record the instrument rules governing body composition and decision procedures. Actual membership, eligibility and meeting outcomes are external evidence, not inferred from a roster.
- Which body composition, appointment and quorum rules apply to this decision type? requirement
- How do interest exclusions, vacancies or exceptional procedures alter eligibility? exception
- What evidence supports the claimed satisfaction of notice and voting requirements? validation
Delegation scope and continuity
Answerable context for delegation scope and continuity.
Delegation scope and continuity
Reference each grant to its source power and evidenced recipient capacity. Capture partial withdrawal and subdelegation limits without making employment, record access or a cycle into authority.
- Which source power, grant instrument and recipient capacity support this delegation? relationship
- Does the evidenced grant permit subdelegation and within which boundaries? constraint
- Which revocation, holder change or expiry evidence affects the delegation chain? lifecycle
Change and continuity Instrument-specific context for change and continuity.
Amendment and consolidation
Answerable context for amendment and consolidation.
Amendment and consolidation
Separate substantive amendment from editorial correction. Preserve affected provision mappings, approvals and effective triggers; later file timestamps do not select the legally operative version.
- What procedure and external approvals govern this proposed amendment? process
- Which trigger makes each changed provision effective? temporal
- How does the consolidation map every affected clause to its source versions? interoperability
Renewal, cessation and successor
Answerable context for renewal, cessation and successor.
Renewal, cessation and successor
Distinguish expiry of this instrument, withdrawal of a particular mandate and dissolution of the governed body. Preserve renewal gaps and successor references rather than assuming continuity.
- What termination, renewal or replacement rule applies to this instrument? lifecycle
- Is there an evidenced gap or overlap between the old and renewed mandate? temporal
- Which residual duties and record-custody arrangements survive cessation? retention
Accountability and evidence Instrument-specific context for accountability and evidence.
Oversight duties and discharge assertions
Answerable context for oversight duties and discharge assertions.
Oversight duties and discharge assertions
Record duties created by the instrument and refer to performance evidence. Receipt, acceptance and satisfaction are distinct assertions; no filing or review is performed by this model.
- Which duty is owed to which oversight body under which clause? requirement
- What cadence, trigger and reporting period qualify the duty? temporal
- Does the evidence show submission, receipt, acceptance or a disputed discharge? quality
Controlled disclosure and evidence integrity
Answerable context for controlled disclosure and evidence integrity.
Controlled disclosure and evidence integrity
Maintain a traceable instrument projection for its entitled audience. Public text does not automatically expose signatures, contact details, privileged interpretation or restricted evidence.
- Which steward maintains the record and which authority approves its audience-specific projection? ownership
- Which text and supporting evidence may this reader receive under the applicable access policy? access
- How can a reader trace a projected claim to its inspected source and detect a changed copy? provenance
Classifiers Filled
- Family
- World Models
- Category
- Society, people and institutions
- Entry kind
- entity
- Navigation path
- NAV.SOC.ORG.MND
- Domain
- SOC.ORG.MND
- Industry
- Cross-industry
- Tags
- mandatechartersoc.org.mnd
- Also called
- O4
What it is Filled
The root is a persistent instrument record, including a charter, statute, articles, constitution or separately issued mandate instrument. Revisions and clause-level mandate assertions belong to that record; independently issued instruments get separate identities and references. It records claimed authority and evidence without adjudicating legal validity or executing grants.
In scope
- Instrument identity, type, applicable organization or body references, jurisdiction and authoritative text references.
- Version-qualified provisions, purposes, power assertions, reserved matters and delegation evidence references.
- Governance and amendment rules contained in the instrument, effective intervals, supersession, termination and renewal evidence.
- Accountability duty definitions and linked discharge assertions, evidence provenance and reader-specific projections.
Out of scope
- Organization, unit, committee, position, employment and membership master lifecycles or legal entity registration.
- General access authorization, policy enforcement, signing, contract execution, filing submission and automated legal-effect decisions.
- Court proceedings, dispute resolution, accounting, full audit-trail infrastructure and unrelated internal policies.
- Operational instructions for weapons, detention or controlled items; any such mandate remains at policy and authority-reference level.
Why it exists Filled
Represent one identifiable constitutive or mandate instrument and its provision-grounded assertions of purpose, powers, constraints and accountability across revisions.
Distinguishing features Derived, awaiting review
- Unlike Organization, unit and governance body: An instrument can govern an existing body without creating a new legal person. Do not require the legacy one-charter-to-one-organization cardinality. Refer to constituted or governed subjects with explicit relationship roles.
- Unlike Position, employment and membership: Name the capacity in which an authority is held and resolve its holder externally. Being an employee or occupying a post does not by itself prove a power.
- Unlike Organization policy and commercial contract: Record constitutive scope and clause references here. Routine policy and contract transactions retain their own masters; internal limits are not a universal conclusion about third-party legal effect.
- Unlike Legal entity registration and registry mandate: Registration evidence is a reference, not the charter identity. The legacy public-register label must not be mapped to a registry mandate as if it were a register entry.
- Unlike Instrument collection and legal document representation: One instrument may have many expressions and manifestations. A collection of independent instruments is not silently merged into one root. Clause numbering, organization numbers and file names are not sufficient instrument identity.
- Unlike Dispute case, stewardship, access and audit: Keep challenge, ownership, permission and audit event masters external; this record holds only scoped references and assertions. A provenance link is not certification.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- No automated action may confer, revoke, exercise or certify a legal power from this research structure.
- Deny nonpublic evidence unless the actor has purpose-scoped permission.
May
- Register instrument evidence: Proposed, unimplemented local operation. Create a local draft identity record for an evidenced instrument without adopting or registering the governed organization.
- Record effect assertion: Proposed, unimplemented local operation. Attach a qualified assertion about adoption or effective scope after review; do not activate legal powers.
- Inspect power evidence: Proposed, unimplemented local operation. Prepare a local evidence view for a requested capacity, action and time, including gaps and contradictory claims.
- Record amendment evidence: Proposed, unimplemented local operation. Link an evidenced amendment and changed clauses to their prior revision without executing amendment or filing.
- Link duty evidence: Proposed, unimplemented local operation. Attach an attributed submission, receipt or acceptance assertion to a defined duty without declaring satisfaction from an upload.
- Prepare instrument view: Proposed, unimplemented local operation. Render a version-specific view for an entitled reader using the selected access policy.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Derived, awaiting review
- Apply the adopted retention schedule, preservation holds and lawful deletion rules to payloads and personal data.
Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.
Owners Filled
Steward
Identify the accountable record steward by governed role and identifier, not a brand or product.
Roles
- Record steward
- Maintain identity, evidence links and version continuity.
- Competence reviewer
- Assess instrument status and authority assertions under the applicable profile.
- Evidence curator
- Record source provenance, uncertainty and contradiction without adjudicating legal effect.
- Access custodian
- Approve audience scope, redaction and retention decisions under external policy.
- Entitled reader
- Use only the permitted version-specific view and respect visible limitations.
Links to other meta-models Filled
references
- WM-ORG-001 - Candidate binding; adoption must pin the target version. Governed organizations and oversight bodies remain independently mastered.
- WM-ORG-002 - Candidate binding; adoption must pin the target version. Organizational units are recipient references; this model does not create or restructure units.
- WM-ORG-004 - Candidate binding; adoption must pin the target version. Position capacity references replace the ambiguous legacy role-assignment shorthand.
- WM-ORG-005 - Candidate binding; adoption must pin the target version. Employment assignments supply holder evidence only; employment alone confers no charter power.
- WM-ORG-006 - Candidate binding; adoption must pin the target version. Membership evidence supports the capacity of a member; admission and termination remain external.
- WM-ORG-018 - Candidate binding; adoption must pin the target version. Governance bodies supply decision-maker identity; meeting execution and body membership remain external.
- WM-ORG-019 - Candidate binding; adoption must pin the target version. Routine policies remain separate from constitutive rules and reference their enabling basis.
- WM-ORG-010 - Candidate binding; adoption must pin the target version. Legal entity registration is supporting evidence; never use its identifier as sole instrument identity.
- WM-ECO-006 - Candidate binding; adoption must pin the target version. Contract transactions may cite powers; execution and third-party effects remain external.
- WM-POL-009 - Candidate binding; adoption must pin the target version. Challenges link to separately mastered court or arbitration cases.
- WM-XCT-001 - Candidate binding; adoption must pin the target version. Record stewardship policy is referenced, not reconstructed as a constitutive power.
- WM-XCT-002 - Candidate binding; adoption must pin the target version. Reader permissions and consent are external access-policy inputs, not organizational powers.
- WM-XCT-004 - Candidate binding; adoption must pin the target version. Link local access-audit evidence without importing a general audit-trail engine.
aligned
- https://www.w3.org/TR/vocab-org/ - Candidate binding; adoption must pin the target version. Conceptual alignment for organization and capacity references; no RDF implementation is supplied.
- https://www.w3.org/TR/prov-o/ - Candidate binding; adoption must pin the target version. Conceptual provenance alignment, not legal certification or implemented conformance.
- https://docs.oasis-open.org/legaldocml/akn-core/v1.0/os/part1-vocabulary/akn-core-v1.0-os-part1-vocabulary.html - Candidate binding; adoption must pin the target version. Work, expression, manifestation and clause-reference alignment; no wildcard imports or conformance claim.
neighbor
- Organization, unit and governance body - An instrument can govern an existing body without creating a new legal person. Do not require the legacy one-charter-to-one-organization cardinality. Refer to constituted or governed subjects with explicit relationship roles.
- Position, employment and membership - Name the capacity in which an authority is held and resolve its holder externally. Being an employee or occupying a post does not by itself prove a power.
- Organization policy and commercial contract - Record constitutive scope and clause references here. Routine policy and contract transactions retain their own masters; internal limits are not a universal conclusion about third-party legal effect.
- Legal entity registration and registry mandate - Registration evidence is a reference, not the charter identity. The legacy public-register label must not be mapped to a registry mandate as if it were a register entry.
- Instrument collection and legal document representation - One instrument may have many expressions and manifestations. A collection of independent instruments is not silently merged into one root. Clause numbering, organization numbers and file names are not sufficient instrument identity.
- Dispute case, stewardship, access and audit - Keep challenge, ownership, permission and audit event masters external; this record holds only scoped references and assertions. A provenance link is not certification.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier
- Governed global identifier or IRI
- Dimension-assigned UUID or ULID
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
- Register instrument evidence: Proposed, unimplemented local operation. Create a local draft identity record for an evidenced instrument without adopting or registering the governed organization.
- Record effect assertion: Proposed, unimplemented local operation. Attach a qualified assertion about adoption or effective scope after review; do not activate legal powers.
- Inspect power evidence: Proposed, unimplemented local operation. Prepare a local evidence view for a requested capacity, action and time, including gaps and contradictory claims.
- Record amendment evidence: Proposed, unimplemented local operation. Link an evidenced amendment and changed clauses to their prior revision without executing amendment or filing.
- Link duty evidence: Proposed, unimplemented local operation. Attach an attributed submission, receipt or acceptance assertion to a defined duty without declaring satisfaction from an upload.
- Prepare instrument view: Proposed, unimplemented local operation. Render a version-specific view for an entitled reader using the selected access policy.
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
- RFC 3339: Date and Time on the Internet: Timestamps
Context of use required Filled
- Charity guidance is scoped to England and Wales; company model articles apply only when evidenced as adopted.
- US federal committee renewal and filing guidance is illustrative and does not impose a universal lifespan or public-register duty.
- External standards support representation only; no legal-system equivalence or schema conformance is claimed.
Sources Filled
- How to write your charity's governing document (CC22b) - Charity Commission for England and Wales
- Charitable companies: changing your governing document - Charity Commission for England and Wales
- Federal Advisory Committee Charters - United States General Services Administration
- Companies Act 2006, section 40 - United Kingdom Parliament
- Model articles for private companies limited by shares - United Kingdom Companies House
- The Organization Ontology - World Wide Web Consortium
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Akoma Ntoso Version 1.0. Part 1: XML Vocabulary - OASIS
- RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force
Open questions
- Verify exact source versions, current consolidated law and exceptions, final URLs and hashes outside the sandbox; HTTP success alone is insufficient.
- Develop adopting profiles and test multiple instruments, conditional effect, partial revocation, renewal gaps, conflicting copies, restricted annexes and lawful disposal.
- Implement nested instance schemas and loss-aware mappings, and pin all external model bindings before operational use.
- Restore independent external review before canonical or publishable-draft promotion.
- Independent external review is absent; Claude and Grok are skipped under the owner-authorized waiver.
- Direct HTTP checks are not attempted under the owner-reported sandbox block; current versions, redirects and source hashes remain unverified.
- Full section 40 text and exceptions were not retrieved; only official indexed evidence supports the limited counterexample.
- Indigenous, religious, international, emergency and other national legal forms require separate research profiles.
- Nested data schemas, adversarial instance fixtures, signed-text verification, precise external bindings and executable conformance remain incomplete.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-org-007-mandate-charter/spec.yaml