Preliminary Document Recovery Disposition

• Status: RESEARCH / PRELIMINARY BASELINE
• Owning re-review: P1-001 — Canonical Documentation Structure, Integration And Cleanup; live status remains in the Roadmap
• Re-review observation: completed locally on 2026-07-30; this dated fact does not own Task or Git status
• Reviewed deletion: cc25434eaa0dfec09eaf22e1579f2fb00870b4e9
• Original preliminary review completed at: qa@444955b74ec65859275b47cad6b2c1b732ae8e17
• Exact original disposition: raw/preliminary-document-recovery-disposition-original.md
• Retention/removal: retain this final source-by-source reasoning and the exact original disposition while they remain useful; Git preserves removed source bytes and superseded execution wrappers

Meaning

A preliminary recovery pass reviewed all 113 paths changed by the deletion commit and recorded:

Preliminary decision	Paths
RESTORE	10
ABSORB	3
KEEP_RESEARCH	44
DELETE	56
Total	113

That work recovered useful bounded owners and consumer evidence, but it was performed before the canonical document hierarchy, roles, naming and templates were approved. Therefore these decisions are not final cleanup authority.

Current use

P1-001 used this baseline to avoid repeating the investigation and re-evaluated each material decision against the approved hierarchy.

Preliminary pass
= source inventory, consumer evidence, conflict findings, provisional disposition

P1-001
= completed hierarchy approval, canonical owner construction, content integration,
  usability/consumer verification, final disposition and cleanup

Valid results to preserve

The following results remain useful unless later evidence disproves them:

• the deletion commit changed 113 paths;
• several documents and tools had real Runtime/script/operator consumers;
• the former Product Charter and System Design contained valid target input; their content was absorbed and their old paths were removed after repository consumer migration and caller-zero;
• current Architecture/API/DB/UI rules remain distinct technical inputs;
• Operations Manual/process/API-catalog paths require coordinated consumer migration before movement;
• the old evolution/catalog/generated-status/fixed-Harness structures must not regain current authority;
• the full foundation research and recovered source snapshots must remain available during integration.

What must be re-reviewed

• whether each restored current owner belongs in the approved final hierarchy;
• whether ABSORB targets are the final canonical owners;
• whether KEEP_RESEARCH collections remain uniquely useful after integration;
• whether DELETE candidates contain any valid content not yet absorbed;
• whether rewritten operations/runbook/agent documents overlap the approved Development or Task standards;
• whether path and naming decisions match the new hierarchy;
• whether any consumer-bound file needs a coordinated move.

P1-001 approved-hierarchy re-review — 2026-07-30

Basis: Reset Revision 11, D2=B; D1,D3-D12=A.

The raw 113-path decisions are candidate actions, not final cleanup authority. The committed qa@508eb0be8 tree is the bounded manifest; unlisted paths default to KEEP_PENDING_REVIEW, while separate Local uncommitted artifacts cannot prove remote status or completion.

Source/family	Re-reviewed action	Current result / remaining gate
docs/product/PRODUCT_CHARTER.md	ABSORB -> DELETE	Product content mapped to Local docs/PRODUCT.md; repository executable consumers were zero, current links migrated and the obsolete path removed
.agents/rules/SYSTEM_DESIGN.md	ABSORB -> DELETE	target content mapped to Local docs/DESIGN.md; repository executable consumers were zero, current links migrated and the obsolete path removed
README.md, AGENTS.md, agent/operation routers	KEEP + REWRITE/NARROW	Local navigation points to approved owners and Roadmap; committed-current behavior must not be inferred
docs/templates/*.md	KEEP + REWRITE; former plan.md DELETE	optional examples aligned; valid Task fields moved to task.md; caller-zero plan.md deleted with Stage 6 approval
docs/OPERATIONS_MANUAL.md, docs/USER_MANUAL_INDEX.md	HISTORICAL — KEEP / KEEP + NARROW	this 2026-07-30 pre-reopen result preserved exact Runtime paths; the 2026-08-03 source-by-source disposition below supersedes it for the later DB Wiki absorption and deletion decision
docs/processes/**	KEEP + NARROW in P1	stale packet-status routing removed from the Standard; semantic lifecycle review remains P6
React/API target and inventory documents	REWRITE / KEEP DATED INPUT	API v2 remains framework-independent; React proposal is conditional; inventory counts remain dated evidence
old integration/performance/modernization plans	source-by-source DELETE or KEEP_RESEARCH	duplicate integration plan removed; modernization active/master authority retired but exact snapshots retained with correction headers because historical consumers remain
accepted transition-audit ADR	KEEP + REWRITE	current source/migration evidence linked; DB/Production state remains unverified
docs/research/**, scoped reference/performance observations and docs/current-state/**	KEEP_RESEARCH / KEEP	unique detail and provenance retained; historical status cannot authorize work
deleted evolution/Track/packet/register/catalog/generated/fixed-Harness paths	DELETE_CANDIDATE	remain absent; restore only for unique unabsorbed content or proven consumer

Final source-by-source cleanup — 2026-07-31

Removed path/family	Absorption or preservation basis
docs/product/PRODUCT_CHARTER.md	valid Product content absorbed into docs/PRODUCT.md; no executable consumer
.agents/rules/SYSTEM_DESIGN.md	valid target content absorbed into docs/DESIGN.md; historical clickable links migrated; no executable consumer
.agents/rules/INTEGRATION_PLAN.md	target rules routed to Design/Architecture/API contracts, current migration detail to API inventory and future order to Roadmap P2/P5/P7
docs/requirements/CTC_TO_BE_REQUIREMENTS.md	valid one-code/profile/module/runtime-preservation constraints already owned by Product/Design/Architecture; obsolete yard-centric target removed
docs/control-tower/work-item-agent-guide.md	no unique procedure; retirement detail retained in docs/migrations/control-tower-task-retirement.md
modernization move manifest/map/report	one-time generated archive-move outputs with no current consumer; Git preserves move and bytes
recovered raw/original-path/** and original execution wrapper	exact duplicates of named Git trees; per-path reasoning retained in the original disposition and this final wrapper

The following remain because they have distinct downstream value:

• performance plan/status/evidence for P9 reconciliation;
• modernization decisions, history, packet register, phase, contract, baseline and deep-analysis evidence;
• corrected historical ACTIVE.md and MASTER_PLAN.md snapshots while retained archive references still require their exact paths;
• dated current-state matrices and CTC operating-model input;
• platform-foundation research and evidence collections;
• consumer-bound manuals, workflows, registries, runbooks and API sources.

Authority boundary

The named Git tree retains the exact removed raw bytes, including their original historical headings and numeric labels. Those labels are provenance only. This wrapper and the retained original disposition do not own current Task status, Roadmap state, document hierarchy or final disposition.

P1 re-review addendum — 2026-08-03

The original paths remain the integration sources during this P1 re-review; classification is not a move to research. The following retained source sets were read against the current owner named here. Their stale delivery/status claims were narrowed in place, while their unique proposal or evidence content remains available to the owning Phase.

Absorbed historical P02A conflict findings

The former modernization conflict register recorded five dated integration findings now represented by current owners: snapshot metadata remains dated evidence rather than DB fact; Client-2 read-only browser proof is bounded and not CRUD/UAT proof; user procedure is owned by the DB Wiki while dated UAT is evidence; process workflows, not a test runbook, own atomic behavior; and no new process ID duplicates the existing order-to-packing owner. Historical findings do not override current Product, Design, Roadmap, technical contracts or process registry.

The former platform/tenant lifecycle delta is likewise absorbed as dated evidence: only the recorded Client-1 YMS/Dock adapter scope was verified; Client-2 end-to-end isolation, direct-ID, files, logs, jobs, providers and AI remained unproven. Current tenant/runtime contracts and activation belong to the P4 owners and Roadmap, not this historical observation.

The former CTC operational-evidence inventory is absorbed as dated capability limits: process contracts and domain/provider logs can answer bounded questions, but they do not prove an end-to-end process instance, retry/recovery causation, durable Telegram delivery, current Production retention or clock alignment. Any observation must use the recorded bounded, redacted, tenant-scoped sample protocol; instrumentation and retention changes remain separately authorized.

The former inbound-loader SOP's dated aggregate, Local rollback checks and unproven boundaries are now in docs/research/processes/2026-07-16/CTC_INBOUND_LOADER_EVIDENCE.md; the current workflow/registry retain process and recovery ownership.

Retained source set	Canonical current owner	P1 disposition and removal condition
APMT Truck Appointments input	docs/tasks/P4-001.md, Roadmap and API contracts	dated provider research absorbed into the owning Task; provider activation remains separate
Spare/Leftover design input	docs/tasks/P6-001.md, Bale Inventory Adjustment workflow, API contracts and DB schema	development input absorbed into the owning Task; current process/technical owners remain authoritative
transition-audit input	docs/tasks/P4-001.md, Roadmap and activated P4/P5/P6 owners	dated transition proposal absorbed into the owning Task
AI Voice plans and docs/requirements/CTC_AI_VOICE* sources	Roadmap, P6, current process/API owners	historical preliminary disposition only; superseded below by the P6-001 absorption and deletion record, while provider, DB, deployment and Field evidence remain separately unverified
Issue #1194 inventory-lot repair plan	DB schema, API contracts, Warehouse Grid workflow, Roadmap	dated repair proposal; retain until an activated owner accepts or retires it
docs/WAREHOUSE_MAP_PLANNING_KO.md, docs/WAREHOUSE_MAP_DEVELOPMENT_KO.md	docs/tasks/P6-001.md, DB schema, API contracts, Warehouse Grid workflow	ABSORB -> DELETE; each was a two-line consolidation pointer, repository caller-zero was verified, and the integrated source now names its current owners
docs/reference/modernization-v1/**	current Product/Design/technical owners; P5/P7/P8/P9	historical archive at its original path; retain until named later-Phase cleanup proves archive-specific consumer zero

This addendum does not mark P1 complete: final user review and acceptance of the resulting source-by-source cleanup remains required by P1-001.

2026-08-03 integration record: MK inbound purchase to inventory-lot UAT

The historical WP07-05 archive evidence was reclassified as dated Local/Production evidence and absorbed into The current MK inbound workflow, process registry, Admin2 runbook and historical P07 navigation now point to that owner. The archive source is removed after caller-zero verification; raw foundation inventory remains dated provenance only.

2026-08-03 integration record: MK order-to-packing composition

The historical WP03-12 composition analysis was absorbed into The canonical composite workflow and registry now cite that current evidence owner; the archive source is removed only after caller-zero verification.

2026-08-03 integration record: CTC inbound planning and Loader

WP03-06's dated reconstruction limits were merged into CTC_INBOUND_LOADER_EVIDENCE.md; the current workflow remains the sole process/recovery owner. Registry and P03 navigation now point to this canonical evidence owner.

2026-08-03 integration record: CTC labels, reports and adjustments

The WP03-11 source reconciliation was absorbed into The Warehouse Grid, daily/report and label-print registry owners now cite the canonical evidence; the user procedure remains the Local/Production Wiki page.

P1 manual and runbook integration addendum — 2026-08-03

2026-08-03 integration record: Appointment Email no-write trace

The historical WP07-02 browser trace was absorbed into The process contract, registry and P07 navigation now cite the canonical dated evidence owner; the former archive source is removed after caller-zero review.

2026-08-03 integration record: Yard/Driver no-write trace

The historical WP07-03 browser trace was absorbed into The Yard, Driver and handoff registry references and P07 navigation now cite the canonical dated evidence owner; the archive source is removed after caller-zero review.

2026-08-03 integration record: MK Booking/Packing preview baseline

The historical WP07-04 no-write trace and parity disposition were absorbed into The Packing registry and P07 navigation now cite the canonical dated evidence owner; the archive source is removed after caller-zero review.

2026-08-03 integration record: Appointment Local UATs

WP03B-01 and WP03B-02 were absorbed into and The appointment contract, registry and P03B navigation now cite the canonical dated evidence owners; both archive sources are removed after caller-zero review.

2026-08-03 integration record: Yard, Driver and handoff baseline

WP03-07 through WP03-09 were absorbed into The Yard, Driver, handoff and daily registry owners now cite this dated baseline while the canonical contracts and Local/Production Wiki procedures remain their current owners; the three archive sources are removed after caller-zero review.

2026-08-03 integration record: Billing, QBO and document baseline

WP03-10 was absorbed into The daily registry and P03 navigation now cite the dated baseline; current workflow and Local/Production Wiki owners remain unchanged, and the archive source is removed after caller-zero review.

2026-08-03 integration record: MK process reconstruction baseline

WP03-13 through WP03-16 were absorbed into The commercial, inbound/outbound, booking/allocation/export, Scale, Trade, cost and document registry owners now cite the dated baseline; their current workflow and Local/Production Wiki owners remain unchanged, and the four archive sources are removed after caller-zero review.

2026-08-03 integration record: MK inbound mutation and allocation evidence

WP08-19, WP08-20 and WP08-22 through WP08-29 were absorbed into The registry, P08 status table and Work Packet register retain their exact packet results and now cite this dated evidence; the ten archive sources are removed after caller-zero review.

2026-08-03 disposition: restricted MK legacy baselines

MK-legacy-system-and-process-baseline.md and MK-legacy-data-and-workbook-map.md are the canonical redacted provenance for the supplied legacy source, production-labelled SQL snapshot and workbook structure. Their static findings are cited by P02A, the commonization crosswalk and the MK commercial registry only as historical input; they do not own current Runtime, product, process, tenant or migration authority.

They remain only until a user-approved, redacted replacement evidence package can preserve the same source-safety, schema/workbook and legacy behavior facts. They must not be copied into current contracts as verified Runtime facts or used to authorize a legacy import, live access or write.

The following is an executed source-by-source disposition, not a relocation to research. User-facing procedure content was absorbed into T_WIKI_PAGE in both Local and Production and is presented at /operations-manual; the internal Wiki map only traces the owner and is not the manual content owner.

Removed source family	Absorption target and verification
OPERATIONS_MANUAL.md, CTC_OPERATION_MANUAL.md, MK_OPERATION_MANUAL.md, USER_MANUAL_INDEX.md	curated DB Wiki navigation/pages; both client source checks return sources=0
CTC operator manuals for appointment email, AR billing, billing close, driver delivery, inbound planning, yard dispatch, labels/reports and Spare/Bale tracking	corresponding CTC DB Wiki pages plus the named process workflow for technical state/recovery; current-owner caller-zero reviewed
CTC_OPERATION_SCREEN_SPEC.md, CTC_SCREEN_MANUAL.md, CTC_ROLLOUT_PARITY_CHECKLIST.md	DB Wiki screen guidance, docs/runbooks/CTC_FIELD_USER_PROCESS_SYSTEM_TEST_RUNBOOK.md and dated CTC evidence; former static screen/spec claims no longer own current behavior
CTC_SPARE_BALE_TRACKING_SOP.html, CTC_WAREHOUSE_REPORT_ADJUSTMENT_OPERATOR_MANUAL.html, AR_BILLING_QBO_SOP.html/.pdf	corresponding DB Wiki page plus Spare/Bale, Warehouse/Label or Billing process/evidence owner; repository consumer references migrated before deletion
MK_*_OPERATOR_MANUAL.md family	corresponding MK DB Wiki pages; Client 2 source check returns sources=0
MK_SCREEN_MANUAL.md, CTC_SCREEN_MANUAL.md	MK_CLIENT2_VALIDATED_SCREEN_REFERENCE.md and docs/runbooks/CTC_FIELD_USER_PROCESS_SYSTEM_TEST_RUNBOOK.md; current-owner caller-zero reviewed
GMAIL_APPOINTMENT_SOP.html/.pdf	appointment-email DB Wiki page in Local and Production plus APPOINTMENT_EMAIL_TO_SCHEDULED_WORKFLOW.md; page readback confirmed the Gmail guidance marker in both environments
HUB_OPERATING_MODEL.md	.agents/rules/PROJECT_OPERATIONS.md for shared repository policy and docs/runbooks/HUB_QA_OPERATIONS_RUNBOOK.md for hub-specific QA/SSH procedure; current-owner caller-zero reviewed
CTC_USER_PROCESS_SYSTEM_TEST_RUNBOOK.md	docs/runbooks/CTC_FIELD_USER_PROCESS_SYSTEM_TEST_RUNBOOK.md; every process-registry, Wiki-map and static source metadata caller migrated in this change
PRODUCTION_ENVIRONMENT.md, QUICKBOOKS_TIME_PRODUCTION_SETUP.md	docs/runbooks/PRODUCTION_ENVIRONMENT_RUNBOOK.md and docs/runbooks/QUICKBOOKS_TIME_PRODUCTION_SETUP_RUNBOOK.md; API catalog and P4 current callers migrated in this change
root MK test checklist, report, field-demo worksheet and validated-screen reference	docs/runbooks/MK_ADMIN2_FUNCTIONAL_TEST_RUNBOOK.md for repeatable procedure and dated docs/research/mk/<date>/ records for observations; P2, process registry and relative-document callers migrated in this change
WAREHOUSE_MAP_SYSTEM_KO.md, task-904-api-performance-plan.md	docs/tasks/P6-001.md as dated design input and docs/performance/TASK_904_API_PERFORMANCE_BASELINE.md as dated P9 baseline; process registry and P1 current callers migrated in this change
dated docs/current-state/** and docs/analysis/** inputs	dated docs/research/current-state/<date>/ and docs/research/runtime/ records; process registry current caller migrated, while historical evidence keeps its original source-path text as provenance
CTC_AI_Voice_Field_Information_Required.md	field-routing, transfer, UAT and default response absorbed into docs/tasks/P6-001.md as explicitly historical/unverified input; current caller-zero reviewed
AI Voice Load Lifecycle Walkthrough, Planner Integration Principles and Field User Button Guide	valid selected-Load route, existing action, Loader, Completed, Spare and Yard Closing draft guidance absorbed into docs/tasks/P6-001.md; Wiki manual asset and current caller-zero reviewed
CTC_AI_VOICE_READINESS_AND_GAP_ANALYSIS.md	dated source/gap findings absorbed into docs/tasks/P6-001.md with capture-date limitation; current caller-zero reviewed
CTC_AI_VOICE_DEVELOPER_REQUEST_GUIDE.md	developer evidence checklist and fixed technical constraints absorbed into docs/tasks/P6-001.md; current caller-zero reviewed
CTC_AI_VOICE_FIELD_REQUEST_GUIDE.md	pilot field/IT decision and secure-information checklist absorbed into docs/tasks/P6-001.md; current caller-zero reviewed
2026-07-18 v2 and 2026-07-21 v3 AI Voice requirement/design revisions	shared valid constraints and explicit Scale Out conflict disposition absorbed into docs/tasks/P6-001.md; the obsolete requirement sources were deleted after current caller-zero
ctc-ai-voice-mockup-first-plan.md	mockup/manual approval gate and preserved card-level UI boundary absorbed into docs/tasks/P6-001.md; superseded Scale Out mockup explicitly retained as a dated conflict note
modernization archive 01–07, 10, 14–17, 20–35, 57–67 source families	valid dated findings absorbed into the named current process, P03/P07/P08 navigation and scoped research/reference/performance baselines above; current registry/status/navigation callers migrated or proven zero before source deletion

The removed sources remain recoverable from Git history. Browser, field and provider operation were not run by this documentation integration; DB Wiki readback was limited to the changed page records.

P1-001 C1/C2 integrated disposition addendum — 2026-08-05

Interpretation correction

The earlier P1-001 = completed ... final disposition and cleanup wording and Final source-by-source cleanup — 2026-07-31 section are bounded historical results only. They were superseded by the user-directed 2026-08-03 reopen. They do not establish current completion, final deletion authority or current environment proof. Live P1/P1-001 status remains owned only by docs/ROADMAP.md and remains IN PROGRESS — REOPENED.

The Cloud handoff is a non-authoritative review input. This addendum records actual Cloud findings in the preliminary disposition; it does not authorize a merge, deletion, Wiki publication, Runtime/DB/Production write or status change.

Candidate identity and applicability

Item	Observed result	Disposition meaning
Current review base	qa@7d1c781e69df1f31f94bbc6222b6ba1c48664e41	current remote authority snapshot used for this review
Remote P1 candidate	codex/p1@1dd7b6d858557a76319e5cf03683f49106a631bb	independent remote candidate snapshot only
Merge base	2fd250b0bb0d5995ae1481aed45188e8e70f6821	candidate and current qa diverged after this commit
Candidate relation	candidate is 1 commit ahead and 17 commits behind current qa	direct merge/application is not an accepted integration path
Reported Local staged set	424 paths, as stated in the handoff	exact manifest, patch and staged bytes were not supplied to Cloud
Candidate equivalence	NOT PROVEN	codex/p1 must not be treated as the Local staged tree without an exact manifest/SHA comparison

Source-family disposition

Source or family	Re-reviewed action	Current disposition and required preservation/deletion gate
docs/PRODUCT.md, docs/DESIGN.md, docs/DEVELOPMENT.md	REWRITE metadata; ABSORB only unique owner content	both current qa and the remote candidate retain LOCAL UNCOMMITTED status text. Final P1 writer must first reconcile the exact candidate, then change only the stale status metadata to current owner wording. These files are never deletion candidates.
docs/ROADMAP.md, docs/tasks/P1-001.md	KEEP; Task REWRITE historical/current interpretation	Roadmap remains the sole live status owner and is not changed by this review. Earlier Task PASS/cleanup prose is historical evidence only; current C1/C2 result and remaining gates belong in the integrated Task ledger.
docs/OPERATIONS_MANUAL.md, docs/USER_MANUAL_INDEX.md, CTC/MK operator manuals, SOP HTML/PDF and Wiki assets	MOVE_WITH_CONSUMER / ABSORB / KEEP	the candidate contains broad manual deletion and Wiki/asset relocation. Source shows a DB-backed Wiki boundary and source-check tooling, but Cloud did not verify Local/Production T_WIKI_PAGE rows, tenant/role/browser behavior, asset integrity, external PDF/bookmark consumers or old-path caller-zero. No deletion is authorized.
docs/wiki/**, frontend/pages/platform/help/operations-manual*.php, scripts/verify_operations_manual_sources.php	KEEP / REWRITE with the same consumer change	repository Wiki files own internal mapping/assets; tenant-scoped T_WIKI_PAGE owns saved user Markdown. Candidate source alignment is useful, but DB readback and executable verification remain NOT_RUN.
docs/processes/**, docs/processes/process-registry.yaml	KEEP / REWRITE references	workflows and registry remain current process owners. Candidate relocation of supporting evidence/manual references must be re-created on current qa, then checked against every registry document, process ID, manual source and executable consumer before an old path is removed.
docs/plans/CTC_SPARE_BALE_TRACKING_PLAN.md, docs/requirements/CTC_SPARE_BALE_TRACKING_DEVELOPMENT.md	ABSORB / REWRITE / KEEP_RESEARCH	process semantics route to the Bale Inventory Adjustment workflow; technical facts route to current source/API/DB owners; activation/progress routes to Roadmap and the owning Task; dated design/progress evidence remains research. Current-build language cannot own live status. Keep both sources until unique content and consumers are proven absorbed.
docs/plans/APMT_TRUCK_APPOINTMENTS_INTEGRATION_PLAN.md	KEEP_RESEARCH / ABSORB / REWRITE	preserve the provider contract, credential boundary, rollout/rollback and UAT blockers. Route only verified target/current facts to the exact activated Task and API/integration owners. The candidate's broad P4 routing is not sufficient deletion evidence.
docs/plans/WP01-09-additive-transition-audit-store.md	KEEP accepted decision/research input; ABSORB exact current facts	preserve accepted ADR rationale, schema/migration contract and rollback boundary. DB/Production application remains unverified; implementation-progress text is historical unless Roadmap activates the owner.
docs/requirements/CTC_AI_VOICE*, AI Voice plan/manual assets	REWRITE / ABSORB / KEEP_RESEARCH	split the earlier absent-module gap observation from later source-level implementation claims. Product boundary, target design, current source/API facts, process semantics, operator procedure and dated evidence require separate owners. Provider, DB, deployment and field activation were not verified; no family deletion is authorized.
docs/performance/**, performance evidence and candidate docs/tasks/P9-001.md absorption	ABSORB / KEEP_RESEARCH; later DELETE only after verification	the candidate P9 Task contains substantial performance plan/status content, showing a plausible absorption target. Preserve measurement provenance, rollback seams and residual field gaps. Rebase/re-create the absorption on current qa, verify links/callers and retain evidence before deleting plan/status sources.
docs/reference/modernization-v1/**, current-state, research and evidence families	KEEP_RESEARCH / ABSORB / source-by-source DELETE	sampled historical owners such as ACTIVE.md correctly narrow current authority. Broad candidate moves/deletions still require an exact path manifest, unique-content comparison, retained-reference repair and executable/current-navigation/external consumer review.
docs/runbooks/**, API catalogue paths, agent routers, templates and verification scripts	KEEP / REWRITE / MOVE_WITH_CONSUMER	candidate path updates demonstrate known coordinated consumers, not complete caller-zero. Re-create against current qa; run focused link, PHP/script and consumer checks before removing any old path.

Not authorized by this addendum

• merging or force-applying codex/p1 to qa;
• treating the remote candidate as the reported Local 424-path staged tree;
• deleting any manual, plan, requirement, research, evidence, runbook or asset solely because the candidate removes it;
• changing Product/Design/Development metadata before exact candidate reconciliation;
• changing docs/ROADMAP.md status or declaring P1/P1-001 complete;
• claiming Wiki-row, Runtime, DB, provider, browser, Field, Production or deployment verification.

Remaining final-disposition gates

1. obtain the exact Local staged base SHA, staged manifest and binary-safe patch, or explicitly prove exact equivalence to a current remote candidate;
2. reconcile every staged path count one-for-one with one primary action, target owner, preservation reason, consumer set and deletion evidence;
3. rebase or re-create accepted candidate changes on current qa without overwriting the 17 intervening commits;
4. correct canonical owner metadata and narrow Roadmap-external current/progress language only after source ownership is resolved;
5. run focused link, manual-source, PHP/script, registry, asset and caller-zero checks on the exact final tree;
6. perform any required Local/DB/browser/role/tenant/Production readback under separate authorization;
7. obtain user review of the actual integrated tree and deletion result.

Until these gates pass, every unverified removal remains BLOCKED and this file remains a preliminary research input rather than final cleanup authority.

Post-merge candidate reconciliation — 2026-08-05

The preceding Cloud candidate identity is a historical review snapshot. The current Local P1 integration base is codex/p1@132664cad8f73573381a518ba3bce8af42e13df9, which contains origin/qa@46cc4f923700bc3924c16c0f94b2643559d8868e as its integrated QA parent. Its exact diff from that QA parent has 426 paths (19 added, 57 modified, 93 deleted and 257 renamed). The candidate is 0 behind and 2 ahead of origin/qa. The metadata and ledger corrections recorded in this worktree are a subsequent uncommitted local set.

This corrects the former candidate-equivalence and divergence limitation only. It does not convert the Cloud source-family review into final deletion evidence: the 93 deleted paths still require their individual absorption, current/external consumer and caller-zero record before P1 completion review.

---

Source: docs/research/recovered-documents/2026-07-30/preliminary-document-recovery-disposition.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged.