Hartmut
0f129dc0de
Budget Forecast Widget: - Project: "Active projects with a defined budget" - Budget Usage: "Percentage of total budget consumed by current allocations" - Burn/mo: "Monthly burn rate based on currently active allocations" - Exhaustion: "Projected date when budget will be fully consumed" Project Health Widget: - Project: "Active projects scored across three health dimensions" - B / S / T: "Budget health, Staffing health, Timeline health" - Score: "Composite score: average of Budget, Staffing, Timeline (0-100)" - Score badge: dark theme variants for green/amber/red Skill Gap Widget: - Skill: "Skills required by open demand positions" - Demand: "Number of unfilled demand requirements needing this skill" - Supply: "Number of active resources with this skill at proficiency 3+" - Gap: "Supply minus Demand: negative = shortage, positive = surplus" All three: added dark:bg-gray-800/50 thead, dark:divide-gray-800 tbody, dark:hover:bg-gray-800/30 rows, dark:text-gray-100/300/400 text colors. Co-Authored-By: claude-flow <ruv@ruv.net>
Documentation Index
Date: 2026-03-12 Purpose: Single entry point for active Planarchy product and technical documentation.
Canonical Documents
| Topic | File | Use |
|---|---|---|
| Active roadmap and open gaps | product-roadmap.md | Primary backlog and current delivery order |
| Estimating system design | estimating-extension-design.md | Workbook analysis, field mapping, and implementation plan |
| Dispo import implementation | dispo-import-implementation.md | Clean-slate Dispo v2 import design, mapping rules, staging flow, and commit policy |
| Dispo import ticket pack | dispo-import-implementation-tickets.md | Worker-ready delivery slices, dependencies, and acceptance criteria for the Dispo import |
| Demand/assignment cutover guide | demand-assignment-migration-cutover.md | Go/no-go criteria, staged cutover, and readiness artifact policy |
| Strategic architecture direction | v2-architecture-proposal-2026-03-11.md | Longer-horizon architecture target |
| Implementation history | LEARNINGS.md | Append-only decisions and lessons |
| Agent/project guidance | CLAUDE.md | Working conventions and quality gates |
Archive Policy
Older plan and proposal markdown files stay in the repository only as archive notes when:
- the feature is already implemented enough to leave the active backlog
- the content was merged into a canonical document
- the file still has historical value, but should not drive current work
Archive-note files should point back to the relevant canonical document instead of carrying parallel backlog state.
Current Archive Notes
All archived markdown plan and proposal files now live under docs/old-markdowns/.