Cortex Roadmap

The roadmap keeps current work discoverable. It is not a permanent dump for issue snapshots, transition notes, or migration-era planning notes.

Tracks

• Plans/ - focused implementation or research plans.
• Epics/ - long-running initiatives when an active epic exists.
• Completed/ - shipped initiatives retained because they still explain current architecture.
• Archive/ - superseded proposals retained selectively.

Active Epics

• Substrate Soundness Closure — prove the novel Wire/Pulse middle is mechanically sound end-to-end, before investing in parser/compiler/IO correspondence.

Current Plans

• Lean mechanization - machine-checked support for the fixed-topology core.
• Rewrite materialization and recovery - runtime-grounded rewrite and recovery semantics.

Retention Rule

When a plan stops explaining current work, remove it or replace it with a short current plan. Do not preserve stale issue-era plans merely because they once existed.

Templates

Use the roadmap-epic template or implementation-plan template for new roadmap docs.