06 — Naming + Retire Action Packets

No auto-ratification. Naming targets below are recommendations with evidence for the council. Each carries the exact DOT command to run after approval, plus rollback.

FAC-02 governed vocabulary (live)

LBL-101 Cấu trúc · LBL-102 Nội dung · LBL-103 Quy tắc · LBL-104 Công cụ · LBL-105 Giám sát. There is no LBL-106. So quy_trình and dữ_liệu have no governed FAC-02 mapping yet — that is precisely the council decision.

A. The 12 naming decisions (rg_kind/domain provisional + rp_local domain intent)

#	Pivot	species	current registry_group	recommended FAC-02	rationale
1	PIV-004	workflow	quy_trình	LBL-106 (new "Quy trình") or LBL-104	process-domain; no existing label fits cleanly
2	PIV-005	workflow_step	quy_trình	LBL-106 / LBL-104	as above
3	PIV-006	wcr	quy_trình	LBL-106 / LBL-104	as above
4	PIV-012	checkpoint_type	quy_trình	LBL-103 (Quy tắc)	checkpoints encode rules
5	PIV-013	checkpoint_set	quy_trình	LBL-103 (Quy tắc)	as above
6	PIV-010	task	dữ_liệu	LBL-102 (Nội dung)	task records are content
7	PIV-015	governance_infra	default(rp_local)	LBL-105 (Giám sát)	governance infra = monitoring
8	PIV-017	governance_infra	default	LBL-105 (Giám sát)	as above
9	PIV-018	governance_infra	default	LBL-105 (Giám sát)	as above
10	PIV-019	governance_infra	default	LBL-105 (Giám sát)	as above
11	PIV-016	species (meta)	default	LBL-101 (Cấu trúc)	species registry = structural meta
12	PIV-021	checkpoint_support	default	LBL-103 (Quy tắc) or LBL-105	support of rule checkpoints — council to pick

Why these are NOT a simple dot-pivot-update run

Two distinct changes hide here, and only one is a registry_group value edit:

1. New label (quy_trình→LBL-106) requires adding a taxonomy row first (a taxonomy/label DOT or Directus action) — dot-pivot-update does not create labels and its validator will reject an unknown registry_group until the label exists.
2. Remap to an existing label can be done as a registry_group edit, but the deeper, correct fix is the schema split (domain_facet + pivot_kind + drill_level) so that registry_group's domain-vs-shape conflation is resolved structurally (see §09).

Post-approval command pattern (per row, once the FAC-02 value is governed/in-use)

dot-pivot-update --code PIV-0xx --field registry_group --value <approved_value> \
                 --reason "council FAC-02 ratification <ref>"          # dry-run
dot-pivot-update --code PIV-0xx --field registry_group --value <approved_value> --commit
# rollback: dot-pivot-update --code PIV-0xx --field registry_group --value <old> --commit

B. The 2 retire candidates — already retired (no action)

Pivot	registry_group	is_active	composition	note
PIV-020	default	false	atom	already soft-deleted; species null; no_ref
MTX-TEST	test	false	matrix	already soft-deleted; test scaffold

Both are is_active=false already → dot-matrix-retire would early-exit ("already retired"); dot-pivot-update refuses inactive rows by design. Identity impact of a hard delete: DO NOT hard-delete — Đ26 lifecycle is soft-delete (is_active=false + superseded_by). Hard delete would break pivot_results history and any parent_code references. Recommended action: none (leave retired), optionally set superseded_by='deprecated' via dot-matrix-retire if not already set.

C. Blocked / deferred

• 9 drill_overload rows: law-valid, keep (resolved by schema split, §09).
• 2 ambiguous_meta species (PIV-016, PIV-103 = governed meta-species species): not bugs — a governed meta-species legitimately pivots over entity_species. Keep.
• L2-gated items: none for RP classification (L2 not required here).