KB-119C
RP Aggregate Pivots — 07 Done-Enough for Information Work
3 min read Revision 1
registries-pivotdone-enoughinformation-work2026-06-03
07 — Done-Enough for Miếng Thông Tin (Workstream F)
Evaluation against the done-enough checklist
| criterion | state |
|---|---|
| parent graph live? | ✅ 26 roots / 6 parents / 13 children, 0 dangling/cycle/inactive-parent/self-edge |
| key aggregate pivots live? | ✅ PIV-311 (IU=219) + PIV-313 (sys-issues open=207,940) committed, pivot_backed |
| DOT drill honest? | ✅ PIV-104 sums to 309, reconciles to PIV-007 (RECONCILES); no drill mismatch anywhere |
| PIVOT_MISSING list explicit? | ✅ v_rp_aggregate_candidate_register lists every missing/candidate/law aggregate with live count + status |
| final substrate available? | ✅ node contract final_substrate_ref on every leaf |
| UI contract sufficient? | ✅ base node contract + 2 additive views cover tree, counts, candidate, drill, drift, unverifiable |
no dependency on invalid dot-pivot-update? |
✅ untouched/unused |
Decision
- DONE_FOR_INFORMATION_WORK: YES. RP now reflects PG automatically (hierarchy by
parent_codedata, counts by engine, no Nuxt math), the count surface is honest (final vs candidate vs missing vs law vs drill vs unverifiable), and the DOT drill no longer lies. Information-piece work can proceed against the backend contract. - DONE_FOR_UI_IMPLEMENTATION: YES (read-only). The UI can build the old Registries-style surface from
v_registries_pivot_node_contract+v_rp_drill_reconciliation+v_rp_aggregate_candidate_registerwith zero recomputation.
What is explicitly NOT claimed done (and is NOT a blocker to information work)
- Promotion of orphan/phantom/drift/KG to FINAL canon pivots — owner law ratification (future).
- PIV-500 grand-total closure — needs a ratified anchor set (future); surfaced honestly as UNVERIFIABLE.
- PIV-304 unmanaged definition — needs law (future).
- dot_tools record-surplus 146 (phantom-candidate) hygiene — a birth/orphan-track concern, not an RP layer/count concern; surfaced via
drift_status. registry_pin/ label-by-facet — next phase.
These are information-layer-orthogonal: they are correctly surfaced (never hidden, never faked), which is all the information work needs.
Single smallest remaining blocker (to full aggregate ratification, not to information work)
Owner ratification of the law definitions in doc 04 (unmanaged + grand-total anchor) and the candidate promotion criteria in doc 03. Engineering is complete; nothing else blocks.