dot-iu-cutter v0.1 — G-3 Capability-Intake Reviewer Closure

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

1. Gap Scope

G-3 đóng governance gap về Capability-Intake Reviewer — owners cho TAC capability intakes (Đ38), KG capability intakes (Đ39), policy/threshold tuning intakes, Đ24 vocabulary intakes, tool_revision upgrades, audience filter policy intakes — toàn bộ surface F3 Upgrade Loop của dot-iu-cutter v0.1.

g3_scope:
  intake_kinds_owned:
    - tac_capability (Đ38)
    - kg_capability (Đ39)
    - policy_or_threshold_tuning (always Standard+ per D4 §4.5)
    - dieu24_vocabulary_change (cross-law)
    - tool_revision (always Standard+ per D4 §4.5)
    - audience_filter_policy (joint with G-5)
  scope_basis: D4 design + Governance Closure Package §5.3
  out_of_scope: 
    - schema migration design (FUTURE phase)
    - execution of approved intakes (separate implementation pathway)

G-3 covers WHO reviews capability intake records. G-3 does NOT cover schema design or execution of the changes themselves.

2. Proposed Owner Role (per Đ37)

2.1 Primary Roles

Intake kind	Đ37 role	Approval level
`tac_capability` (Đ38)	TAC Governance Reviewer	Standard+ → Council co-sign
`kg_capability` (Đ39)	KG Governance Reviewer	Standard+ → Council co-sign
`policy_or_threshold_tuning`	Council	Always Standard min (D4 §4.5)
`dieu24_vocabulary_change`	Đ24 Governance (cross-law)	per Đ24 SOP
`tool_revision`	Council + Đ32 review	Always Standard+ min
`audience_filter_policy`	Council + G-5 Access-Control Authority	Standard+ (HIGH if external surface)

Mapping hints:

TAC Governance Reviewer may map to existing Đ38 owner.
KG Governance Reviewer may map to existing Đ39 owner.
Both should exist in current Đ37 SOP under existing law-owner classes (not new roles).

2.2 Joint Authorities

Audience filter policy intakes always joint: G-3 (Capability-intake reviewer) + G-5 (Access-Control Authority) + Council. HIGH risk if customer/partner surface affected.
Tool revision intakes always joint: G-3 + Đ32 + Council. Cross-link with G-4 for DOT-pair drift policy.
Vocabulary intakes always cross-law: G-3 + Đ24 governance. Đ24 has final say on vocabulary content.

3. Backup / Deputy Roles

Primary role	Backup
TAC Governance Reviewer	TAC reviewer deputy (Đ37 SOP standby) or Đ38 owner deputy
KG Governance Reviewer	KG reviewer deputy or Đ39 owner deputy
Council	Đ37 council quorum rules
Đ32 reviewer	Đ32 standby per existing SOP

Backup activation is auditable via Decision Backlog (G-2 custodian).

4. Responsibility Boundaries

4.1 TAC Governance Reviewer

Reviews capability_intake_record of kind tac_capability per D4 §4.2.
Validates impact diff (D4 §4.3) for completeness.
Evaluates risk per Đ32 — escalates to Council for Standard+ risk.
Confirms no Đ24 vocabulary leak (cross-law cooperation with Đ24 governance).
Tracks effective_from dates; ensures cut-over does not corrupt prior manifests at older tool_revision.

4.2 KG Governance Reviewer

Reviews capability_intake_record of kind kg_capability per D4 §4.2.
Validates impact diff on threading / retrieval / edge semantics.
Confirms universal_edges-first discipline (Đ39) is preserved by the intake.
Tracks instrumentation dependencies (cross-link D8 §8 missing-instrumentation backlog).
Escalates to Council if KG capability changes affect graph authority semantics.

4.3 Council (Capability Intake Surface)

Authoritative for policy/threshold/tool_revision intakes (always Standard+ min).
Co-signer for TAC and KG reviewer decisions when risk is Standard or higher.
Final authority on Self-Review cadence (cross-link Decision 8 — held pending Council ratification).
Ratifies allowlist changes for auto-accept (cross-link G-1 Decision 1).

4.4 Đ24 Governance (Cross-Law)

Owns vocabulary intake content.
Without Đ24 ratification, no vocabulary change can be applied to cutter.
G-3 routes vocabulary requests to Đ24 governance — does not invent terms.

4.5 Đ32 (Cross-Law Risk)

Co-reviews tool_revision and any Standard+/HIGH risk intake.
Escalation path for incidents emerging from approved intakes.

4.6 Self-Review Cadence (Decision 8 — Held)

Per D4 §4.4, Cutter Self-Review fires on:

Milestones (N cuts, Y days).
Release cycles (each TAC/KG release).
Patterns (health-signal clusters from D3).
Complaints.

Proposed default cadence:

self_review_cadence_proposal:
  time_based: every 30 days
  cut_based: every 100 cuts
  release_based: every TAC or KG capability acceptance
  complaint_based: ad-hoc on any user/council complaint
status: proposed_pending_council_ratification

Council holds final authority on cadence values.

4.7 Boundaries — What G-3 Does NOT Own

Decision Backlog sweep (G-2).
Threading domain ownership (G-1).
Access-control authority (G-5).
DOT-pair signing (G-4).
Schema design (FUTURE migration phase).
Execution of approved patches (separate implementation pathway).

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

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

#	Criterion	Status
1	TAC Governance Reviewer role recorded in Đ37 SOP	proposed; may map to existing Đ38 owner; requires Council confirm
2	KG Governance Reviewer role recorded in Đ37 SOP	proposed; may map to existing Đ39 owner; requires Council confirm
3	Council ownership of policy/threshold/tool_revision intakes confirmed	proposed (§4.3); requires Council ratification
4	Đ24 cross-law channel formalized	proposed (§4.4); requires Đ24 governance acceptance
5	Council + G-5 joint authority for audience filter intakes confirmed	proposed (§2.2); requires Council + G-5 ratification
6	Self-Review cadence defaults published	proposed (§4.6 default); requires Council ratification
7	D4 intake → review → approval flow documented in Đ37 SOP	proposed; requires Council adoption into SOP
8	Đ32 escalation path for high-risk intakes wired	proposed (§4.5); requires Đ32 + Đ37 confirmation queue
9	D5 backlog entry for G-3 transitions `status = resolved`	pending P0-5 schema + dependency chain (G-1+G-2+G-5) ratify

Net status: 0 of 9 criteria fully met by this document alone. All 9 require Đ37 council action (1–7) plus Đ32 + Đ24 cross-law + P0-5 schema (8, 9).

6. Dependencies

dependencies:
  upstream:
    - G-1 (Threading roles) — required; G-3 needs Threading Domain Owner contract for thread-related intakes
    - G-2 (Backlog Custodian) — required for tracking
    - G-5 (Access-Control Authority) — required; G-3 audience filter intakes need G-5 authority
  parallel:
    - none (G-3 is downstream of G-1, G-2, G-5)
  downstream:
    - G-4 (DOT-pair signing) — depends on G-3 for tool_revision policy
  cross_law:
    - Đ24 (vocabulary intake — must engage)
    - Đ32 (HIGH/Standard+ risk intakes)
    - Đ38 (TAC capability surface)
    - Đ39 (KG capability surface)
    - Đ44 (schema-impacting intakes route to Family Registry)

G-3 cannot ratify until G-1, G-2, G-5 ratify. This is the explicit dependency rule from Governance Closure Execution Checklist §3 dependency graph.

7. Blockers if G-3 Unresolved

If G-3 does NOT close:

Capability intakes accumulate as proposed — cutter cannot absorb TAC/KG improvements → positive recursion loop (P10) cannot close (D4 §4.9 anti-stale rule fires but routing breaks).
Tool revisions could deploy without Đ32 risk approval → Đ32 violation; criterion 28 DOT-pair drift risk.
Đ24 vocabulary changes risk silent invention — criterion 39 violation.
D4 implementation planning blocked — capability intake subsystem cannot enter migration design phase without reviewer contract.
G-4 (DOT-pair signing) cannot start — tool_revision policy (§2.1) is a G-3 surface; G-4 depends on it.
Decision 2 (retrieval targets) cannot be tuned over time — tuning is a D4 capability intake; without G-3, targets become frozen.
Decision 1 allowlist expansion blocked — allowlist changes are D4 intakes routed through G-3.
Self-Review cadence undecided — cutter goes stale (D4 §4.9 explicit trigger).
Audience filter intakes blocked at intake step even after G-5 closes — G-5 owns authority but G-3 owns review process.
9 missing-instrumentation items (D8 §8) remain unrouted; instrumentation backlog stays frozen.

8. Required Ratification Authority

ratification_authority:
  primary: Đ37 Council
  per_role_specific:
    tac_governance_reviewer: Council confirms (may map to existing Đ38 owner)
    kg_governance_reviewer: Council confirms (may map to existing Đ39 owner)
    council_intake_authority: Council ratifies own scope claim
    audience_filter_joint: Council + G-5 joint ratify
  cross_law:
    dieu24: vocabulary intake acceptance channel
    dieu32: HIGH/Standard+ risk co-review path
    dieu38: TAC capability owner alignment
    dieu39: KG capability owner alignment
    dieu44: schema-impacting intake route to Family Registry
  risk_class: Standard (governance role assignment; HIGH for individual high-risk intakes downstream)
  dieu32_required: 
    for_g3_role_assignment: NO (Standard)
    for_high_risk_intakes_post_g3: YES (per intake)
  user_required: NO (User PASS on design phase covers strategic direction)
  council_quorum: YES
  dependency_chain_must_close_first: [G-1, G-2, G-5]

9. Final Status

g3_status: proposed_closed_pending_council_ratification
g3_ratification_authority: Đ37 Council + Đ24 + Đ32 + Đ38 + Đ39 cross-law confirmations
g3_dependency_status:
  g1_threading_roles: pending (blocks G-3)
  g2_backlog_custodian: pending (blocks G-3 tracking)
  g5_access_control_authority: pending (blocks G-3 audience-filter intake authority)
g3_blocks_downstream:
  g4_dot_pair_signing: blocked until G-3 closes
  decision_1_allowlist_expansion: blocked
  decision_2_retrieval_target_tuning: blocked
  self_review_cadence_ratification: blocked
acceptance_criteria_satisfied_by_this_document: 0 of 9
acceptance_criteria_pending_dieu37_council: 7 of 9 (criteria 1–7)
acceptance_criteria_pending_cross_law_and_schema: 2 of 9 (criteria 8, 9)
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