tegwick
9e8d73fa7d
All three stages of the infospace tooling roadmap are complete. The Wealth of Nations / VSM example passes 6/6 viability thresholds on 988 entities, and composition is demonstrated via the supply-chain-vsm example. - Parent roadmap (roadmap/infospace-tooling/PLAN.md): header now shows the closed status with final validation metrics. - S3 close-out plan (roadmap/infospace-s3-closeout/PLAN.md): records the final task dispositions. C.1–C.6 and C.8 done; C.7 (clean per-chapter git history) is deferred indefinitely — the task was cosmetic, its prerequisite branch no longer exists, and reconstructing 35 archival commits would not change any output files. Rationale documented inline. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
MarkiTect Project Roadmap
This roadmap directory contains planning directories for roadmap topics.
- When starting to implement a topic its directory will be timestamped
- If implementing multiple topics in parallel use branches
- Keep current state of what's next to implement in TODO.md
- See ../history directory for closed topics
Naming Convention
Directory Format: yymmdd-topic-name
- Use 2-digit year prefix (e.g.,
260106-for 2026-01-06) - Lowercase topic names with hyphens
- Examples:
260106-semantic-document-validation,260105-schema-evolution
This convention keeps names concise while maintaining chronological sorting.
Purpose
This planning documentation serves multiple purposes:
- Implementation State Awareness: Allow for recovery after breaks or breakdowns
- Minimal Plan-Implement Loop: Don't complicate agentic coding with issue tracking if unnecessary
- Planning Info Analysis: Keeping the planning info allows for retrospective analyses to optimize
- Clean Repo Structure: Using roadmap/ for planning and TODO.md as current state helps stay organized
xxx