KB-1FE3

RP Final Acceptance 08 — Information-Piece Handoff

3 min read Revision 1
registries-pivotinformation-handoffmieng-thong-tin2026-06-03

08 — Information-Piece (Miếng Thông Tin) Handoff

Operative doc for the next Agent/GPT to continue information-piece work WITHOUT rediscovering RP.

Canonical RP surface

  • Primary UI/data surface: v_registries_pivot_surface (hierarchy + counts + pin order + grouping). Order by pin_sort_rank, display_order.
  • Base contract (26 cols): v_registries_pivot_node_contract.
  • Tree skeleton: v_registries_pivot_tree.
  • Candidates/non-final: v_rp_aggregate_candidate_register.
  • Drill reconciliation: v_rp_drill_reconciliation.
  • Count integrity (leaf): v_count_integrity (160 leaves).
  • Leaf drill/substrate: fn_registries_pivot_node_substrate(code) (STABLE).
  • Pin registry: registry_pin (INSERT to pin; empty today). Grouping policy: rp_grouping_policy (default 50).
  • Route /knowledge/registries-pivot; API /api/registries-pivot/{summary,rows,node}.

Statuses

  • count_status=pivot_backed → FINAL; PIVOT_MISSING → not yet defined (never 0).
  • grouping_status: SATISFIED=drill · NEEDS_GROUPING=show total + needs-grouping · NOT_REQUIRED=flat · NO_COUNT=missing.
  • pin_state: PINNED/UNPINNED. drift_status: ok/drift/null.
  • candidate aggregate_status: CANDIDATE_REPORT_ONLY (badge), NEEDS_LAW_DEFINITION (propose, never 0), NOT_A_PIVOT_EQUATION_VIEW (equation + UNVERIFIABLE).
  • drill_status: RECONCILES / WARNING_DRILL_MISMATCH (none today) / ADVISORY.

FINAL vs CANDIDATE

FINAL = pivot_backed nodes (PIV-001..019,021,207,311,313; 22 pivot-backed leaves). CANDIDATE/not-final = register rows (orphan 59, phantom 289, drift 3, KG 2,259, unmanaged NULL, grand-total NULL; is_canonical_pivot=false).

Forbidden (do not regress RP)

No Nuxt count math; no hardcoded depth/pins; no candidate→FINAL without owner law; no faked grand-total/unmanaged; no RP cleanup/dot-pivot-update; no hiding PIVOT_MISSING/candidate/warnings.

Next practical tasks

  1. Define the miếng-thông-tin unit and map to substrate (information_unit PIV-311=219, system_issues PIV-313=207,940).
  2. Define group pivots for NEEDS_GROUPING roots (IU by type/topic; issues by status/severity) → drill becomes SATISFIED.
  3. Pin owner rows (INSERT INTO registry_pin …).
  4. (Operator) deploy UI patch P1–P5.

Verify layer graph: SELECT count() FILTER (WHERE is_root), count() FILTER (WHERE has_children) FROM v_registries_pivot_tree; → 26 roots, 6 parents.

Verify integrity: SELECT count_integrity_status, count(*) FROM v_count_integrity GROUP BY 1; → 152 ok/5 unverified/3 failed. Drill reconciles PIV-007/009/016.

Back to Knowledge Hub knowledge/dev/reports/architecture/registries-pivot-final-acceptance-law-pin-ui-information-handoff-2026-06-03/08-information-piece-handoff.md