# Interaction Episode

- Name: Interaction Episode
- Catalogue ID: WM-MEM-003
- Registry ID: vr.wm-mem-003
- Type: Published Vercy entity
- Version: 0.1.0
- Specification: https://ver.cy/models/wm-mem-003-interaction-episode/spec.yaml
- Storage type: format-independent; select a binding in the page constructor
- Interface: https://ver.cy/models/wm-mem-003-interaction-episode/#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-mem-003

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 noncanonical reviewable draft. Codex is the sole
active provider. Claude and Grok were skipped with zero attempts under the
owner-authorized waiver; the separate local no-tools self-audit is not
independent external review. Local package generation establishes no remote
availability. Publication status describes the distribution package only.

Independent review, direct source/version verification, adoption-profile review
and executable conformance remain holds. Seven primary documents supplied
selected web-service evidence. Direct HTTP checks were not attempted under the
owner-reported sandbox restriction; every status is unmeasured. The coordinator
checker is in research/runs/wm-mem-003/check_sources.py. Consult the full holds in
spec.yaml before adoption. Do not promote this package to canonical status.

The root is a memory entity describing an interaction, not the interaction
occurrence itself. Preserve separate memory, occurrence, source and revision
identities. History preservation above is subject to the adopting retention and
redaction policy; it never mandates indefinite retention of personal payloads.
All functions are proposed and unimplemented. Candidate parent alignment and
neighbor links require tested bindings before operational use.