03 — G2 Human-Org-Role Law (Đ37-H) Sovereign Enactment Packet (Branch C)

Authority status: NOT_FOUND (doc 01) → agent does NOT enact. This is the final sovereign enactment packet. The law is review-ready from prior campaigns; this consolidates the enactment contract.

1. Gap (live, verified this session)

governance_registry = 9 rows: GOV-COUNCIL (council), GOV-DOT / GOV-KG-SYS / GOV-NRM-SYS / GOV-SIV (system), GOV-MOW/MOT/MOIT/MOUT (factory/mother). 0 human-organizational roles. No staff / department_lead / super_admin; no view/edit/approve/delegate/escalate verbs; no Directus-policy binding. This blocks: MOW-UI, the Governance Cockpit human-visibility layer, and the human side of Đ32 approval (G3).

2. Why it is independent of Đ37

Đ37 = factory/system agency axis (gov_type ∈ council/system/factory). Đ37-H = human organizational axis (who, in the org, may act on what). They are orthogonal; Đ37-H does not amend Đ37's rows — it adds a human-role substrate. No conflict.

3. Law text skeleton (sovereign to finalize + enact)

• Đ37-H.1 Roles: staff, department_lead, super_admin, plus the existing ROLE-AGENT (tier 0).
• Đ37-H.2 Verbs: view, edit, approve, delegate, escalate.
• Đ37-H.3 Role × verb matrix (recommended):

Role	view	edit	approve	delegate	escalate
staff	✓ (scope)	✓ (own draft)	✗	✗	✓
department_lead	✓ (dept)	✓ (dept)	✓ (in-scope, low-risk)	✓ (to staff)	✓
super_admin	✓ (all)	✓ (all)	✓ (with cross-sign)	✓	n/a
ROLE-AGENT	✓ (scoped)	propose/draft	✗ (never)	✗	✓ (raise flag)

• Đ37-H.4 AI/Agent boundary: AGENT cannot approve, delegate, flip gates, or mint terminal review_decision. This is the law-level statement of "no agent self-approval / no self-mint."
• Đ37-H.5 Approval routing: in-scope/low-risk approval may be a department_lead; cross-domain/high-risk requires council/sovereign cross-sign ≥2 (feeds G3).

4. Registry home decision (sovereign chooses)

A human-role registry is itself a governed collection birth subject to the same meta_catalog cascade/guard reversibility as G1. Two options:

• (a) Separate human_org_role + human_role_grant registry (recommended; clean separation, prior campaigns drafted this).
• (b) Extend governance_registry with human gov_type (smaller footprint, muddies the agency axis). Either way the birth follows the G1 procedure (doc 02 §2–§6) once the law is enacted.

5. Directus / Nuxt / Mother implications

• Directus: map each Đ37-H role to a Directus policy; super_admin → admin policy, department_lead → scoped collection policies, staff → read+own-draft.
• Nuxt: UI gating is downstream and remains NO-GO until runtime gates open; document-only here.
• MOW/MOT/MOIT/MOUT impact: factory rows gain a human-ownership/permission placeholder; no double-ownership (Đ7) — human roles operate factories, they do not own outputs the factories own.

6. Enactment contract (FOUND_VALID definition)

Enacted = law file revision bumped with Đ37-H text + a council/sovereign approval record + (if chosen) the role substrate born per G1 procedure. No agent action beyond producing this packet.