Rewrite roadmap: unified 5-pillar semantic engineering vision

[Alan-Jowett]

Summary

Rewrites the roadmap from a flat feature list into a structured, dependency-aware plan organized around five capability pillars — each addressing a distinct class of engineering risk.

Structure

Pillar	Threat Model	Status
1. Specification Integrity	Correctness drift between specs, code, and tests	Phase 1 ✅, Phase 2 partial ✅, Phase 3 planned
2. Software Archaeology	Legacy risk — hidden invariants, undocumented behavior	Partially shipped (\
everse-engineer-requirements)
3. Protocol & Standards	Protocol risk — RFC drift, interop failures, breaking changes	Planned
4. Security & Emergent Behavior	Security risk — undocumented capabilities, bypass paths	Planned
5. Continuous Semantic Integration	Evolution risk — gradual drift across all artifacts	Vision

What changed vs. the previous roadmap

• Restructured from flat sections into pillars with explicit threat models and dependencies
• Integrated 18 work items from the design brainstorming session (software archaeology, protocol analysis, security, CSI, living specs)
• Added dependency map showing how pillars build on each other
• Added new sections: Formats, Taxonomies, and expanded Protocols/Personas
• Preserved all existing content (distribution, extensions, templates, testing, community)
• Updated shipped status to reflect PRs Add traceability audit template for cross-document specification drift #35 and Add code compliance audit template (spec+design → code) #42

Dependency Map

\
Phase 1: Cross-Doc Audits ✅
Phase 2: Code ↔ Spec Audits ✅ (code) / planned (test)
│
├── Phase 3: Invariant Extraction
│ ├── Pillar 3: Protocol & Standards
│ └── Pillar 5: CSI & Living Specs
│
├── Pillar 2: Software Archaeology
└── Pillar 4: Security & Emergent Behavior
\\

[Copilot]

Pull request overview

Rewrites docs/roadmap.md into a structured, dependency-aware roadmap organized around five “pillar” capability areas (spec integrity, archaeology, standards, security, and continuous semantic integration) to better communicate long-term direction and sequencing.

Changes:

• Reorganized the roadmap from a flat list into five pillars with explicit threat models and dependency relationships.
• Updated/expanded roadmap content for audits, RFC/standards work, security/emergent behavior, and CSI automation, including a new dependency map.
• Refreshed distribution/packaging and extension sections to align with the current positioning.