Skip to content

Platform Foundation Research — 2026-07-30

  • Status: RESEARCH INPUT / NOT A TASK REGISTRY
  • Source snapshot: tree immediately before deletion commit cc25434eaa0dfec09eaf22e1579f2fb00870b4e9
  • Current use: preserved research/provenance input for P1-001 through P1-004 and their downstream owners
  • Numbering rule: these collections do not occupy Task numbers.
  • Retention/removal: retain unique foundation evidence and decision provenance; remove a wrapper only after canonical-owner absorption and downstream consumer review, while raw Git provenance remains preserved

Important interpretation

The five records were originally produced with Task-shaped numeric metadata. That wrapper is invalidated. The investigation itself is preserved in full.

Historical numeric label, status, completion, dependency and unlock
= NOT CURRENT

Detailed investigation, source references, observations, unknowns,
limitations, comparison matrices and proposed follow-up questions
= PRESERVED RESEARCH INPUT

The current filenames are descriptive. Files under raw/ still point to the exact original Git blobs, so their internal historical headings and wording remain unchanged.

Research records

Research topic Current classification Descriptive path Original source path Original blob
Document inventory and authority analysis RESEARCH-INPUT raw/document-inventory-and-authority-analysis.md docs/tasks/P1-001.md c8b1998b492b779206d410cef8c71c4a5055468c
Competitor benchmark and CTC product gap RESEARCH-INPUT raw/competitor-benchmark-and-product-gap.md docs/tasks/P1-002.md 6e485f88577ce96b56b4c2f2d47cc5264fe4bb37
Repository, filesystem and Runtime consumers RESEARCH-INPUT raw/repository-filesystem-and-runtime-consumers.md docs/tasks/P1-003.md 972e671a4652ee59502e9ae7b5de688b124f68b6
Harness and automated-verification reality check RESEARCH-INPUT raw/harness-and-verification-reality-check.md docs/tasks/P1-004.md 751b81ecfeb55639354565008063da230a2abda8
Request, Control Tower, Orca and Codex baseline RESEARCH-INPUT raw/request-control-tower-orca-codex-baseline.md docs/tasks/P1-005.md 6f5b577d22cfddec116e04c0979ada39809ba474
Full competitor benchmark output RESEARCH-INPUT raw/benchmark/CTC-COMPETITOR-BENCHMARK.md docs/BENCHMARK.md 81cb4e41a3c0e6b5916cf8535b42f75fd5b1a012

The original source paths are provenance only. They do not reserve or consume current Task IDs.

P1 artifact routing and dated decision provenance

The hierarchy approval record is canonical-document-hierarchy-draft.md. The user approved D2=B; D1,D3-D12=A on 2026-07-30. This is dated decision provenance; live Task and Git status remain outside this research index.

The P1 artifacts are routed below without copying live Roadmap state:

Preserved document-inventory artifacts

Artifact Current path Original blob
full CSV disposition dataset raw/evidence/document-inventory/document-inventory.csv 6b7bd4fb108c93172e7fab4156bc89fe4647a505
full JSON disposition dataset raw/evidence/document-inventory/document-inventory.json cab32d0b197c46bfa320087bed794293378016bf
Local reconciliation raw/evidence/document-inventory/local-reconciliation.md ac74cda663830f8702b92d6af556e51007224529

The supporting CTC-DOCS-R1 inventory, link graph, consumer map, UAT answers and validation report remain under raw/evidence/CTC-DOCS-R1/ because the document research relied on their complete contents.

How P1-001 used this material

  1. Read each detailed record, not only a summary.
  2. Separated observed fact, proposal and historical wrapper metadata.
  3. Revalidated only facts whose freshness mattered.
  4. Used findings to define the canonical document hierarchy and integration scope.
  5. Re-reviewed the preliminary recovery disposition after hierarchy approval.
  6. Kept every internal historical COMPLETE, IN PROGRESS, numeric label or Unlocks text outside current authority.

---

Source: docs/research/platform-foundation/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.