Hartmut
5d9f4218a0
Replace manual field definition with a visual field catalog where admins toggle available attributes on/off and set defaults inline. New files: - blueprint-field-catalog.ts: 36 pre-defined fields across 7 categories (Client & Billing, Technical Specs, Scope, Person Info, Organization, Contract, Skills & Work) for both PROJECT and RESOURCE targets - FieldCard.tsx: toggle card with type icon, expandable default value editor, required/show-in-list toggles, helper text - BlueprintFieldCatalog.tsx: main catalog modal with category sidebar, search bar, collapsible sections, custom field support UX improvements: - All standard fields pre-defined — users toggle instead of typing - Default values set inline on each card (type-appropriate inputs) - Fields grouped by category with enable counts - Search/filter to find fields quickly - Custom fields still supported via "Add Custom Field" - Full backward compatibility: existing fieldDefs auto-map to catalog 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/.