Skip to content
Canonical

Canonical Pipeline — Pre-Phase References (Historical Context)

Canonical Pipeline — Pre-Phase References (Historical Context)

Section titled “Canonical Pipeline — Pre-Phase References (Historical Context)”

Status: Historical-context artefact (read-only) Authored: S67 W1a (22/05/2026) per Subtask ID-31.7 Companion to: PLAN.md §1 Decomposition methodology

Context

Section titled “Context”

This document satisfies the P-OQ-4 A2 EXPANDED ratification (S67 W1a planning): T0 is not a distinct Task in the canonical-pipeline implementation ledger. The canonical-pipeline umbrella in ledgers/umbrellas.json (retired JSON ledger — superseded by the ordna task files) points its substrate_doc field at the adjacent PLAN.md. That single substrate cannot, however, encode the full pre-phase research lineage that informed the spec pair and decomposition. This file is the historical-context index that closes that gap — it enumerates the four canonical reference sources mined during the S199–S241 research arc, so a future reader (Curator, Checker, or fresh Planner) can retrace the chain without re-mining the substrate from scratch. PLAN.md itself stays untouched (per the PRODUCT non-goal at docs/specs/id-31-canonical-pipeline-task-list-migration/PRODUCT.md line 73-74: substrate stays read-only here).

References

Section titled “References”

1. Mempalace memory wing — knowledge-hub

Section titled “1. Mempalace memory wing — knowledge-hub”

Long-form research, session diary blocks, and ratification memos from the canonical-pipeline planning arc are indexed in the mempalace knowledge-hub wing. Verified via mempalace_list_wings at author time: 75 878 drawers under that wing as of 22/05/2026 (alongside the focused knowledge-hub-prod-readiness wing at 22 773 drawers and the knowledge-hub-content-architecture wing at 1 046 drawers). Use mempalace_search (default wing, then filter results client-side by wing — per CLAUDE.md mempalace gotcha) to retrieve drawers by topic.

2. Cocoindex-code substrate — docs/specs/id-31-0.9-canonical-pipeline/

Section titled “2. Cocoindex-code substrate — docs/specs/id-31-0.9-canonical-pipeline/”

The original Phase 0.9 canonical-pipeline spec pair (pre-S241):

Treated as historical substrate per S241 direction (referenced in PLAN.md header). The architecture sub-docs cited at PLAN.md header (02 / 04 / 05 / 06 / 08) live under docs/themes/canonical-pipeline/intended-architecture/, not inside the 0.9-canonical-pipeline directory:

3. GitNexus index — knowledge-hub repo

Section titled “3. GitNexus index — knowledge-hub repo”

Code-intelligence graph indexed by GitNexus (canonical instance at /Users/liamj/.gitnexus/repos/knowledge-hub, last indexed 12/05/2026 at commit 186a05bc). Stats: 40 988 nodes, 58 754 edges, 593 communities, 300 execution flows across 1 806 files. Used at planning time for impact analysis (gitnexus_impact), execution-flow tracing (gitnexus_query), and symbol context (gitnexus_context). See the local .gitnexus/CLAUDE.md for the discovery-and-safety workflow.

4. Original Phase 0.9 documentation

Section titled “4. Original Phase 0.9 documentation”

The S199–S241 research arc that fed PLAN.md decomposition is preserved in:

Section titled “Forward-link”

Continue at PLAN.md §1 Decomposition methodology for the active implementation plan.