KB-1C3D

dot-iu-cutter v0.5 — Repo Authority Resolution: Evidence Review (KB SSOT cross-check; classification = ONLY_WORKING_TREE_MIRROR_FOUND)

5 min read Revision 1

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

Phase: v0_5_iu_cutter_repo_authority_resolution · Nature: read_only_evidence_review · Date: 2026-05-18 · doc 2 of 4

decision_authority: GPT / User ONLY ; self_advance: PROHIBITED

1. KB SSOT cross-check

SSOT_designated_path: /Users/nmhuyen/iu-cutter-build/repo/iu-cutter
  source: code-authoring report §2 + code-authoring plan §1 (both name this
          path; both already record "NOT a git repository").
patch_apply_BLOCKED package (4 docs) finding: identical — repo path correct
  per SSOT, but git_state = NOT a git repo (no .git in dir or any parent;
  parent walk to /; find under trees + /Users/nmhuyen => no .git anywhere).
this_phase_live_reprobe: CONFIRMS prior finding byte-for-byte. C1 still not a
  git repo; dryrun.py / test_dryrun_snapshot_mark.py still ABSENT (rule #2
  clean — additive, no clobber). C2 stage copy also not a repo.
consistency: this investigation does NOT contradict KB SSOT; it corroborates
  it and adds the negative filesystem sweep + VPS access boundary.

2. Per-candidate authority weighing

C1 /Users/nmhuyen/iu-cutter-build/repo/iu-cutter
  pro: KB SSOT explicitly designates it; most complete v0.4 skeleton
       (9 cutter_agent modules + 5 tests incl. test_real_postgres_adapter.py);
       carries .gitignore (intended-to-be-git-tracked hint).
  con: NOT a git repository (no .git) — plain working-tree mirror only.
  verdict: authoritative WORKING TREE, but not a git repo.

C2 /Users/nmhuyen/.iu-cutter-stage/iu-cutter
  pro: contains a cutter_agent skeleton.
  con: strict subset of C1 (4 tests, missing test_real_postgres_adapter.py,
       no .gitignore); KB plan §1 labels it "older stage copy"; older mtime.
  verdict: NOT authoritative; must NOT be the apply target. Divergence from
       C1 is a stale-copy artifact, NOT a competing authoritative repo.

C5 VPS /opt/incomex/dot[/iu-cutter]
  status: UNDETERMINED (INSUFFICIENT_ACCESS — no git/FS introspection tool;
       read_file allowlist denies it). No iu-cutter container running.
  verdict: cannot be confirmed or excluded as a git repo from here. Not
       usable as an apply target without it being made observable/accessible.

3. Conflict analysis

multiple_copies_present: YES (C1 + C2) — but they are NOT "multiple
  conflicting GIT repos": neither is a git repo at all, and C2 is a stale
  subset of C1, not an independent authority. KB SSOT unambiguously picks C1.
classification_decision_tree:
  - REAL_GIT_REPO_FOUND?            NO  (zero .git anywhere local; VPS unknown)
  - MULTIPLE_CONFLICTING_REPOS?     NO  (no repos; C2 is a stale mirror of C1,
                                         SSOT already disambiguates to C1)
  - INSUFFICIENT_ACCESS?            PARTIAL — applies ONLY to the VPS candidate
                                         (C5); the local question IS fully
                                         answerable and is answered.
  - ONLY_WORKING_TREE_MIRROR_FOUND? YES — the dominant, decision-bearing fact:
                                         the authoritative iu-cutter code
                                         exists locally only as a non-git
                                         working-tree mirror (C1).

4. Determination

PRIMARY_CLASSIFICATION: ONLY_WORKING_TREE_MIRROR_FOUND
  authoritative_working_tree: /Users/nmhuyen/iu-cutter-build/repo/iu-cutter (C1)
  git_tracked: NONE
SECONDARY_NOTE: VPS candidate (C5) = INSUFFICIENT_ACCESS (cannot probe);
  no evidence of a real repo there (no container, allowlist denies FS) — it
  must not be assumed to exist. If GPT/User believe a canonical GitHub-backed
  clone exists on the VPS or elsewhere, that location must be made accessible
  before it can be evaluated (see recommendation doc 3, OPT-A2).
NOT MULTIPLE_CONFLICTING_REPOS: C2 is a stale subset mirror; SSOT designates C1.

5. Statement

  • QG1–QG4 PASS: nothing modified; no git init / patch apply / commit / deploy.
  • Evidence consistent with KB SSOT (corroborated, not contradicted).
  • doc 2 of 4 → recommendation (3), report (4). STOP after 4 → GPT/User. Self-advance PROHIBITED.
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/v0.5-iu-cutter-repo-authority-resolution/dot-iu-cutter-v0.5-repo-authority-evidence-review-2026-05-18.md