Skip to content

Recovered Documents — 2026-07-30

  • Status: RECOVERY RESEARCH RECORD / FINAL P1-001 DISPOSITION
  • Deletion reviewed: cc25434eaa0dfec09eaf22e1579f2fb00870b4e9
  • Snapshot source: parent tree fcf769199b698c53fa91371f1a51a29207dcc068
  • Owning re-review: P1-001; live Task status is owned only by the Roadmap
  • Preliminary disposition: preliminary-document-recovery-disposition.md
  • Retention/removal: retain this compact record and the exact original disposition while they provide unique source-by-source reasoning. Git history preserves removed source bytes.

Purpose

The deletion commit removed useful product, design, development, operational, decision, evidence and research material together with Roadmap, Task, Request, generated-index and fixed-Harness systems that the user rejected.

A preliminary recovery pass reviewed all changed paths and restored several bounded owners. That pass used an earlier numeric label that is no longer a Task ID. Its exact source bytes remain recoverable from the named Git trees; the original source-by-source disposition remains under raw/.

The preliminary result was not the final document-hierarchy decision. P1-001 defined the canonical hierarchy, roles, naming and templates, then re-evaluated every material recovery decision before final cleanup.

Git preservation and retained exact decision record

Duplicate raw source copies and the superseded execution wrapper were removed after final absorption review. Their internal Task number and completion wording remain historical in Git and the retained disposition.

Active original-path inputs and utilities

The following bounded owners/utilities are currently restored or retained at their original paths, subject to re-review in P1-001:

Path Current role
.agents/rules/PROJECT_OPERATIONS.md repository/Git/external-write/promotion boundary
.agents/rules/CONTROL_TOWER.md CTC-side Control Tower boundary and later cross-repository input
.agents/skills/ctc-field-process-testing/SKILL.md explicit opt-in field/process testing route
docs/control-tower/README.md routes Control Tower implementation detail to the sibling repository
docs/runbooks/RELEASE_GATE_RUNBOOK.md explicit-authority release handoff
scripts/verify_operations_manual_sources.php bounded read-only verifier for the in-app Operations Manual consumer

AGENTS.md, README.md, docs/ROADMAP.md, the durable Context and the Roadmap-activated Task are current entry/planning sources. This research snapshot owns no live Task state.

Research-only snapshots

The snapshot includes prior Product, Design, Development, Benchmark, Roadmap, Request, Task, documentation-governance, skill-routing, field-testing, decision, migration and release material. These are conflict-analysis and absorption inputs only.

Current target owners are:

The former Product Charter and System Design content was absorbed into the canonical owners and the old paths were removed after repository caller-zero.

Systems that remain inactive

The recovery does not reactivate:

  • docs/evolution/** program/status/register/generated surfaces;
  • former CTC-DOCS-R2 plan collection;
  • obsolete docs/modernization/** pointers;
  • docs/catalog.json, generated docs indexes or exact-text validators;
  • .agents/harness/** and scripts/harness/**;
  • scripts/docs/**;
  • repository-wide scripts/verify-change.sh or automatic release-gate orchestration.

Runtime-consumer boundary

Operations Manual, process, API-catalog and other proven consumer-bound documents are not passive files. Their original paths remain until consumers are migrated in the same change, source signatures/metadata are updated where required, output is verified and caller-zero is proven for the old path.

P1-001 use record

P1-001 used the exact snapshots and preliminary disposition to:

  1. define and approve the final hierarchy;
  2. construct canonical current owners;
  3. integrate valid content;
  4. verify human/AI/navigation and actual consumers;
  5. issue final KEEP/ABSORB/REWRITE/MOVE_WITH_CONSUMER/KEEP_RESEARCH/DELETE decisions;
  6. remove obsolete material only after the new structure works.

---

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