Area Reconciliation & Retirement

The honest answer to Code's flag

LEGACY-MOVE ×5 is a no-op — there is nothing to retire. Code was right to refuse to guess. I checked the live database and repo: there are no distinct "4.8-era" files sitting beside the v5 pages in any of the five areas. The v5 page is the page (exactly what B-T93 found: "replaced in place").

4.8 remnant files found

5 / 5

areas have a clear v5 canonical

already parked (dealspine, title-objections)

real overlap to review (Transaction)

Evidence: every candidate page reports has_shell=false and first_seen=2026-07-01 (the seed date) — i.e. the DB has no era tag because there is no second-era file to tag. If a 4.8 twin still existed, it would show up here as a separate row. It doesn't.

CDA

Commission Disbursement

No standalone page

CDA lives inside the clearing/title flow (lane-b/pure-clearing, pure-title-closing) — no separate cda*.html exists.

NO-OP · close

CRM

Client / People

pure-crm.html

Canonical v5. No 4.8 twin. (Separately tracked: CRM≈AMS shared-engine build.)

KEEP · canonical

LEGACY-MOVE-CRM

Nothing to move.

NO-OP · close

MLS

Search & MLS

pure-mls-console.html

Canonical v5 MLS surface.

KEEP · canonical

mls-hub.html · mls-directory.html

Distinct sub-tools (hub landing / directory of MLSs). Poppy to confirm not duplicative of the console.

REVIEW

LEGAL

Legal & Forms

pure-legal.html

Canonical v5 legal hub.

KEEP · canonical

legal-forms.html · legal-tracker.html

Distinct functions (forms library / matter tracking) — feed the Docs & Signatures build. Keep.

KEEP

TXN

Transaction — the one real overlap

pure-transaction-hub.html

Recommended canonical "home" for the transaction area.

KEEP · canonical

deals.html · transaction-room.html

Two more "transaction home" pages. Overlap with the hub — Poppy review: keep one as the room, park the redundant with a redirect to the hub.

REVIEW · park?

dealspine.html · pure-title-objections.html

Already parked (dealspine /transaction-room).

PARKED

deal-desk · title-closing · closeout · offer-builder · multi-offer · timeline · comms · 2× intake

Distinct functions, not duplicates. Keep all.

KEEP

How this fits Lane B's plan

MRG-B3 ("sign-off & retire area by area") is the parent; the 5 LEGACY-MOVE-* tickets are its execution arm. The 5 APPROVE-MRGB3-* area sign-offs were already Poppy-approved 7/6 under your blanket approval. This plan closes the loop: the sign-offs were valid, and execution = no files to move, plus one small Transaction overlap to tidy.

On your approval, Lane A will

Decision — approve / revise

Close LEGACY-MOVE ×5 as no-op / superseded-by-in-place-replacement (unblocks Code).
Poppy reviews the 3 REVIEW rows (mls-hub, mls-directory, deals/transaction-room). Any it deems redundant parked to the Boneyard with a named successor + 301 redirect — never deleted, fully restorable, kept long-term.
Nothing else moves. All KEEP pages stay exactly as they are.

Boneyard = long-term keeping, not deletion. Every park records the successor and injects a redirect ribbon; Restore un-parks in one click. The 90-day cold-review never auto-deletes — it asks you first.

Revise anything above and I'll update the plan before executing. Shattique's sign-off on the Transaction canonical (hub vs room) is the one open call.

PURE MLS Technologies · a product of Acquisto Real Estate · Area Reconciliation & Retirement review · sources: pure_pages · pure_boneyard · pure_board (MRG/LEGACY-MOVE)