migration: add capability ledger foundation

2026-08-05 08:57:24 +03:00
parent c3ac183fff
commit 060f1c9ac1
5 changed files with 762 additions and 0 deletions
@@ -0,0 +1,35 @@
+# Capability ledger
+
+This directory is the versioned, machine-readable register that prevents active
+2019 capabilities from silently disappearing during the Autodesk 2026 migration.
+It is product-neutral by schema: Plant 3D, Revit and Navisworks records use the
+same required fields, while product adapters remain outside the ledger.
+
+Current coverage is deliberately narrow: active, non-archive `P_Rec_Annot`
+Plant 3D command registrations. The generated ledger does not claim to be a
+complete inventory of the 2019 ecosystem. Launcher, profiles, palettes,
+resources, Revit and Navisworks must be added as independently audited slices.
+
+## Working journal — 2026-08-05
+
+1. This work makes a real 2019 capability visible, owned and decidable rather
+   than treating the first migrated command as the programme boundary.
+2. It closes the risk that active P_Rec_Annot commands disappear unnoticed.
+3. The schema is reusable for Revit and Navisworks because it describes a
+   capability and its evidence, not a Plant API.
+4. No Launcher or product domain logic is introduced.
+5. The scope statement and source pointer make missing coverage explicit.
+6. Equivalence is proven only by the record's verification method and runtime
+   evidence; `NOT REPORTED` remains explicit.
+7. Users gain an accountable migration path for every currently-audited active
+   P_Rec_Annot command, including the already verified reference vertical.
+
+## Regeneration and validation
+
+```powershell
+pwsh migration/tools/Build-CapabilityLedger.ps1
+pwsh migration/tools/Test-CapabilityLedger.ps1
+```
+
+The builder consumes audited source records only, excludes `_archive`, writes
+stable IDs, and retains unknowns instead of manufacturing a target decision.