# Agent Delegation Mandate

- Name: Agent Delegation Mandate
- Catalogue ID: WM-AI-015
- Registry ID: vr.wm-ai-015
- Type: Published Vercy relationship
- Version: 0.1.0-review.20261021
- Specification: https://ver.cy/models/wm-ai-015-agent-delegation-mandate/spec.yaml
- Storage type: format-independent; select a binding in the page constructor
- Interface: https://ver.cy/models/wm-ai-015-agent-delegation-mandate/#template-builder
- Processes: https://ver.cy/processes/
- Model agent protocol: https://ver.cy/model-agent-protocol.md
- Research evidence: https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-ai-015

Read this file first, then `spec.yaml`. Traverse Bundle to Layer to Finding to
Questions and Artifacts. The specification is published, while its research
assurance remains `reviewable-draft`. Do not claim canonical completeness
while `researchAdjudication.publicationHolds` is non-empty. Preserve source
references, master-system identity and access rules.

## Five-facet gate

Before creating or changing an instance, inspect the specification for explicit
coverage of: identity and class; direct properties; recognition and observation;
capabilities, behaviour and possible actions; context and evidence. Treat each
facet as required, optional, not applicable with a reason, or delegated through
a pinned model reference. Do not invent physical properties for abstract
objects. For physical measurements preserve units, tolerances, method,
conditions, observation time, uncertainty and provenance.

Keep capability, behaviour, state, transition, affordance, operation,
precondition, effect, reversibility, permission, constraint, hazard and failure
mode distinct. Resolve delegated child models and master systems instead of
copying their domains into this model.

## Agent lifecycle route

1. **Fill:** read the nearest owner and Dimension policies, resolve master
   identities, ask only for missing facts or authority, then record facts,
   hypotheses and unknowns distinctly with evidence and observation time.
2. **Extend:** propose a versioned extension when the published bundles and
   layers cannot express a required concept. Preserve stable IDs and namespace
   ownership; do not silently widen the model boundary.
3. **Edit:** validate authority, purpose, current version and concurrency before
   mutation. Preserve history and provenance. Treat access expansion, external
   writes and material side effects as confirmation-gated actions.
4. **Validate:** run schema, semantic, reference, permission, evidence and
   five-facet checks before and after a write. Report unresolved references,
   lossy projections, stale observations and publication holds.
5. **Retire:** deprecate and supersede through the declared lifecycle. Preserve
   immutable history and resolvable references. Require confirmation before
   deletion, destructive migration or irreversible external action.

Autonomous work is limited to policy-authorized reading, local population of
confirmed facts, validation, indexing and non-destructive maintenance. Propose
schema changes and new imports. Require confirmation for publication, broader
access, external writes, deletion and irreversible effects. Follow the model
agent protocol and the nearest local `AGENTS.md` whenever their rules are more
restrictive.

## Local package assurance

This package is local and noncanonical. Codex is the sole active research
provider; Claude and Grok were skipped with zero attempts. The separate local
no-tools self-audit is not independent external review. No deployment or remote
availability was checked or performed in this run.

Publication holds:

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

Bootstrap binding fields:

- Specification URL: https://ver.cy/models/wm-ai-015-agent-delegation-mandate/spec.yaml
- Storage type URL: supplied by the adopting Dimension when a storage binding is chosen; unresolved in this research draft
- Interface URL: supplied by the adopting Dimension when an interface is implemented; unresolved in this research draft
- Processes URL: supplied by the adopting Dimension for its authorized record and review processes; unresolved in this research draft

These catalogue URLs are package metadata, not evidence of a live deployment.
Operational reliance requires qualified profile review and current authority
evidence. Research package validation does not validate a mandate instance.