Phase 0.9 project docs — register with status tags
Phase 0.9 project docs — register with status tags
Section titled “Phase 0.9 project docs — register with status tags”Last updated: S238 (2026-05-14). Predecessor: Flat list pre-S238 (groups intact, no tags). Maintained by: Phase 0.9 owner (Liam) + main-session synthesis pass.
How to use this document
Section titled “How to use this document”This register is the index of every Phase 0.9-related document — 0.9-* canonical docs, spike outputs, synthesis snapshots, third-party evaluations, client briefs, and platform reference docs. Each entry now carries a status tag so a reader entering the register cold can tell at a glance which doc is the live source of truth and which is historical context.
Status tags:
| Tag | Meaning |
|---|---|
[CURRENT-CANONICAL] | Active source of truth. Cite this doc for the named topic. |
[ACTIVE-LIVING-DOC] | Still being edited; expect frequent updates across sessions. |
[HISTORICAL-CONTEXT] | Captures past decision-state; useful for audit-trail but superseded for direct use by a later doc. |
[SUPERSEDED-BY-X] | Explicitly replaced by named successor X. Read only for archaeology. |
[OUTDATED — SLATED FOR SPLIT] | Central frame at variance with current ratifications; being split into smaller current-state sub-docs (S238+). |
[DEPRECATED] | Should not be consulted as source of truth; preserved for historical reference only. |
Reading order if starting cold:
00-synthesis-v2.md(10-feedback-investigation-findings/) for the post-S237 central state.0.9-synthesis.md(this doc’s anchor) for spike-phase outcomes + §8 prerequisite chain + §8.6 post-S236 status table.0.9-decision-graph.md§11 for S234+S235+S236+S237 ratifications.0.9-collapse-candidates.md§12-§14 for ratified retires + DEFERRED-v1.1 + DO-NOT-BUILD items.INV-architecture-split-readiness.md(underdocs/specs/core-docs-pathway-assessment/) for the WP4 9-sub-doc split wave plan.
Do NOT enter Phase 0.9 via 0.9-intended-architecture.md — it is OUTDATED and slated for split into 9 sub-docs (S238+). See note on its entry below.
Core project documents (Phase 0.9 canonical set)
Section titled “Core project documents (Phase 0.9 canonical set)”0.9-context—[CURRENT-CANONICAL]— investigation framing + scope.0.9-decision-graph—[CURRENT-CANONICAL]— §11 carries S234+S235+S236+S237 ratifications consolidated. Living register.0.9-intended-architecture—[OUTDATED — SLATED FOR SPLIT]— 2015-line monolith (10/05/2026, S229-stamped) predating every S233-S237 ratification. Liam preserves as snapshot pre-split. Being decomposed into 9 sub-docs underdocs/plans/phase-0-investigation/architecture/01-vision.md…09-diagrams.md. Wave plan inINV-architecture-split-readiness.md§6. To be archived to.planning/.archive/.specs/after Wave 4 closes.0.9-collapse-candidates—[CURRENT-CANONICAL]— §12-§14 carry ratified retires (S235 refresh + S237 CV-driven additions —capabilityCV 04,firecrawl/trafilatura/pdfplumberCV 16, lockstep retire patterns).
Current core project functionality-related documents
Section titled “Current core project functionality-related documents”0.9-edit-flow-investigation—[CURRENT-CANONICAL]— §6 per-UC Candidate A/B/C set cited by0.9-canonical-pipeline/PRODUCT.mdP-11 Q2.9 ratification.0.9-spike-S10-dedup-substrate—[CURRENT-CANONICAL]— S230 HYBRID resolution (cocoindex + skill-seekers intersection 91.7%/1.5-4.5%). UC8 v1.0.9-spike-S3-mempalace-observe—[CURRENT-CANONICAL]— Shape A+B+C+miner CONFIRMED; three-column extension (provenance + confidence + adapter_name).0.9-spike-S16-qa-schema-design—[CURRENT-CANONICAL]— two-tierq_a_pairs+q_a_extractionsmodel. Notes: S16-verification + OQ responses fold into0.9-synthesis.md§1 finding 5 and Q-OQR1-06 ratification.
Central post-S237 synthesis (NEW canonical layer)
Section titled “Central post-S237 synthesis (NEW canonical layer)”10-feedback-investigation-findings/00-synthesis-v2.md—[CURRENT-CANONICAL]— §3 new items + §4 WP4 readiness map + §5 still-open register. Most-current entry-point for any S238+ work.10-feedback-investigation-findings/feedback-findings-review.md—[CURRENT-CANONICAL]— §5 post-prereq disposition register + §6 S237 closures.
Synthesis & related feedback (Historical context)
Section titled “Synthesis & related feedback (Historical context)”09-synthesis-and-verification-feedback—[HISTORICAL-CONTEXT]— S231 Liam feedback. Cited from00-synthesis-v2.md§4 row 6 (06-mcp-tooling source).0.9-synthesis—[ACTIVE-LIVING-DOC]— this doc’s anchor synthesis. S230 origin, S231 refresh, S238 §8.6 annotation. Will continue receiving forward-looking refresh passes through Phase B close.wave-08-feedback—[HISTORICAL-CONTEXT]0.8-synthesis—[HISTORICAL-CONTEXT]07-synthesis-feedback—[HISTORICAL-CONTEXT]0.7-synthesis—[HISTORICAL-CONTEXT]0.6-synthesis—[HISTORICAL-CONTEXT]
Core third-party evaluation documents (Historical context — point-in-time)
Section titled “Core third-party evaluation documents (Historical context — point-in-time)”0.8.2-cocoindex-evaluation—[HISTORICAL-CONTEXT]— §5.4 + lines 38/46/51/142-143/227 carry correction notes per0.9-synthesis.md§9.1 (Scenario A confirmed in S1; API drift cross-ref0.9-spike-S2 §3+0.9-spike-S1 §1).0.8.4-pullmd-evaluation—[HISTORICAL-CONTEXT]0.8.5-skill-seekers-evaluation—[HISTORICAL-CONTEXT]— §Q5 carries correction per0.9-synthesis.md§9.2 (dep_analyzer.py0% non-overlapping TP — SKIP).0.8.7-mempalace-evaluation—[HISTORICAL-CONTEXT]— §5.6 / §8.4 carries stale-marker per0.9-synthesis.md§9.3 (mempalace_searchFIXED in v3.3.5 per PR #1396; CLAUDE.md “Memory (Mempalace)” section reflects current state).trpc-evaluation-feedback—[HISTORICAL-CONTEXT]
Core investigation documents pre-third-party tooling pivot (Historical context)
Section titled “Core investigation documents pre-third-party tooling pivot (Historical context)”0.7.2-python-paths-obsolescence—[HISTORICAL-CONTEXT]0.7.4-source-documents-history-relationship—[HISTORICAL-CONTEXT]— superseded by B2 RESOLVED-α + §3.15source_documents.workspace_idnullable (00-synthesis-v2.md§3.15).0.7.3-p6-p8-absorption—[HISTORICAL-CONTEXT]0.7.1-path-normalisation-feasibility—[HISTORICAL-CONTEXT]0.5-ep2-spec-impact—[HISTORICAL-CONTEXT]0.2b-side-tables-audit—[HISTORICAL-CONTEXT]0.2a-content-items-column-audit—[HISTORICAL-CONTEXT]0.1-mcp-create-content-item—[HISTORICAL-CONTEXT]0.1-rss-intelligence-pipeline—[HISTORICAL-CONTEXT]
Initial Project Kick-off documents (very outdated)
Section titled “Initial Project Kick-off documents (very outdated)”content-items-cleanup-phase-0-investigation—[DEPRECATED]— superseded by entire Phase 0.9 investigation arc.content-items-cleanup-plan—[DEPRECATED]— superseded by0.9-intended-architecture(and its forthcoming split) + the Q-OQR1-16 combined-PR scope.
Core Platform Reference Docs (mixed)
Section titled “Core Platform Reference Docs (mixed)”Knowledge Hub — Platform Overview.md(client-facing,docs/client-documentation-base/markdown/) —[CURRENT-CANONICAL]— Liam-cited input for WP401-vision.md.Knowledge Hub — Claude Integration Guide.md(client-facing,docs/client-documentation-base/markdown/) —[CURRENT-CANONICAL]— Liam-cited input for WP401-vision.md.docs/reference/product-differentiation-audit.md—[CURRENT-CANONICAL]docs/reference/ux-principles.md—[CURRENT-CANONICAL]docs/reference/ai-visibility-policy.md—[CURRENT-CANONICAL]— cited in CLAUDE.md “AI is invisible infrastructure” principle.docs/reference/ai-integration-strategy.md—[CURRENT-CANONICAL]docs/reference/ai-integration-layers.md—[CURRENT-CANONICAL]docs/reference/client-personas.md—[CURRENT-CANONICAL]docs/reference/classification-architecture.md—[CURRENT-CANONICAL]docs/reference/entity-type-taxonomy-spec.md—[CURRENT-CANONICAL]— cited in CLAUDE.md “Entity classification” gotcha as source of truth.docs/reference/field-consumer-dependency-map.md—[CURRENT-CANONICAL]docs/product-functionality/directory —[CURRENT-CANONICAL]— feature-level functional docs.
Original Requirements and Subsequent Client Feedback Docs
Section titled “Original Requirements and Subsequent Client Feedback Docs”Product_KB_Dev_Brief.md—[HISTORICAL-CONTEXT]— initial client brief.Sector-Intelligence-Brief-Liam-Final.md—[HISTORICAL-CONTEXT]— initial SI brief.sector-intelligence-analysis.md—[HISTORICAL-CONTEXT]— initial KH-vs-SI-brief gap analysis.kb-hub-gap-analysis-liam—[HISTORICAL-CONTEXT]kb-hub-gap-analysis-response-s188—[HISTORICAL-CONTEXT]docs/client-documentation/kb-hub-gap-analysis-action-tracker.md—[ACTIVE-LIVING-DOC]— gap-analysis action tracker; receives entries through Phase 2 commencement.docs/plans/phase-0-investigation/kh-client-feedback.md—[ACTIVE-LIVING-DOC]— client feedback log; receives entries through Phase 2 close.
WP6 + WP8 + WP4 follow-on artefacts (S236+)
Section titled “WP6 + WP8 + WP4 follow-on artefacts (S236+)”docs/ontology/*.md(29 CV files + README) —[CURRENT-CANONICAL]— WP6 markdown ontology scaffold. LANDED-S236-S237 (Waves A→C+E1 + D1 implementer + E2 ratifier).docs/specs/wp6-ontology-harness/TECH.md—[CURRENT-CANONICAL]— WP6 D1 implementer spec.docs/specs/wp6-ontology-harness/verifier-reports/(B1 / B2 / E1 / E2) —[CURRENT-CANONICAL]— Wave verifier outputs.docs/specs/id-31-0.9-canonical-pipeline/PRODUCT.md—[ACTIVE-LIVING-DOC]— plan-skeleton; S238 WP1 flips PROVISIONAL → RATIFIED-S2XX with citations + adds §13 v1 scope + §14 v1.1 scope.docs/specs/id-31-0.9-canonical-pipeline/TECH.md—[ACTIVE-LIVING-DOC]— same S238 WP1 pass.docs/specs/core-docs-pathway-assessment/INV-architecture-split-readiness.md—[CURRENT-CANONICAL]— S237 sub-agent output; §6 carries the WP4 9-sub-doc wave plan. Cited from forthcomingarchitecture/01-vision.mdper its own §7.1 mitigation. To be archived to.planning/.archive/.audits/after Wave 4 closes.docs/plans/phase-0-investigation/architecture/directory —[ACTIVE-LIVING-DOC]— WP4 9-sub-doc split target; pilot01-vision.mdlands S238.