# nagent_review_v3_1_20260620 — Delta Summary

**Date:** 2026-06-20
**Status:** Draft (Phase 1 setup complete; cluster thickening in progress)
**Owner:** Tier 1 Orchestrator
**Delta from:** v3 (`nagent_review_v3_20260619.md`, 803 lines, 2026-06-19)
**Spec pair:** `spec_v3.1.md` + `plan_v3.1.md`

---

## What v3.1 changed

### Per-cluster thickening (11 clusters)

The main review file (`nagent_review_v3_20260619.md`) is thickened in place. Each cluster section grows from ~50-65 lines to 300-450 lines (or 400-500 for deep-dive clusters §9-§11). The thickening follows the chunking strategy (per `spec_v3.1.md` §4.1).

| § | Cluster | v3 lines | v3.1 target | Phase |
|---|---|---|---|---|
| §1 | Campaigns | ~50 | 350-450 | Phase 2 |
| §2 | Conversation safety net | ~60 | 350-450 | Phase 3 |
| §3 | Hooks | ~60 | 350-450 | Phase 4 |
| §4 | Project-local roots | ~50 | 300-400 | Phase 5 |
| §5 | Provider expansion | ~50 | 300-400 | Phase 6 |
| §6 | Delegation rewrite | ~50 | 300-400 | Phase 7 |
| §7 | Robustness | ~60 | 350-450 | Phase 8 |
| §8 | Operating rules | ~60 | 300-400 | Phase 9 |
| §9 | Case-study methodology | ~65 | 400-500 | Phase 10 |
| §10 | PEP case study | ~50 | 400-500 | Phase 11 |
| §11 | Collisions case study | ~50 | 400-500 | Phase 12 |

### Three new top-level sections (Phase 13)

- **§12 YAML avoidance** (~200-300 lines): catalogs every YAML use site in nagent; flags them as "do not adopt" for Manual Slop; documents the markdown + custom DSL alternative. Captures the user's directive: "I don't like YAML ... I would not use it in whatever I take from his nagent implementation. I would continue to utilize markdown in combination with a custom DSL."
- **§13 Agent context-window observations** (~200-300 lines): captures the user's OpenCode + MiniMax M3 empirical findings (warm-up ~100-150k; window up to ~500k; safe zone 250-350k; compact→re-warm→continue cycle); notes nagent's stricter enforcement; documents Manual Slop's partial mitigation via `docs/` + `conductor/` markdown navigation; flags the "agents forget to read" shortcoming; proposes nagent's `--hook-per-run` as the pattern for closing the gap.
- **§14 Fine-tuning observations** (~150-250 lines): captures the diagnosis (current generalized models bottlenecked by not having conventions baked in) + Together.ai observation + lists 6 prosumer fine-tuning vendors in a comparison table; flags that vendor analysis is out of scope for v3.1.

### Side artifacts refresh (Phase 14)

- `comparison_table.md` REPLACED with v3.1 content (adds rows for §12, §13, §14).
- `decisions.md` REPLACED with v3.1 content (adds Candidates 27-30).
- `nagent_takeaways_v3_1_20260620.md` NEW bridge doc (~150 LOC, 5-part structure).

### Section renumbering (user directive 2026-06-20)

Per the user's directive — "just cohesively adjust the sections so the information flows well with the user's subjective opinion preserved" — v3's existing `§12 Decisions` / `§13 Cross-references` / `§14 References` are renumbered to `§15` / `§16` / `§17`. The new §12-§14 (YAML avoidance, agent context-window, fine-tuning) go in the spec's specified positions. The information flow is now: clusters (§1-§11) → new observations (§12-§14) → decisions (§15) → cross-references (§16) → references (§17). The observations come before the decisions because the observations inform the decisions.

## What v3.1 did not change

- The 11-cluster scheme from v3 stands.
- All v2.x historical reviews + v3 spec/plan/bridge preserved unchanged.
- `conductor/tracks.md` not modified.
- No new commits to nagent or the case-study repos are reviewed (v3 baseline preserved).
- No project source code modified (research-only track).

## Verification

Per `spec_v3.1.md` §7 verification criteria (12 criteria). All verified in Phase 15.

## See also

- `spec_v3.1.md` — the v3.1 spec
- `plan_v3.1.md` — the v3.1 plan
- `nagent_review_v3_20260619.md` — the thickened main review
- `nagent_takeaways_v3_1_20260620.md` — the v3.1 bridge doc
- `comparison_table.md` — v3.1 comparison table
- `decisions.md` — v3.1 candidate list
