# Memory Quarantine and Redaction

- Name: Memory Quarantine and Redaction
- Catalogue ID: WM-MEM-020
- Registry ID: vr.wm-mem-020
- Type: Published Vercy entity
- Version: 0.1.0
- Specification: https://ver.cy/models/wm-mem-020-memory-quarantine-and-redaction/spec.yaml
- Storage type: format-independent; select a binding in the page constructor
- Interface: https://ver.cy/models/wm-mem-020-memory-quarantine-and-redaction/#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-020

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
   policy-permitted history and resolvable references under the case retention rules. 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. Generation does not establish remote availability. The sole provider is Codex; Claude and Grok were skipped with zero attempts. The separate local no-tools audit is not independent review.

Case history, selectors, hashes, mappings and evidence references remain subject to minimization and lawful retention. History preservation never requires indefinite raw payload storage. A case assertion or approved disposition does not execute a restriction, write, redaction or deletion.

Open 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 audit is not independent second-provider review.
- Source and version verification remains incomplete. Seven sources supplied selected official passages through the web service; direct HTTP was not attempted under the owner-reported sandbox restriction, with no measured statuses. Reconcile the older NIST control PDF with later releases, pin living guidance, and run check_sources.py outside the sandbox.
- Adoption requires qualified privacy, retention, preservation, disclosure, tenant and review-authority profiles. No universal legal compliance, anonymization, attack resistance or complete erasure is certified.
- Nested instance schemas, pinned neighbor bindings, selector and provenance mappings, authenticated receipt contracts and synthetic adversarial conformance fixtures remain incomplete. No runtime enforcement, transformation, concurrency or recovery guarantee is implemented.
- Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft.