dot-iu-cutter v0.5 — Repo Authority Resolution: Recommendation

Phase: v0_5_iu_cutter_repo_authority_resolution · Nature: recommendation_only__sovereign_decision_routed · Date: 2026-05-18 · doc 3 of 4

classification: ONLY_WORKING_TREE_MIRROR_FOUND
recommended: OPT-A1 (git init + baseline commit C1, then branch-apply)
decision_authority: GPT / User ONLY ; self_advance: PROHIBITED

---

1. Situation (one line)

The authoritative iu-cutter code exists locally only as a non-git working-tree mirror at /Users/nmhuyen/iu-cutter-build/repo/iu-cutter (C1); there is no git-tracked repository anywhere reachable; the BLOCKED patch-apply phase is git-bound and cannot proceed until a git-tracked authoritative repo is designated/established (a sovereign decision).

2. Options for GPT / User (sovereign)

OPT-A  (RECOMMENDED) — establish the git-tracked authoritative repo, then
       re-run the patch-apply+CI phase against it:

  A1 (PREFERRED): GPT/User authorize, in a separate explicitly-gated phase:
       step 1  `git init` C1 = /Users/nmhuyen/iu-cutter-build/repo/iu-cutter
       step 2  baseline commit of the EXISTING ratified v0.4 skeleton EXACTLY
               as-is (9 cutter_agent modules + 5 tests + cli.py + .gitignore;
               __pycache__ excluded via .gitignore) — NO content change,
               commit message records "baseline: ratified v0.4 skeleton,
               pre-patch, no modification"
       step 3  create a feature branch
       step 4  apply the additive patch (KB doc 2) on that branch — verify
               written-file sha256 == f1f42e83… (dryrun.py) /
               31143968… (test) — run the unit suite as CI — report
               git diff/status — NO commit-to-default, NO deploy, NO
               first dry-run (all remain separately gated)
       why preferred: preserves diff / branch / rollback / CI guarantees the
               patch-apply phase exists to provide; C2 stale mirror is not
               touched; additive patch keeps zero regression on v0.4 baseline.

  A2: GPT/User point to a real GitHub-backed iu-cutter clone (on the VPS or
       another host) as the canonical apply target, AND make it accessible
       for inspection (current tooling cannot see the VPS filesystem/git).
       Use ONLY if such a canonical remote-tracked repo actually exists and
       supersedes C1 as SSOT — otherwise A1.

OPT-B  (LESS PREFERRED) — GPT/User explicitly authorize a NON-git plain-file
       application into C1 with sha256 verification (written files must hash
       to f1f42e83… / 31143968…), accepting the documented loss of git
       diff / branch / rollback / CI guarantees. Only on explicit user
       preference for a quick non-git apply.

3. Recommendation

recommend: OPT-A1
basis:
  - C1 is the KB-SSOT authoritative working tree and is the most complete
    v0.4 skeleton; it already carries .gitignore (intended git-tracking).
  - the patch is purely additive (2 new files, 0 modified) → a clean baseline
    commit + branch-apply yields an exact, revertable diff and runnable CI,
    which is precisely the guarantee the BLOCKED phase requires.
  - governance: never invent missing authority — `git init` + baseline is a
    sovereign act, so it is ROUTED, not taken here.
do_NOT:
  - use C2 (.iu-cutter-stage) as the apply target (stale subset of C1).
  - assume a VPS repo exists (C5 unobservable; no container; allowlist-denied).
  - proceed without an explicit GPT/User ruling.
gating_unchanged: even after OPT-A1/A2/B, the FIRST Constitution dry-run, CUT,
  VERIFY, production DB, commit-to-default, and deploy remain SEPARATELY gated.

4. Exact next action requested of GPT/User

rule_one_of:
  - "OPT-A1: authorize a gated phase to git-init + baseline-commit C1, branch,
     then apply+CI the additive patch (no default-branch commit, no deploy,
     no dry-run)"
  - "OPT-A2: designate + make-accessible the canonical git-backed iu-cutter
     repo to use instead of C1"
  - "OPT-B: authorize non-git sha256-verified plain-file apply into C1"
then: a new explicitly-authorized phase executes the chosen option; this agent
  does not self-advance.

5. Statement

• QG1–QG4 PASS (nothing modified / no git init / no apply / no commit-deploy).
• QG6 PASS: recommendation is explicit and singular (OPT-A1).
• doc 3 of 4 → resolution report (4). STOP after 4 → GPT/User. Self-advance PROHIBITED.