# sub-lead-view-auditor-0 — H24 LIGHT-AUDIT S137 (2026-07-17)

> vai-STALE. Enum ĐÓNG (5 view-*): view-stale-count · view-stale-status · view-stale-header · view-stale-role-desc · view-residual-asym.
> Cadence: light=6 deep=15 jump_on_class_repeat=3. class_repeat baseline: view-residual-asym=1, view-stale-count=1.
> Window S125->S137, focus S133-S137 (wave adap khung-nhip da349fc + freeze-NS Mig67 S133 + luy-ke S134).
> Machine base = gov-detectors-S137-base.txt TOTAL 46 (mostly pre-existing classified; W3/S132 closeout-gap = FP DO-NOT-flag). I do SEMANTIC only.

## Ghi-dia-trong-luc-lam (anti-#53). Append findings below as I verify.

---

## CANDIDATES (verifying)

### VERIFIED so far
- ROSTER clean: agents/README:5,:27 = 14 (10 product/quality + 4 monitor), points to STATUS canonical, refuses hardcode. STATUS recent frozen blocks (484/493/512/523/533) = "Sub-agents 14" correct. "Sub-agents 12" hits (192/216/243/276/309) = S108-S111 frozen blocks (correct for their time). NO view-stale-role-desc.
- COUNTS clean: STATUS CURRENT STATE 439=Mig 67, 446=528 test = canonical-by-definition, disk-verified (detector C2/B3). Machine already owns derived count-drift (CLAUDE.md:86 etc, LOW).
- per-label folding "treo" = CLEAN NEGATIVE in my lane. Only live hits: WAL.md:7,:14 (EXCLUDED, em-main updates) + governance-detectors.ps1:920 (em-main in-progress fix, told-not-to-flag W3) + investigator-codebase diary:23 (sub-diary, not lead-surface). No LIVE lead-surface asserts treo.
- OVERDUE/cadence: no LIVE assertion. "counter=7/OVERDUE none" only in frozen blocks STATUS:492(S133), :564(S122), HANDOFF:13(S131-2), :81(S128). Not stale.
- tiep.md §2.5 (110-112) tick+dong-no WIRED = S131 de-xuat (1) LANDED, counter runtime-ticked to 11.

### FLAG CANDIDATES
- F1 (view-stale-status, LOW, self-resolving): HANDOFF:7 (current S134 NEXT-anh) item (5) "2 de-xuat S131 CHO GAT" — both actioned: tick-wire committed da349fc @S136 (tiep.md:110-112 + counter last_ticked=S137) + light-run = THIS consented audit. Source contradicts "CHO GAT/pending". Note: also "CHO HUB reply-batch" likely stale (wave processed /check-email AI_INFRA + _owner_ratified cites reply e50a4bd0). Resolves at S137 session-end rewrite.

- F2 (view-stale-status, LOW but PERSISTENT 15 sessions — headline): STATUS.md:450 (CURRENT STATE §Sub-agents Note, the LIVE canonical roster cell) still says 2 H24 monitors "⚠️ CHUA verified-runtime — ... 14/14 spawn-probe PHAI chay SAU RESTART". SOURCE contradicts: STATUS.md:557 (Recently Done S122) "Spawn-probe 14/14 SONG (0 error/0 garble) — roster→14 chung runtime" + counter.json (monitors ran S124 first-real-run + THIS S137 audit). ASYMMETRY: office-document sibling in the SAME cell got its "✅ verified-runtime S107" flip; H24-monitor caveat left un-flipped since S121. view says "CHUA verified-runtime / must run after restart" vs source "14/14 spawn-probe SONG S122 (Agent-tool registry) + monitors ran S124/S137". resolve: flip ⚠️→✅ verified-runtime S122; keep the real residual noted at :557 (hmw.js→agentType path still uncovered — that part is TRUE, only the Agent-tool 'PHAI chay SAU RESTART' is satisfied).

### INFORM (not flags)
- INFORM-1 (cross-ref omission/H1): memory-budget.json "measured" block (144-155) lists 12 role rows, predates + omits the 2 H24 monitors (added S121, 16 sessions). _note honestly scopes to S107 snapshot → does NOT assert current roster, so NOT view-stale (missing rows = omission-lane gap-*, or H1 measurement-freshness). Surfacing for lead-omission-auditor.
- INFORM-2 (context): governance-detectors.ps1:920 "union-per-label ... retires the tail-adjacency" = em-main's IN-PROGRESS fold+guard fix for W3 FP (told-not-to-flag). No live LEAD-surface asserts "per-label folding treo" (only WAL.md excluded + this in-progress script + a sub-diary). Prompt's hypothesized treo-stale = clean negative in my lane.

### SCOPE NOTE (honest)
- Wave S135-S137 (da349fc) not yet in STATUS CURRENT STATE / HANDOFF top = primarily OMISSION (lead-omission-auditor lane), NOT mine. I flag ONLY the two specific CONTRADICTIONS (F1, F2), not the general not-yet-harvested state.
- Machine-owned (NOT re-flagged): derived count-drift (CLAUDE.md:86, SKILL.md ×N — LOW), title-freshness (rag-setup-plan:4, form-engine SKILL:15 — H24-1), W3 closeout-ritual FP. My 2 flags are SEMANTIC (machine cannot judge "CHO GAT now actioned" / "CHUA verified-runtime should flip").

## TALLY
- TOTAL: 2 FLAG (view-stale-status ×2) + 2 INFORM
- class_repeat impact: view-stale-status fires THIS audit (baseline was 0; class_repeat had view-residual-asym=1, view-stale-count=1). 2 instances = within-audit seeding tally, NOT cross-audit repeat ⇒ jump_on_class_repeat (N=3) does NOT fire. em-main: bump class_repeat.view-stale-status per contract.