05 — Current RP State & Mutation Need

RP classification view — live composition status

match 21 (none) · mismatch 3 (the cleanup, tool-gated) · drill_overload 9 (keep — law-valid, Đ26 td-matrix ladder) · no_ref 4 (rp_local / retire candidate). Total 37 active.

The 3 mismatches (the only data cleanup)

PIV-001 molecule→atom, species catalog (SPE-CAT, clean), lane governance_home. PIV-016 atom→meta, species 'species' (SPE-SPE, ambiguous_meta), lane rp_local. PIV-021 atom→molecule, species checkpoint_support (SPE-CKS, clean), lane rp_local. All three born, is_active=true, governance-attached. The view computes the correct target composition — truth already visible.

Is any RP mutation required before resuming IU work?

No. (1) RP view is live. (2) No immediate mutation required to continue miếng-thông-tin work: the 3 mismatches are classification-accuracy flags, not integrity faults; downstream IU work reads the governed composition the view already exposes. (3) Deferred cleanup is well-defined: update composition_level on 3 rows via dot-pivot-update once lawfully born.

RP schema split (domain_facet + pivot_kind + drill_level)

Still pending/deferred. The view already separates registry_group_kind and pivot_kind as computed columns — enough to resume; the physical base-table split is a later owner-scoped RP build, out of this minimal macro's scope.

Conclusion

RP is clean-enough-to-resume: classification attached and live; only data cleanup (3 composition fixes) is tool-gated and deferrable; no mutation required to continue IU work. RP cleanup NO-GO; RP work GO via Path 3.