05 — Naming Decision Packet (Action B, for council)

12 rows need a domain (FAC-02 role) decision. These are genuinely semantic — this macro does not self-ratify. Below: grouped by proposed target, with a recommended default where evidence is strong, and the one place a new FAC-02 label may be warranted.

FAC-02 vocabulary (live, 5 labels)

code	name	meaning (system role)
LBL-101	Cấu trúc	structure / schema / registry skeleton
LBL-102	Nội dung	content / work-item data
LBL-103	Quy tắc	rules / definitions / constraints
LBL-104	Công cụ	tools / automation / executable capability
LBL-105	Giám sát	monitoring / oversight / governance infra

Group 1 — governance infrastructure → LBL-105 Giám sát (recommended; strong)

pivot_code	source	species	rationale
PIV-015	trigger_registry	governance_infra	trigger/monitoring infra
PIV-017	species_collection_map	governance_infra	governance mapping infra
PIV-018	entity_audit_queue	governance_infra	audit/oversight queue
PIV-019	birth_registry	governance_infra	lifecycle oversight

Recommendation: LBL-105. Confidence: high. These are oversight/audit infra.

Group 2 — structural meta-registry → LBL-101 Cấu trúc (recommended; strong)

pivot_code	source	species	rationale
PIV-016	entity_species	species (meta)	the registry-of-registries skeleton

Recommendation: LBL-101. Confidence: high. (PIV-016 also takes the Action-A composition fix → meta in the same future dot-pivot-update.)

Group 3 — rule definitions → LBL-103 Quy tắc (recommended; medium-high)

pivot_code	source	species	rationale
PIV-012	checkpoint_types	checkpoint_type	rule/definition catalog
PIV-013	checkpoint_sets	checkpoint_set	rule grouping
PIV-021	task_comments	checkpoint_support	rule/monitoring support → LBL-103 or LBL-105

Recommendation: LBL-103 for PIV-012/013. PIV-021 is a coin-flip (LBL-103 vs LBL-105) — council to decide; default LBL-103 (it supports checkpoint rules). (PIV-021 also takes Action-A composition fix → molecule.)

Group 4 — work-item content → LBL-102 Nội dung (recommended; medium)

pivot_code	source	species	rationale
PIV-010	tasks	task	work-item content (vs LBL-104 if seen as tooling)

Recommendation: LBL-102. Confidence: medium. Alt LBL-104 if tasks are framed as automation units.

Group 5 — process automation → NEW LABEL DECISION REQUIRED

pivot_code	source	species	current token
PIV-004	workflows	workflow	quy_trình
PIV-005	workflow_steps	workflow_step	quy_trình
PIV-006	workflow_change_requests	wcr	quy_trình

These already carry the provisional domain token quy_trình (process), which has no exact FAC-02 label. Two governed options — council must choose:

• Option 5a (no vocab change): map the workflow family to LBL-104 Công cụ (treat process automation as tooling). Cheapest; slightly lossy.
• Option 5b (extend vocab): create a new governed label LBL-106 Quy trình via the classification.label DOTs (Đ24 path) and map PIV-004/005/006 to it. Cleaner taxonomy; adds one governed label.

Recommendation: 5b if the team expects process/workflow to be a first-class reporting axis (it is a distinct "4-mothers" concern); else 5a. Either way it is an L1 governed-vocabulary change — never a manual UPDATE.

Operator / council wording (paste-ready)

"Ratify FAC-02 role assignments for 12 RP pivots: Giám sát(105): PIV-015,017,018,019; Cấu trúc(101): PIV-016; Quy tắc(103): PIV-012,013 [+021?]; Nội dung(102): PIV-010. For the workflow family (PIV-004,005,006): choose (a) map to Công cụ(104), or (b) create LBL-106 'Quy trình' and map to it. PIV-021 role: Quy tắc(103) vs Giám sát(105) — choose. On ratification, apply each via the governed dot-pivot-update --code <PIV> --group <token> (no manual UPDATE)."

What does NOT wait on this packet

Nothing in the live view waits — RP UI/API consumes the mapping today and shows these as fac02_pending_naming. The packet only governs the eventual write-back of a domain token onto the base rows (via the future update-DOT).