# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-21T15:46:01Z", "synthesisSha256": "b452f8d81590c57f382933bc2686c6553cc0fe4aab7465b36b065d8626c0f3f0", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-AI-015", "registryId": "vr.wm-ai-015", "name": "Agent Delegation Mandate", "version": "0.1.0-review.20261021", "previousVersions": [], "entryKind": "relationship", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.AI.MND" ], "tags": [ "agent", "delegation", "mandate", "inf.ai.mnd" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-ai-015-agent-delegation-mandate/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-ai-015", "model": { "registry_id": "vr.wm-ai-015", "model_id": "WM-AI-015", "name": "Agent Delegation Mandate", "entry_kind": "relationship", "purpose": "Describe a versioned entrustment of bounded work to an identified agent on behalf of a principal, with authority evidence, limits, oversight and an effective interval.", "scope_statement": "One identified delegation relationship and its mandate revisions. The root connects a principal, delegate and authorized work context; it records asserted terms and evidence without issuing credentials or deciding runtime access. Proposed, accepted, disputed, suspended and ended mandates remain distinguishable. This is a proposed format-neutral research model, not an executable authorization or legal instrument.", "in_scope": [ "Mandate identity, principal and delegate references, issuing authority and acceptance evidence", "Entrusted objective, permitted and forbidden action-resource pairs, conditions, budgets and review gates", "Temporal validity, permitted subdelegation, revision lineage, withdrawal evidence and external execution references" ], "out_of_scope": [ "Agent identity lifecycle, capabilities, prompts, memory, tool definitions and execution plans", "Credential issuance, identity proofing, cryptographic verification, policy evaluation, enforcement and runtime audit-trail execution", "Automatic legal agency, universal consent rules, contracting or financial execution, and safety-critical operating instructions" ], "boundary_notes": [ { "neighbor": "WM-AI-002 AI Agent", "distinction": "Registry parent denotes context, not type inheritance. A mandate is not an agent. Reference the delegate master and revision binding without copying its lifecycle or capabilities.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "WM-AI-004 AI Inference / Agent Run", "distinction": "Runs supply observed activity and evidence references. Many runs can cite a mandate revision; a run does not prove authorization or own mandate terms.", "source_refs": [ "SRC-004", "SRC-008" ] }, { "neighbor": "WM-AI-005 Prompt / Agent Configuration and WM-AI-017 Tool Description", "distinction": "Instructions and advertised tool capabilities do not grant authority. Bind versions by reference; untrusted content cannot amend mandate scope.", "source_refs": [ "SRC-002", "SRC-007" ] }, { "neighbor": "WM-AI-016 Agent Handoff Message", "distinction": "A handoff carries task or context references. It neither creates a mandate nor implies permission to subdelegate.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "Credential, policy decision and approval record masters", "distinction": "This model records binding and evidence references only. A mandate may exist without a token; a valid token or approval document alone does not establish all mandate conditions.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006", "SRC-007" ] } ] }, "sources": [ { "id": "SRC-001", "title": "RFC 8693: OAuth 2.0 Token Exchange", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc8693.html", "version_or_date": "January 2020; sections 1.1, 4.1 and 4.4", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:44:50Z", "relevance": "Delegation separates represented subject and current actor; nested prior actors are historical, not additional access authority." }, { "id": "SRC-002", "title": "RFC 9396: OAuth 2.0 Rich Authorization Requests", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc9396.html", "version_or_date": "May 2023; sections 2.1, 2.2, 12 and 13", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:44:50Z", "relevance": "Typed authorization details distinguish actions and resource locations. Combined arrays can widen permissions; requested details are not automatically granted rights." }, { "id": "SRC-003", "title": "ODRL Information Model 2.2", "organization": "W3C", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "Recommendation 2018-02-15; sections 2, 2.6, 2.10 and 3", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:44:50Z", "relevance": "Policy vocabulary for permissions, prohibitions, duties and constraints; explicit conflict strategies and application profiles. Conceptual alignment only." }, { "id": "SRC-004", "title": "PROV-O: The PROV Ontology", "organization": "W3C", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation 2013-04-30; actedOnBehalfOf and qualifiedDelegation", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:44:50Z", "relevance": "Delegation provenance connects actors and retained responsibility. Attribution does not establish current authority or legal enforceability." }, { "id": "SRC-005", "title": "RFC 7009: OAuth 2.0 Token Revocation", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc7009.html", "version_or_date": "August 2013; sections 2.1 and 2.2", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:44:50Z", "relevance": "Revocation has propagation and related-token policy boundaries; endpoint acknowledgement is not evidence that every downstream effect stopped." }, { "id": "SRC-006", "title": "RFC 7662: OAuth 2.0 Token Introspection", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc7662.html", "version_or_date": "October 2015; sections 2.2 and 4", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:44:50Z", "relevance": "Active-state observations and cached status can become stale. Token status is distinct from a mandate and its governing conditions." }, { "id": "SRC-007", "title": "NIST SP 800-162: Guide to Attribute Based Access Control Definition and Considerations", "organization": "NIST", "url": "https://csrc.nist.gov/pubs/sp/800/162/upd2/final", "version_or_date": "January 2014; updated 2019-08-02; publication abstract reviewed", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:44:50Z", "relevance": "Subject, object, operation and environmental attributes frame authorization context. Only the official abstract was reviewed, not the full publication." }, { "id": "SRC-008", "title": "NIST AI RMF 1.0: AI RMF Core", "organization": "NIST", "url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/", "version_or_date": "AI RMF 1.0, 2023; online Core GOVERN 1-3 and MAP 1-3", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:44:50Z", "relevance": "Accountable roles, purpose, contextual risk and human oversight inform proposed mandate review questions; this voluntary framework is not a mandate schema." } ], "structure": { "bundles": [ { "id": "mandate-parties", "name": "Mandate and parties", "description": "Identify the entrustment and the parties without collapsing their roles.", "rationale": "A delegation relationship needs its own identity and accountable role bindings.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "layers": [ { "id": "mandate-identity-layer", "name": "Mandate identity", "description": "Keep relationship identity separate from a document revision, runtime session or token identifier.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "mandate-identity", "name": "Stable mandate and revision", "description": "Keep relationship identity separate from a document revision, runtime session or token identifier.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "mandate-identity-q01", "text": "Which master identifier denotes this mandate across revisions?", "kind": "identity", "answer_data": [ "mandate_id", "master_system", "revision_id" ] }, { "id": "mandate-identity-q02", "text": "What kind of entrustment does the declared profile classify this as?", "kind": "classification", "answer_data": [ "mandate_class", "profile_ref", "classification_reason" ] }, { "id": "mandate-identity-q03", "text": "Which principal and delegate master records participate in this relationship?", "kind": "relationship", "answer_data": [ "principal_ref", "delegate_ref", "identity_binding_evidence" ] }, { "id": "mandate-identity-q04", "text": "Which identity or authority changes require a new mandate rather than a revision?", "kind": "lifecycle", "answer_data": [ "continuity_rule", "supersedes_ref", "change_basis" ] } ], "data_elements": [ { "id": "mandate-identity-data01", "name": "Mandate identifier", "description": "Stable relationship identity, distinct from revision and token IDs.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "mandate-identity-data02", "name": "Revision identifier", "description": "Immutable revision in its master namespace.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "mandate-identity-data03", "name": "Party bindings", "description": "Principal and delegate references with issuer-qualified identifiers and binding evidence.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "mandate-identity-artifact", "name": "Mandate identity record", "description": "Versioned evidence view for stable mandate and revision; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "authority-basis-layer", "name": "Entrusting authority", "description": "Distinguish principal, issuer, delegate, approver and accountable reviewer; claims of authority require supporting references.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "findings": [ { "id": "authority-basis", "name": "Authority and acceptance evidence", "description": "Distinguish principal, issuer, delegate, approver and accountable reviewer; claims of authority require supporting references.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "questions": [ { "id": "authority-basis-q01", "text": "Who may issue this mandate on the principal's behalf and under which authority reference?", "kind": "authority", "answer_data": [ "issuer_ref", "principal_ref", "authority_basis_ref", "verification_state" ] }, { "id": "authority-basis-q02", "text": "What evidence records the delegate's acceptance or refusal of the stated revision?", "kind": "evidence", "answer_data": [ "acceptance_ref", "accepted_revision", "acceptance_state", "observed_at" ] }, { "id": "authority-basis-q03", "text": "Who remains accountable for reviewing the entrusted work and its effects?", "kind": "ownership", "answer_data": [ "accountable_role", "reviewer_ref", "responsibility_scope" ] }, { "id": "authority-basis-q04", "text": "How is disputed or missing authority represented before the mandate can be relied on?", "kind": "exception", "answer_data": [ "dispute_ref", "unknown_reason", "reliance_block", "resolution_owner" ] } ], "data_elements": [ { "id": "authority-basis-data01", "name": "Authority evidence", "description": "Issuer, authority basis, approval and verification state; identity authentication alone is insufficient.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "authority-basis-data02", "name": "Acceptance evidence", "description": "Optional evidence while proposed; acceptance requirements depend on the adopting profile.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "authority-basis-data03", "name": "Accountability binding", "description": "Role-based owner and reviewer references, with no commercial owner embedded in the model.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "authority-basis-artifact", "name": "Entrustment evidence record", "description": "Versioned evidence view for authority and acceptance evidence; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "entrusted-scope", "name": "Entrusted work and scope", "description": "Record why work was entrusted and the action-resource limits.", "rationale": "Purpose and scope must remain more precise than an instruction or advertised capability.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ], "layers": [ { "id": "purpose-outcome-layer", "name": "Purpose and outcomes", "description": "Describe the intended result and completion criteria without importing the task plan or claiming success.", "source_refs": [ "SRC-003", "SRC-008" ], "findings": [ { "id": "purpose-outcome", "name": "Entrusted objective", "description": "Describe the intended result and completion criteria without importing the task plan or claiming success.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "purpose-outcome-q01", "text": "What bounded objective is entrusted to the delegate?", "kind": "definition", "answer_data": [ "objective", "purpose_ref", "excluded_objectives" ] }, { "id": "purpose-outcome-q02", "text": "Which deliverables and acceptance criteria define completion of this entrustment?", "kind": "requirement", "answer_data": [ "deliverable_refs", "acceptance_criteria", "acceptance_owner" ] }, { "id": "purpose-outcome-q03", "text": "Which task or case references supply context without transferring their ownership?", "kind": "composition", "answer_data": [ "work_context_refs", "reference_versions", "boundary_notes" ] }, { "id": "purpose-outcome-q04", "text": "Which ambiguity in the objective requires clarification before consequential work?", "kind": "decision", "answer_data": [ "ambiguity", "clarification_owner", "pause_condition" ] } ], "data_elements": [ { "id": "purpose-outcome-data01", "name": "Entrusted objective", "description": "Purpose and intended result stated independently of tool commands.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "purpose-outcome-data02", "name": "Completion criteria", "description": "Candidate criteria and authorized acceptance role; results remain externally evidenced.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "purpose-outcome-data03", "name": "Work context references", "description": "Optional separately mastered tasks or cases.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "purpose-outcome-artifact", "name": "Entrusted objective record", "description": "Versioned evidence view for entrusted objective; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "action-scope-layer", "name": "Action and resource boundaries", "description": "Represent explicit action-resource pairs and exclusions. Missing scope is unknown, not unrestricted.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ], "findings": [ { "id": "action-scope", "name": "Permitted and prohibited work", "description": "Represent explicit action-resource pairs and exclusions. Missing scope is unknown, not unrestricted.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ], "questions": [ { "id": "action-scope-q01", "text": "Which exact action-resource pairs are within this mandate?", "kind": "constraint", "answer_data": [ "allowed_pairs", "resource_refs", "action_vocabulary" ] }, { "id": "action-scope-q02", "text": "Which prohibitions still apply even when a broad objective suggests an action?", "kind": "security", "answer_data": [ "prohibited_pairs", "restriction_basis", "governing_policy_refs" ] }, { "id": "action-scope-q03", "text": "Which recipient, tenant or resource audience limits apply to each permission?", "kind": "access", "answer_data": [ "audience_refs", "tenant_ref", "recipient_limits" ] }, { "id": "action-scope-q04", "text": "How will a binding avoid unintended combinations when projecting paired permissions?", "kind": "interoperability", "answer_data": [ "mapping_profile", "pair_preservation_rule", "loss_report_ref" ] } ], "data_elements": [ { "id": "action-scope-data01", "name": "Permission pairs", "description": "Proposed collection of action, resource and audience tuples, not a Cartesian expansion of unrelated arrays.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] }, { "id": "action-scope-data02", "name": "Explicit exclusions", "description": "Prohibitions and policy references; empty means no exclusions recorded, not universal permission.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "action-scope-artifact", "name": "Scope matrix", "description": "Versioned evidence view for permitted and prohibited work; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "conditions-oversight", "name": "Conditions and oversight", "description": "Bind resource limits, obligations and human decision points to the mandate.", "rationale": "Conditions narrow entrusted work and identify when the delegate must stop for review.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008" ], "layers": [ { "id": "constraints-budget-layer", "name": "Conditions and limits", "description": "Proposed profile conditions can include expenditure, count, duration, data purpose and operating context; enforcement is external.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ], "findings": [ { "id": "constraints-budget", "name": "Bounded resources and context", "description": "Proposed profile conditions can include expenditure, count, duration, data purpose and operating context; enforcement is external.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ], "questions": [ { "id": "constraints-budget-q01", "text": "Which resource ceilings apply and what units and aggregation windows define them?", "kind": "measurement", "answer_data": [ "limit_value", "unit_or_currency", "window", "aggregation_scope", "budget_master_ref" ] }, { "id": "constraints-budget-q02", "text": "Which time, location, data-use or environmental conditions restrict the entrusted work?", "kind": "spatial", "answer_data": [ "condition_expression", "jurisdiction_or_location_ref", "context_source", "purpose_limit" ] }, { "id": "constraints-budget-q03", "text": "Which duties must be satisfied before a permission may be exercised?", "kind": "requirement", "answer_data": [ "duty_refs", "satisfaction_evidence_ref", "ordering_rule" ] }, { "id": "constraints-budget-q04", "text": "What happens when a budget observation is stale, a unit is unknown or concurrent delegates share a ceiling?", "kind": "exception", "answer_data": [ "freshness_limit", "unknown_rule", "reservation_authority_ref", "stop_condition" ] } ], "data_elements": [ { "id": "constraints-budget-data01", "name": "Limit definitions", "description": "Ceiling, unit, aggregation scope and period; no balance or reservation engine is owned here.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] }, { "id": "constraints-budget-data02", "name": "Contextual conditions", "description": "Conditions and external evidence source, including explicit unknown handling.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] }, { "id": "constraints-budget-data03", "name": "Duty references", "description": "Optional prerequisite evidence references; the responsible process performs the duty.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "constraints-budget-artifact", "name": "Mandate conditions record", "description": "Versioned evidence view for bounded resources and context; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "oversight-gates-layer", "name": "Review and escalation", "description": "Specify review gates and escalation roles at policy level; an escalation cannot itself expand authority.", "source_refs": [ "SRC-003", "SRC-008" ], "findings": [ { "id": "oversight-gates", "name": "Human review requirements", "description": "Specify review gates and escalation roles at policy level; an escalation cannot itself expand authority.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "oversight-gates-q01", "text": "Which proposed effects require an authorized reviewer before proceeding?", "kind": "decision", "answer_data": [ "review_trigger", "effect_class", "reviewer_role", "approval_ref" ] }, { "id": "oversight-gates-q02", "text": "What exact mandate revision and proposed action must a review decision bind?", "kind": "validation", "answer_data": [ "mandate_revision", "action_digest_or_ref", "review_validity", "review_scope" ] }, { "id": "oversight-gates-q03", "text": "Which unavailable-reviewer or emergency conditions require pause or refusal?", "kind": "exception", "answer_data": [ "unavailable_rule", "emergency_policy_ref", "refusal_reason" ] }, { "id": "oversight-gates-q04", "text": "Where are incidents, complaints or conflicting instructions referred for resolution?", "kind": "process", "answer_data": [ "escalation_owner", "case_ref", "stop_rule", "resolution_ref" ] } ], "data_elements": [ { "id": "oversight-gates-data01", "name": "Review gate definitions", "description": "Triggers, authorized reviewer, binding requirements and validity; no automatic approval from silence.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "oversight-gates-data02", "name": "Escalation references", "description": "External incident and review process references; dangerous matters remain policy-only.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "oversight-gates-artifact", "name": "Oversight schedule", "description": "Versioned evidence view for human review requirements; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "delegation-chain", "name": "Delegation and authority bindings", "description": "Record subdelegation limits and credential mappings without creating authority by copying context.", "rationale": "The chain of entrustment is separate from historical actor claims and technical access.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ], "layers": [ { "id": "subdelegation-layer", "name": "Subdelegation conditions", "description": "A child mandate is a distinct relationship. Proposed attenuation rules require explicit permission and evidence of no widening.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "findings": [ { "id": "subdelegation", "name": "Permitted onward entrustment", "description": "A child mandate is a distinct relationship. Proposed attenuation rules require explicit permission and evidence of no widening.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "questions": [ { "id": "subdelegation-q01", "text": "Does this mandate explicitly allow onward delegation and to which delegate class?", "kind": "authority", "answer_data": [ "subdelegation_allowed", "eligible_delegate_refs", "authority_evidence_ref" ] }, { "id": "subdelegation-q02", "text": "Which parent revision and depth or expiry bounds must a child mandate preserve?", "kind": "relationship", "answer_data": [ "parent_mandate_ref", "parent_revision", "maximum_depth", "child_interval" ] }, { "id": "subdelegation-q03", "text": "What evidence supports that a proposed child does not widen scope, budget or duties?", "kind": "validation", "answer_data": [ "attenuation_review_ref", "scope_comparison_ref", "shared_budget_ref", "unresolved_terms" ] }, { "id": "subdelegation-q04", "text": "How are cycles, missing ancestors and parent withdrawal handled without treating actor history as permission?", "kind": "security", "answer_data": [ "chain_status", "cycle_check_ref", "parent_status_source", "reliance_rule" ] } ], "data_elements": [ { "id": "subdelegation-data01", "name": "Subdelegation rule", "description": "Default is not allowed until explicit authority is recorded; this is a proposed adoption rule.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "subdelegation-data02", "name": "Parent mandate binding", "description": "Absent for a root mandate; referenced parents are separately versioned.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "subdelegation-data03", "name": "Child mandate references", "description": "Optional independently governed children, never embedded authority expansion.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "subdelegation-artifact", "name": "Delegation lineage record", "description": "Versioned evidence view for permitted onward entrustment; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "credential-binding-layer", "name": "Technical authorization alignment", "description": "Record external authorization bindings and discrepancies; never store bearer secrets or equate capability with permission.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ], "findings": [ { "id": "credential-binding", "name": "Mandate to credential references", "description": "Record external authorization bindings and discrepancies; never store bearer secrets or equate capability with permission.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ], "questions": [ { "id": "credential-binding-q01", "text": "Which external grant or credential reference is bound to this mandate revision?", "kind": "interoperability", "answer_data": [ "grant_ref", "credential_metadata_ref", "issuer", "binding_profile", "mandate_revision" ] }, { "id": "credential-binding-q02", "text": "Which evidence distinguishes the current actor from the represented principal?", "kind": "identity", "answer_data": [ "current_actor_ref", "represented_subject_ref", "binding_evidence" ] }, { "id": "credential-binding-q03", "text": "What authorization decision reference shows the actual allowed subset for a proposed action?", "kind": "evidence", "answer_data": [ "decision_ref", "requested_scope_ref", "granted_scope_ref", "decision_time" ] }, { "id": "credential-binding-q04", "text": "What prevents a handoff, prompt or credential refresh from silently widening the mandate?", "kind": "constraint", "answer_data": [ "renewal_rule", "mapping_version", "scope_change_review_ref", "handoff_ref" ] } ], "data_elements": [ { "id": "credential-binding-data01", "name": "Authorization references", "description": "Non-secret references to external grant, decision and credential metadata only.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "credential-binding-data02", "name": "Binding profile", "description": "Versioned mapping and loss report; unresolved semantics block reliance.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "credential-binding-artifact", "name": "Authorization binding record", "description": "Versioned evidence view for mandate to credential references; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "validity-change", "name": "Validity and change", "description": "Record effective intervals, change decisions and withdrawal observations.", "rationale": "Mandate state and downstream enforcement are separate and can diverge.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ], "layers": [ { "id": "effective-validity-layer", "name": "Time and state", "description": "Keep asserted status, effective interval and observation freshness distinct. Missing expiry is unresolved unless a profile explicitly governs it.", "source_refs": [ "SRC-003", "SRC-006" ], "findings": [ { "id": "effective-validity", "name": "Mandate effectiveness", "description": "Keep asserted status, effective interval and observation freshness distinct. Missing expiry is unresolved unless a profile explicitly governs it.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "effective-validity-q01", "text": "When does this mandate revision become effective and when must it stop being relied on?", "kind": "temporal", "answer_data": [ "effective_from", "effective_until", "timezone_offset", "expiry_basis" ] }, { "id": "effective-validity-q02", "text": "What evidence supports the asserted state as proposed, active, suspended, ended or disputed?", "kind": "state", "answer_data": [ "asserted_state", "state_basis_ref", "effective_time", "observed_at" ] }, { "id": "effective-validity-q03", "text": "Which prerequisites and approvals must be current for reliance at a particular time?", "kind": "requirement", "answer_data": [ "prerequisite_refs", "approval_validity", "status_freshness_rule" ] }, { "id": "effective-validity-q04", "text": "How are clock uncertainty, missing status and offline operation handled?", "kind": "quality", "answer_data": [ "clock_uncertainty", "maximum_status_age", "offline_policy_ref", "reliance_block" ] } ], "data_elements": [ { "id": "effective-validity-data01", "name": "Effectiveness assertion", "description": "State, time interval, basis and observation timestamps; descriptive, not a runtime verdict.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "effective-validity-data02", "name": "Freshness rule", "description": "Maximum tolerable observation age and unknown-state handling in the adopting profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "effective-validity-artifact", "name": "Validity assertion record", "description": "Versioned evidence view for mandate effectiveness; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "amend-withdraw-layer", "name": "Amendment and withdrawal", "description": "Record changes and end-of-authority decisions without claiming that credentials, running work or past effects were undone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "amend-withdraw", "name": "Revision and termination evidence", "description": "Record changes and end-of-authority decisions without claiming that credentials, running work or past effects were undone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "amend-withdraw-q01", "text": "Who authorized an amendment, suspension, renewal or withdrawal and for which effective time?", "kind": "authority", "answer_data": [ "change_actor_ref", "decision_ref", "change_type", "effective_at" ] }, { "id": "amend-withdraw-q02", "text": "Which predecessor revision does the change supersede and how are conflicting edits detected?", "kind": "lifecycle", "answer_data": [ "predecessor_revision", "expected_revision", "conflict_record_ref" ] }, { "id": "amend-withdraw-q03", "text": "Which downstream systems or child mandates require notification and what acknowledgements exist?", "kind": "event", "answer_data": [ "notification_targets", "notice_refs", "acknowledgement_refs", "propagation_unknowns" ] }, { "id": "amend-withdraw-q04", "text": "Which work or effects remain in flight after withdrawal and who owns stopping or remedying them?", "kind": "process", "answer_data": [ "inflight_run_refs", "stop_decision_ref", "remedy_owner", "unconfirmed_effects" ] } ], "data_elements": [ { "id": "amend-withdraw-data01", "name": "Change record", "description": "Versioned change decision and its effective and recorded times.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "amend-withdraw-data02", "name": "Propagation evidence", "description": "Optional external notification and status evidence; lack of acknowledgement stays unknown.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "amend-withdraw-artifact", "name": "Mandate change record", "description": "Versioned evidence view for revision and termination evidence; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "evidence-assurance", "name": "Evidence and assurance", "description": "Link observation evidence and profile review without claiming operational compliance.", "rationale": "Review needs traceable assertions, limited disclosure and visible uncertainty.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "evidence-accountability-layer", "name": "Evidence and disclosure", "description": "Reference execution and review evidence while retaining source, observation time and recipient-specific disclosure rules.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ], "findings": [ { "id": "evidence-accountability", "name": "Mandate evidence index", "description": "Reference execution and review evidence while retaining source, observation time and recipient-specific disclosure rules.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ], "questions": [ { "id": "evidence-accountability-q01", "text": "Which run or decision evidence cites the mandate revision used at the time?", "kind": "provenance", "answer_data": [ "run_refs", "decision_refs", "mandate_revision", "assertion_source" ] }, { "id": "evidence-accountability-q02", "text": "Which observed departures from the mandate are confirmed, disputed or still unknown?", "kind": "quality", "answer_data": [ "departure_ref", "assessment_state", "contrary_evidence_refs", "review_owner" ] }, { "id": "evidence-accountability-q03", "text": "Who may see the principal, scope and evidence fields for a stated purpose?", "kind": "privacy", "answer_data": [ "recipient_role", "purpose", "field_restrictions", "redacted_view_ref" ] }, { "id": "evidence-accountability-q04", "text": "Which retention, hold and disposal rules apply to mandate evidence and references?", "kind": "retention", "answer_data": [ "retention_policy_ref", "hold_ref", "disposal_authority", "tombstone_rule" ] } ], "data_elements": [ { "id": "evidence-accountability-data01", "name": "Evidence references", "description": "Evidence master IDs and revisions with author and observed time; a digest establishes integrity, not truth.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] }, { "id": "evidence-accountability-data02", "name": "Disclosure and retention bindings", "description": "Profile policies for payload minimization, holds and minimal lawful continuity.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "evidence-accountability-artifact", "name": "Mandate evidence index", "description": "Versioned evidence view for mandate evidence index; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-004", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "profile-assurance-layer", "name": "Profile and conformance", "description": "Pin the adopting profile, mapping versions and unresolved tests; a machine-valid research document is not an executable mandate schema.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007", "SRC-008" ], "findings": [ { "id": "profile-assurance", "name": "Adoption limits and mapping review", "description": "Pin the adopting profile, mapping versions and unresolved tests; a machine-valid research document is not an executable mandate schema.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007", "SRC-008" ], "questions": [ { "id": "profile-assurance-q01", "text": "Which profile defines vocabulary, conflict precedence and unknown handling for this mandate?", "kind": "classification", "answer_data": [ "profile_ref", "profile_version", "conflict_strategy", "unknown_rule" ] }, { "id": "profile-assurance-q02", "text": "Which mappings preserve meaning and which extensions or losses remain unresolved?", "kind": "interoperability", "answer_data": [ "mapping_refs", "unsupported_terms", "loss_report_ref", "extension_namespace" ] }, { "id": "profile-assurance-q03", "text": "What evidence tests expired, disputed, stale, over-budget and revoked-parent cases?", "kind": "validation", "answer_data": [ "fixture_refs", "expected_outcomes", "test_report_refs", "unverified_cases" ] }, { "id": "profile-assurance-q04", "text": "Which legal, sector or safety assumptions still need qualified review before use?", "kind": "constraint", "answer_data": [ "applicability_assumptions", "qualified_reviewer", "open_holds", "review_due" ] } ], "data_elements": [ { "id": "profile-assurance-data01", "name": "Adoption profile", "description": "Required before operational use; profile governs trust, conflict rules and local semantics.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-007", "SRC-008" ] }, { "id": "profile-assurance-data02", "name": "Conformance evidence", "description": "Optional references to future instance tests, mappings and review decisions.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "profile-assurance-artifact", "name": "Profile assurance record", "description": "Versioned evidence view for adoption limits and mapping review; reference authoritative records and restrict sensitive payloads. Not a credential or execution command.", "media_or_form": [ "Structured record", "Human-readable view" ], "serial": true, "identity_strategy": "Authoritative master-system identifier plus immutable revision; otherwise governed IRI, then Dimension-assigned UUID. Sequence is a display label, never identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-proposal", "name": "Register mandate proposal", "description": "Proposed local record operation, not implemented by this research package.", "inputs": [ "Principal and delegate references", "bounded objective", "proposed terms" ], "outputs": [ "Proposed mandate revision or unresolved-reference report" ], "preconditions": [ "Caller has purpose-limited record access under the adopting Dimension policy.", "Exact mandate identity, expected revision and evidence provenance are supplied; otherwise refuse or return unknown.", "Authority-sensitive changes require a separately authorized decision reference." ], "effects": [ "Create a local proposed record only; no grant, token or executable authority is issued.", "Record attribution and revision history subject to retention and disclosure policy." ], "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "record-authority", "name": "Record authority evidence", "description": "Proposed local record operation, not implemented by this research package.", "inputs": [ "Mandate revision", "issuer basis", "acceptance or refusal evidence references" ], "outputs": [ "Attributed authority evidence or refusal to attach unbound evidence" ], "preconditions": [ "Caller has purpose-limited record access under the adopting Dimension policy.", "Exact mandate identity, expected revision and evidence provenance are supplied; otherwise refuse or return unknown.", "Authority-sensitive changes require a separately authorized decision reference." ], "effects": [ "Attach evidence to an exact revision; do not authenticate parties or decide legal authority.", "Record attribution and revision history subject to retention and disclosure policy." ], "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "revise-terms", "name": "Propose revised terms", "description": "Proposed local record operation, not implemented by this research package.", "inputs": [ "Expected revision", "proposed scope and conditions", "change rationale" ], "outputs": [ "New proposed revision or concurrency conflict" ], "preconditions": [ "Caller has purpose-limited record access under the adopting Dimension policy.", "Exact mandate identity, expected revision and evidence provenance are supplied; otherwise refuse or return unknown.", "Authority-sensitive changes require a separately authorized decision reference." ], "effects": [ "Retain predecessor linkage and route material scope changes to the responsible reviewer; no automatic activation.", "Record attribution and revision history subject to retention and disclosure policy." ], "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "link-child", "name": "Link proposed child mandate", "description": "Proposed local record operation, not implemented by this research package.", "inputs": [ "Parent and child references", "explicit onward-delegation basis", "external attenuation review" ], "outputs": [ "Qualified child reference or unresolved-chain report" ], "preconditions": [ "Caller has purpose-limited record access under the adopting Dimension policy.", "Exact mandate identity, expected revision and evidence provenance are supplied; otherwise refuse or return unknown.", "Authority-sensitive changes require a separately authorized decision reference." ], "effects": [ "Record relationship evidence only; do not issue child authority or calculate enforceable permissions.", "Record attribution and revision history subject to retention and disclosure policy." ], "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] }, { "id": "record-withdrawal", "name": "Record withdrawal evidence", "description": "Proposed local record operation, not implemented by this research package.", "inputs": [ "Authoritative decision reference", "effective time", "downstream acknowledgement references" ], "outputs": [ "Withdrawal assertion and unresolved propagation list" ], "preconditions": [ "Caller has purpose-limited record access under the adopting Dimension policy.", "Exact mandate identity, expected revision and evidence provenance are supplied; otherwise refuse or return unknown.", "Authority-sensitive changes require a separately authorized decision reference." ], "effects": [ "Record local status evidence; do not revoke tokens, cancel runs or undo prior effects.", "Record attribution and revision history subject to retention and disclosure policy." ], "source_refs": [ "SRC-005", "SRC-006" ] }, { "id": "inspect-completeness", "name": "Inspect record completeness", "description": "Proposed local record operation, not implemented by this research package.", "inputs": [ "Mandate revision", "selected profile", "evidence and mapping references" ], "outputs": [ "Missing-field, stale-evidence and unresolved-reference report" ], "preconditions": [ "Caller has purpose-limited record access under the adopting Dimension policy.", "Exact mandate identity, expected revision and evidence provenance are supplied; otherwise refuse or return unknown.", "Authority-sensitive changes require a separately authorized decision reference." ], "effects": [ "Read-only structural review; no runtime permission, legal-validity or conformance verdict.", "Record attribution and revision history subject to retention and disclosure policy." ], "source_refs": [ "SRC-002", "SRC-006", "SRC-007", "SRC-008" ] } ], "composition": [ { "target": "WM-AI-002", "relation": "REFERENCE", "purpose": "Candidate reference binding to the delegate master; registry parent is not inheritance. No agent lifecycle owned here. Instance profiles must resolve and pin required bindings; no runtime dependency is installed by this draft.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-AI-004", "relation": "REFERENCE", "purpose": "Optional execution evidence references; run planning, execution, costs and audit trail remain in the run master. Instance profiles must resolve and pin required bindings; no runtime dependency is installed by this draft.", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] }, { "target": "WM-AI-005", "relation": "REFERENCE", "purpose": "Optional configuration version reference. Configuration text cannot amend authority. Instance profiles must resolve and pin required bindings; no runtime dependency is installed by this draft.", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] }, { "target": "WM-AI-016", "relation": "REFERENCE", "purpose": "Optional handoff reference carrying mandate identity; message transfer is not delegation authorization. Instance profiles must resolve and pin required bindings; no runtime dependency is installed by this draft.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-AI-017", "relation": "REFERENCE", "purpose": "Optional tool description reference; interface capability is separate from permitted use. Instance profiles must resolve and pin required bindings; no runtime dependency is installed by this draft.", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] }, { "target": "RFC 8693", "relation": "ALIGN", "purpose": "Conceptual current-actor and subject mapping, not actor-history authorization. No conformance claim.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "RFC 9396", "relation": "ALIGN", "purpose": "Conceptual fine-grained authorization details mapping with pair preservation. No conformance claim.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "ODRL 2.2", "relation": "ALIGN", "purpose": "Conceptual policy terms only; conflict and unknown rules need a specified profile. No conformance claim.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "PROV-O", "relation": "ALIGN", "purpose": "Provenance alignment; provenance cannot establish current permission. No conformance claim.", "required": false, "source_refs": [ "SRC-004" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Identify an accountable mandate steward, authority reviewer and evidence custodian by role and master reference.", "Declare trust domain, profile version, effective-time rules and authority verification responsibilities.", "Declare disclosure, retention, conflict resolution and external enforcement responsibilities before operational adoption." ], "namespace_guidance": "Separate mandate, revision, artifact and external party namespaces. Preserve issuer-qualified identifiers; no dates as identity. Local extensions require governed names and review.", "registry_links": [ "vr.wm-ai-015", "WM-AI-002 candidate delegate binding", "Adopting Dimension profile and authority registry" ] }, "canon_and_patch": { "canonicalization_rules": [ "Keep original evidence and normalized projections distinguishable; record profile version and mapping losses.", "Preserve exact action-resource pairing, units, issuer namespaces and effective times; do not normalize away authorization distinctions." ], "patch_rules": [ "Require expected revision, authorized change basis, author, rationale and affected scope; concurrent edits yield a conflict.", "A principal or delegate replacement requires the profile continuity test; widening authority requires a new reviewed revision, never a silent patch." ], "compatibility_rules": [ "Unknown conditions, unsupported vocabulary or unresolved policy conflicts block reliance. This is a proposed adoption rule, not a claim about every aligned standard.", "Schema-valid projections do not prove equivalent permissions; require profile-specific mapping tests." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "Dimension-assigned UUID or ULID" ], "timestamp_rule": "Use RFC 3339 with seconds and explicit offset or Z; preserve effective event time separately from observation and ingestion time, with uncertainty when relevant.", "serial_naming_rule": "Use a stable mandate identifier, artifact role and revision sequence; a filename or timestamp never replaces master identity.", "integrity_rule": "Record digest algorithm, bytes covered and origin reference for immutable revisions; external signature verification remains a referenced service. Never retain bearer tokens, private keys or credential payloads in mandate artifacts." }, "policies": [ "Mandate data is descriptive and must not be interpreted as a command to execute or an independently sufficient authorization.", "Missing authority, stale status, unresolved conflicts and unsupported conditions are explicit unknowns that prevent reliance under the proposed profile.", "Keep dangerous activity at policy level; adoption requires qualified sector and safety review.", "No automatic subdelegation, scope expansion, approval by silence or emergency override. Record separately authorized exceptions with scope and expiry.", "Minimize personal data and secret-bearing references. Retain necessary history only under an applicable policy, not indefinitely." ], "crud": { "read": [ "Authenticate purpose and recipient role; return a field-limited view with revision, evidence age and uncertainty." ], "create": [ "Create a proposed mandate with stable identity, referenced parties, objective and declared unknowns; creation does not activate authority." ], "update": [ "Require optimistic revision matching and evidence for authority-sensitive changes; preserve predecessor linkage and unresolved propagation state." ], "delete": [ "Retire or supersede mandate records according to the adopting Dimension retention and hold policy; the designated record custodian owns payload deletion and minimal lawful tombstones. Deletion does not revoke credentials, erase external evidence or cancel effects.", "Respect approved erasure or redaction of personal payloads; keep only lawful minimal reference continuity and record disposition evidence." ] }, "roles": [ { "name": "Principal", "responsibilities": [ "Identifies intended work and the basis for entrustment." ] }, { "name": "Authorized issuer", "responsibilities": [ "Provides evidence of authority to issue or change terms." ] }, { "name": "Delegate", "responsibilities": [ "References the accepted revision and reports uncertainty or departures." ] }, { "name": "Authority reviewer", "responsibilities": [ "Reviews scope, exceptions and material changes without relying solely on technical access." ] }, { "name": "Mandate steward", "responsibilities": [ "Maintains identifiers, revisions, profiles and quality." ] }, { "name": "Evidence custodian", "responsibilities": [ "Controls disclosure, retention and disposition of local evidence." ] } ], "access": { "default_rule": "Deny access unless recipient purpose and role are authorized by the adopting Dimension; access to read or edit a mandate never grants authority to perform the entrusted work.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Any exceptional access needs an authorized, time-limited basis and minimal disclosure; unknown authority is not an exception." ], "audit_requirements": [ "Reference attributable access and change events in the external audit master, including denied attempts and redactions.", "Keep reviewer decisions bound to exact mandate revisions; log evidence references without bearer secrets." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Nearest owner and Dimension policies", "AGENTS.md", "spec.yaml and visible research holds", "Pinned authority and adoption profile", "Current mandate revision and evidence references" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one bounded, versioned agent delegation relationship. A separate frozen no-tools local self-audit found no critical conflicts. Independent review, source/version verification, qualified adoption profiles and executable conformance remain open; this is a noncanonical reviewable draft, not an authorization engine or legal instrument.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable relationship identity and revision; distinct party and credential references." }, { "dimension": "lifecycle", "status": "covered", "notes": "Proposed, accepted, active, disputed, suspended and ended assertions; changes require evidence." }, { "dimension": "relationships", "status": "covered", "notes": "Principal, delegate, parent and child mandates, run and handoff references." }, { "dimension": "temporal", "status": "covered", "notes": "Effective interval, observation age, propagation and uncertain clocks." }, { "dimension": "provenance", "status": "covered", "notes": "Attributed evidence and revision references do not prove current authority." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based stewardship and authority review; external masters retain their own functions." }, { "dimension": "validation", "status": "gap", "notes": "Research schema is provided; nested instance schema, executable semantics and fixtures remain to be developed." }, { "dimension": "access", "status": "covered", "notes": "Purpose-limited views at all four structural scopes and separation from execution authority." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Profile-owned disposal, holds, redaction and minimal lawful tombstones." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual alignments only; profile mappings and loss tests remain unimplemented." }, { "dimension": "direct properties", "status": "covered", "notes": "Purpose, permitted work, conditions, budget and effective state are nonphysical properties." }, { "dimension": "physical measurements", "status": "not-applicable", "notes": "The relationship has no mass, dimensions or physical sensing; contextual ceilings can still have units." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Evidence source, observation age and unknown state are explicit." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Proposed local record operations are distinct from external delegated execution." }, { "dimension": "authority and safety", "status": "covered", "notes": "No implied onward authority or dangerous operational instructions; qualified review remains required." }, { "dimension": "independent review", "status": "gap", "notes": "Single-provider waiver; local no-tools audit cannot substitute for independent external review." }, { "dimension": "source verification", "status": "gap", "notes": "Selected web-service excerpts reviewed; direct HTTP unattempted under reported sandbox restriction and current errata not fully checked." } ], "known_omissions": [ "Nested instance schema, units vocabulary, mapping implementations and executable adoption tests.", "Qualified jurisdiction and sector review, including authority, consent, privacy and safety requirements.", "Trust establishment, budget reservation, enforcement and revocation propagation implementation remain external.", "Independent external review and current source/version/errata verification." ], "conflicts": [], "regional_assumptions": [ "No jurisdiction is assumed; authority and legal effect require the adopting profile and qualified review.", "NIST guidance supplies conceptual context and is not a universal legal obligation." ], "adversarial_checks": [ "Challenge whether an authentic credential or valid signature proves the principal authorized the entrusted objective.", "Challenge child mandates that expand scope, exceed shared ceilings or outlive withdrawn parents.", "Challenge stale active status, missing clocks, concurrent edits and unacknowledged downstream withdrawal.", "Challenge prompts, handoffs and historical actor claims being mistaken for authority.", "Challenge Cartesian expansion of action-resource pairs, empty restrictions and unknown policy semantics." ] }, "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": "relationship", "status": "accepted", "rationale": "The root is an identified entrustment between principal and delegate for a bounded work context, with revisions and authority evidence. The registry standalone-mm value describes the record plane. Parent WM-AI-002 is reconciled as a contextual reference, not inheritance; agents, credentials, runs, handoffs and enforcement remain separately mastered." }, "decisions": [ { "concept": "Root kind", "disposition": "accepted", "rationale": "The subject is an identified, versioned entrustment connecting a principal, delegate and work context. Relationship is defensible even though its evidence has entity identifiers; it is neither the agent nor one execution event." }, { "concept": "Registry parent", "disposition": "qualified", "rationale": "The registry standalone-mm value is a record-plane classification. Parent WM-AI-002 supplies context, not subtype inheritance. The draft explicitly references the delegate master and retains agent lifecycle outside the boundary." }, { "concept": "Principal, issuer and delegate", "disposition": "accepted", "rationale": "Identity, issuing authority, acceptance and accountability are separate assertions. Missing or disputed authority remains visible and blocks reliance under the proposed adoption policy." }, { "concept": "Objective and permissions", "disposition": "separated", "rationale": "An entrusted goal does not authorize every means of achieving it. Explicit action-resource pairs, exclusions and audience limits constrain the objective; unknown scope is not unrestricted." }, { "concept": "Cartesian permission widening", "disposition": "rejected", "rationale": "The scope finding preserves pairs and asks for mapping loss evidence. An array projection cannot silently create new combinations of actions, resources and recipients." }, { "concept": "Budget and oversight", "disposition": "accepted as proposed profile rules", "rationale": "Units, aggregation windows, shared ceilings, prerequisite duties and review bindings are questions for adoption. Reservation, enforcement and reviewer decisions remain external. Silence is not approval." }, { "concept": "Subdelegation", "disposition": "qualified", "rationale": "Child mandates are separate relationships with explicit permission and externally reviewed attenuation. The model does not infer child rights from copied task context, actor history or an unverified parent reference." }, { "concept": "Credentials and history", "disposition": "separated", "rationale": "Current actor, principal, grant reference and historical actors are distinguished. A technical token or handoff cannot substitute for mandate evidence or widen the mandate. No bearer secrets belong in these records." }, { "concept": "Validity and withdrawal", "disposition": "accepted with propagation uncertainty", "rationale": "Asserted state and effective times are distinct from observation time and downstream enforcement. Recording a withdrawal cannot cancel runs, revoke tokens or reverse effects; missing acknowledgements remain unknown." }, { "concept": "Local functions", "disposition": "accepted as proposed only", "rationale": "All six functions manage or inspect local records with role and revision conditions. They issue no operational authority and implement no runtime evaluator, budget engine, revocation service or execution control." }, { "concept": "Evidence, privacy and retention", "disposition": "accepted with profile dependency", "rationale": "Attribution and integrity do not prove truth. Recipient restrictions, scoped erasure, retention holds and minimal lawful tombstones govern evidence without requiring indefinite personal-data preservation." }, { "concept": "Candidate bindings and instance schema", "disposition": "deferred", "rationale": "Optional composition flags describe research-level candidate bindings, not optional identity for an operational mandate. Required instance bindings must be resolved by an adopting profile. Candidate object groups and illustrative states are not executable schemas." }, { "concept": "Source strength and design inference", "disposition": "limited", "rationale": "The evidence covers selected official web-service text, with only the NIST SP 800-162 abstract reviewed. The hierarchy and local rules are declared design inferences. Full text, current errata and profile mappings are not certified." }, { "concept": "External review", "disposition": "waived and held", "rationale": "No Claude or Grok result was attempted or admitted. This separate frozen semantic phase is local Codex self-audit, not independent external review; confidence cannot be high." } ], "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 independent second-provider review.", "Live source, version and errata verification remains incomplete. Selected web-service text was reviewed for eight official URLs, including only the SP 800-162 abstract. Direct HTTP checks were not attempted under the owner-reported sandbox restriction; all statuses are unmeasured, with zero measured HTTP 200 responses. The coordinator checker is prepared.", "Qualified adoption-profile review is required for authority, consent, jurisdiction, sector, safety, privacy, retention, budget semantics, oversight and exception handling before operational use. No legal effect or universal authorization semantics is certified.", "Nested instance schemas, pinned neighbor and trust bindings, vocabulary and unit profiles, loss-tested mappings and executable adversarial conformance fixtures remain incomplete. Runtime evaluation, enforcement, shared-budget control and revocation propagation require external implementations.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Restore independent external review and verify official versions, errata and claim support before canonical promotion.", "Develop an adopting profile with qualified authority and sector review, concrete instance schemas and pinned trust and neighbor bindings.", "Test ambiguous scope, unintended permission combinations, stale status, conflicting revisions, shared ceilings, child widening, parent withdrawal and delayed enforcement with external implementations." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }