Elnor Repo Reader

ELNOR REPO READER TEXT MIRROR
Original path: OP-A and Operations and Trackers/OPA_FREEZE.md
Source repo: /Users/OpenClaw1/Elnor/Elnor Specs
Git branch: main
Git commit: dbaa25962edc11ab30e8d4ca1715f9ae5bf77331
Generated: 2026-06-09T01:23:58.539Z

---

# OPA Freeze Manifest

**Status:** ACTIVE
**Started:** 2026-05-27
**End date (hard):** 2026-06-17 (21 days)
**Renewable:** Yes, by writing a new manifest with documented reason. Max single freeze: 30 days.
**Reason:** Memory rebuild flatten (Stage 5R → Stage 5R3 → OP-A V4). OP-A is not updated for memory-plane retargeting until V4 ships.
**Freeze owner:** Will
**Review cadence:** Weekly Monday pass. Warnings fire 7 days before end_date and if deferred queue grows 2+ consecutive weeks.

## In-scope (DEFERRED, not actionable) — allowlist, no judgment fallback

- `Memory Rebuild Docs/` (entire folder)
- `Current Specs/DOC80 Memory Control Plane/` (entire folder)

## Out-of-scope (ACTIONABLE as normal)

All other paths. Edits to DOC72 / DOC73 / DOC1 / DOC8 / DOC25 / DOC15 that are NOT primarily memory-plane retargeting still generate actionable drift.

## Renewal procedure

To extend the freeze beyond 2026-06-17:

1. Will writes a new `OPA_FREEZE.md` (overwrite this file) with:
   - New `Started:` date (today, the day of renewal)
   - New `End date (hard):` (max 30 days from new Started)
   - Documented `Reason:` for renewal (why V4 hasn't shipped, what's remaining)
   - Same or refined `In-scope` allowlist (no operator-judgment fallback — must be explicit paths)
2. The prior manifest is archived (move to `Archived DOC OP-A and Operations DOCS/OPA_FREEZE_archived_YYYY-MM-DD.md`).
3. The nightly drift detector (`elnor-nightly-spec-sync` Piece 1) reads the new manifest on its next firing.
4. The Monday weekly pass reports the renewal in `MAINTENANCE_REPORT.md`.

**Renewal is NOT automatic.** If the end date passes without a new manifest in place, the freeze auto-expires (see below).

## Auto-expiration

When **2026-06-17** passes without renewal:

- Status field updates to `EXPIRED` (by the nightly drift detector on first post-expiration firing).
- Deferred items in `PENDING_OPA_UPDATES_DEFERRED.md` move to `PENDING_OPA_UPDATES.md` as ACTIONABLE.
- The next Monday `MAINTENANCE_REPORT.md` surfaces the merged queue as the top item.
- Will is notified that the freeze expired without renewal — choose to renew or accept the merged queue.

## Resolution (when V4 ships)

When OP-A V4 ships and ratifies the memory-plane retargeting:

- Move deferred items into the audit input (if not already consumed by Pass 2's retargeting).
- Status field updates to `RESOLVED`.
- This file is archived to `Archived DOC OP-A and Operations DOCS/OPA_FREEZE_resolved_YYYY-MM-DD.md` with a final timestamp.
- A new freeze may or may not be declared for subsequent flatten work (Stage 7+); that decision is independent.

## History

| Date | Action | By |
|---|---|---|
| 2026-05-27 | Initial freeze declared via Stage 5R3 Pass 0 setup | Cowork (under architect direction) |