# Migration / Residency Status

- Name: Migration / Residency Status
- Catalogue ID: WM-POL-029
- Registry ID: vr.wm-pol-029
- Type: Published Vercy relationship
- Version: 0.1.0-reviewable-draft
- Specification: https://ver.cy/models/wm-pol-029-migration-residency-status/spec.yaml
- Storage type: format-independent; select a binding in the page constructor
- Interface: https://ver.cy/models/wm-pol-029-migration-residency-status/#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-pol-029

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. The generated publication status
is package metadata and does not establish remote availability. Codex is the sole
active provider. Claude and Grok were skipped under the owner waiver; the local
no-tools self-audit is not independent external review.

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 an independent second-provider review.
- Source and version verification is incomplete. Three pages were readable through the web tool; five relied on selected official indexed evidence and returned browser challenges. The 2026-06-12 long-term-residence consolidation was identified but not fully verified. Direct HTTP checks were not attempted because of sandbox restrictions: zero measured HTTP 200 responses, not a finding of source failure. The coordinator must run check_sources.py and review content, versions and applicability.
- Qualified jurisdictional review must verify current law, national implementation, case-law effects, translation, licensing, category definitions, protection safeguards, lawful disclosure, retention, continuation and remedy rules. No universal status, deadline or eligibility decision rule is delivered.
- Nested instance schemas, pinned neighbor bindings, category-split parent resolution, provenance and permit mappings, executable conformance and adversarial instance fixtures remain incomplete. The package does not certify runtime behavior or legal compliance.
- Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft.