# Rights / Entitlements

- Name: Rights / Entitlements
- Catalogue ID: WM-POL-014
- Registry ID: vr.wm-pol-014
- Type: Published Vercy relationship
- Version: 0.1.0-reviewable.20261006
- Specification URL: https://ver.cy/models/wm-pol-014-rights-entitlements/spec.yaml
- Storage type URL: unbound; the adopting Dimension must supply a concrete storage binding URL
- Interface URL: https://ver.cy/models/wm-pol-014-rights-entitlements/#template-builder
- Processes URL: 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-pol-014

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 is a locally generated reviewable draft, not a canonical release or proof
of remote availability. Codex is the only active provider. Claude and Grok were
skipped with zero attempts under the owner-authorized single-provider waiver.
The separate no-tools Codex self-audit is not independent external review.

Independent review, source/version checks, qualified legal profiles and
executable conformance remain holds. Direct HTTP was not attempted under the
owner-reported sandbox restriction; no status was measured. The coordinator
checker is in research/runs/wm-pol-014/check_sources.py.

Preservation of history in this bootstrap is subject to the payload-specific
retention and lawful-erasure rules in spec.yaml; it never requires perpetual
personal-data storage. Storage and runtime bindings remain unimplemented.