dot-iu-cutter v0.1 — G-1 Threading Roles Closure

Date: 2026-05-15 Status: CLOSURE RESULT — G-1 step of Governance Closure Execution Trigger: GPT PASS on G-2 closure; batch execution of remaining 4 gaps Baseline: Governance Closure Execution Checklist §6 + User Decision Confirmation §4.1 (Decision 1) + Governance Closure Package §5.1 + D9 design Scope: CLOSURE RECORD ONLY. No code, no DDL, no migration, no PG mutation, no implementation planning. G-1 alongside G-3, G-4, G-5 batch; dependency order preserved.

1. Gap Scope

G-1 đóng governance gap về Threading Roles — owner / reviewer / arbitration / oversight roles cho semantic_thread lifecycle, membership, anomaly handling, và user-AI disagreement resolution trong dot-iu-cutter v0.1.

g1_scope:
  threads_in_scope: semantic_thread family per D9
  scope_basis: D9 design + Decision 1 (Balanced auto-accept) + Decision 4 (cutter-only)
  starter_domains: 
    - birth_gate
    - segmentation
  expansion_path: via Decision Backlog (G-2 custodian sweeps) when evidence accumulates
  out_of_scope: cross-DOT thread sharing (future D4 capability intake)

G-1 covers:

Per-thread ownership.
Membership review authority (auto-accept gate enforcement per Decision 1).
Split/merge governance.
User-AI disagreement arbitration.
Anomaly oversight (overbroad, too_narrow, stale, noisy_retrieval).

G-1 does NOT cover:

Schema design for thread tables (FUTURE migration phase; cross-link Đ44 Family Registry).
Retrieval consumer surface (G-5 audience filter authority).
Tool revision policy (G-3, G-4).

2. Proposed Owner Role (per Đ37)

2.1 Primary Roles

Threading concern	Đ37 role	Authority level
Thread owner (per thread)	Threading Domain Owner (Đ37 SOP, per domain)	Low/Standard
Membership reviewer (low-risk)	AI Council reviewer	Low
Membership reviewer (standard/high)	Human reviewer via Đ37 escalation queue	Standard+
Thread split/merge governance	Council	Standard+
User-AI disagreement arbitration	Human reviewer (Đ37 escalation)	Standard
Anomaly oversight	Registry Custodian (G-2) + Council	Standard

Starter Threading Domain Owner appointments:

birth_gate domain → Domain Owner TBD
segmentation domain → Domain Owner TBD

Additional domains added only via Decision Backlog entry + AI Council review + Council ratification (cross-link Decision 1 allowlist expansion).

2.2 Auto-Accept Domain Allowlist Ratification

Per Decision 1 (Balanced thresholds): auto-accept fires only when ALL hold:

confidence ≥ 0.75
≥ 2 independent evidence signals
no negative knowledge conflict
policy explicitly allows
domain in allowlist

Initial allowlist (proposed):

auto_accept_domain_allowlist_v0_1:
  - birth_gate
  - segmentation
allowlist_status: proposed_pending_council_ratification
expansion_rule: per_decision_backlog_entry + AI_Council_review + Council_ratify
contraction_rule: any Threading Domain Owner may petition removal; Council decides

The AI Council reviewer enforces the allowlist at runtime; Council ratifies allowlist changes.

3. Backup / Deputy Roles

Primary role	Backup
Threading Domain Owner	Threading Domain Owner Deputy (per domain)
AI Council reviewer	Redundant AI reviewer instance (separate execution context per D2 §4.7)
Human reviewer	Đ37 escalation queue standby reviewer
Council	Đ37 council quorum rules apply (no single seat)

Backup activation is auditable via Decision Backlog (kind=escalation, custodian per G-2 tracks).

4. Responsibility Boundaries

4.1 Threading Domain Owner

Owns thread lifecycle (create, supersede, split/merge) within their domain.
Confirms thread membership candidates flagged needs_human per D9.
Reviews thread health signals (overbroad, too_narrow, stale) routed to their domain.
Co-signs split/merge proposals with Council.
Cannot override AI Council reject without Council co-sign (avoids silent override of safety review).

4.2 AI Council Reviewer

Default reviewer for semantic_thread_candidate per D9 §4.3 intake flow.
Applies Decision 1 thresholds (Balanced: conf ≥ 0.75, ≥ 2 signals, allowlist).
Emits accept / reject / needs_human verdict per candidate.
Operates in separate execution context from MARK/CUT to preserve independence (D2 §4.7).
Subject to performance health signal ai_reviewer_drift if reject rate diverges materially over time (custodian-tracked via G-2).

4.3 Human Reviewer

Handles needs_human cases routed by AI Council.
Handles user_ai_disagreement arbitration.
Authority for standard-risk membership decisions.
High-risk legal/governance/code-impact memberships escalate further to Council + Đ32.

4.4 Council (Threading Surface)

Approves Threading Domain Owner appointments per Đ37 SOP.
Approves auto-accept allowlist changes.
Ratifies thread split/merge governance decisions.
Owns escalation finalization for unresolved disagreements.

4.5 What G-1 Roles Do NOT Cover

Schema design for thread family tables → FUTURE migration phase + Đ44 Family Registry.
Audience visibility of threads to external surfaces → G-5 (Access-Control Authority).
Capability intake for new thread evidence types → G-3 (Capability-intake reviewer).
DOT-pair signature on thread operations → G-4.
Sweep / anti-forgetting of governance state → G-2 (Registry Custodian).

5. Acceptance Criteria for Closure (per Checklist §6)

Mapping to Governance Closure Execution Checklist §6 — 9 criteria:

#	Criterion	Status (this closure)
1	Domain Owner role recorded in Đ37 SOP for starter domains	proposed; requires Council ratification
2	AI Council reviewer authority documented in Đ37	proposed (§4.2); requires Council ratification
3	Human reviewer escalation path wired through Đ37 queue (no new channel)	proposed (§4.3); requires Council confirmation that existing Đ37 queue accepts this routing
4	Council ownership of split/merge confirmed	proposed (§4.4); requires Council ratification
5	Disagreement arbitration channel documented	proposed (§4.3); requires Council ratification
6	Anomaly oversight responsibility split recorded	proposed (custodian (G-2) + Council); requires both ratifications
7	Decision 1 thresholds ratified into policy	proposed (Balanced per Decision 1); requires Council ratification + allowlist seed approval
8	D5 backlog entry for G-1 transitions `status = resolved`	pending P0-5 schema realization + Council ratification
9	No parallel governance channels created	honored (this document forbids parallel role)

Net status: 1 of 9 criteria fully met by this document (criterion 9). The remaining 8 require Đ37 Council action (criteria 1–7) plus P0-5 schema realization (criterion 8).

6. Dependencies

dependencies:
  upstream:
    - G-2 (Backlog Custodian) — required for tracking this closure to ratification
  parallel:
    - G-5 (Access-Control Authority) — runs in parallel; both fire after G-2 ratify
  downstream:
    - G-3 (Capability-intake reviewer) — depends on G-1 + G-2 + G-5
    - G-4 (DOT-pair signing) — depends on G-3
  cross_law:
    - Đ24 (vocabulary for any new thread-related labels)
    - Đ32 (high-risk thread decisions)
    - Đ39 (universal_edges authority over thread membership graph)
    - Đ44 (Family Registry for semantic_thread family)

G-1 cannot ratify in isolation. It needs:

G-2 ratified (so this closure can be tracked into PG SSOT once P0-5 lands).
Đ44 Family Registry submission for semantic_thread family (parallel governance phase).
Đ24 cross-law check on threading vocabulary (none introduced here outside D9 design which is already ratified).

7. Blockers if G-1 Unresolved

If G-1 does NOT close:

Ungoverned thread creation — semantic graph grows without accountable owners.
Auto-accept fires without enforcement authority — Decision 1 thresholds operational but no reviewer chain → Đ32 risk gate degrades to honor-system.
user_ai_disagreement events orphaned — no arbitration channel → silent overrides possible (rev5d §13.1.4 guardrail violated).
Anomaly signals (overbroad, too_narrow, stale) unrouted — D3 segmentation health degrades.
D9 implementation planning blocked — threading subsystem cannot enter migration design phase without owner contract.
G-3 cannot start — Capability-intake reviewer's authority for threading-related intakes (e.g. new evidence types) depends on Threading Domain Owner being defined.
Decision 1 effective status stuck — User Decision Confirmation §4.1 explicitly waits on G-1 ratification.
Split/merge governance void — F2 (D3 §4.7, §4.8) cannot execute structural threading changes.
Cross-domain thread orphans — no escalation pattern when threads span multiple domains lacking owners.

8. Required Ratification Authority

ratification_authority:
  primary: Đ37 Council
  per_role_specific:
    threading_domain_owner: Đ37 Council appoints; existing or new SOP entry under governance-ops
    ai_council_reviewer: Council ratifies authority + Decision 1 thresholds
    human_reviewer: Đ37 escalation queue accepts routing
    council_split_merge: Council itself ratifies its own scope claim
  cross_law:
    dieu24: vocabulary check (no new labels introduced beyond ratified D9 set)
    dieu39: universal_edges authority confirms thread membership routing
    dieu44: Family Registry submission for semantic_thread family (parallel; NOT a G-1 prerequisite, but G-1 ratification + Đ44 closure together unblock downstream)
  risk_class: Standard (governance role assignment + Decision 1 allowlist ratification)
  dieu32_required: NO (Standard risk)
  user_required: NO (Decision 1 already User-confirmation-pass via GPT delegation; G-1 ratifies INTO operational form)
  dieu37_council_quorum_required: YES

9. Final Status

g1_status: proposed_closed_pending_council_ratification
g1_ratification_authority: Đ37 Council
g1_starter_allowlist_proposed: [birth_gate, segmentation]
g1_dependencies_preserved: 
  upstream_g2: required_before_pg_tracking_via_p0_5
  parallel_g5: independent_can_run_simultaneously
  downstream_g3: blocked_until_g1_closes
  downstream_g4: blocked_until_g3_closes
decision_1_effective_status: recorded_pending_g1_ratification
acceptance_criteria_satisfied_by_this_document: 1 of 9 (criterion 9)
acceptance_criteria_pending_dieu37_council: 7 of 9 (criteria 1–7)
acceptance_criteria_pending_p0_5_schema: 1 of 9 (criterion 8)
implementation_planning_allowed: false
implementation_execution_allowed: false
no_code: true
no_ddl: true
no_migration: true
no_pg_mutation: true
no_design_or_planning_or_prior_closure_file_modified: true