The Phase 3 roadmap rated multi-namespace registry (TASKSET 20) as “High risk — fundamental schema change.” In reality, choco:// support was already built into the schema’s IMPORT_URI_PATTERN, bridge resolvers (IC-02) were tested, and cross-scheme DAG building worked. The “namespace registry” became a thin config layer (16 tests, 120 lines) instead of a schema rewrite.
Key learning: Before rating a taskset as high risk, audit what infrastructure already exists. The IC-02 bridge resolver work from TASKSET 6 had already solved the hard problem. TASKSET 20 just needed a config file and a validation function. Pattern: when you think you need a “fundamental change,” first check if you already built the foundation while solving an adjacent problem.
Applicable pattern: Design foundational abstractions (like BridgeResolver interface) even when you only have one implementation. The abstraction costs minutes; the reuse saves weeks when the second implementation arrives.
