docs(roadmap): commit ladder-climb-roadmap plan (interview-ratified)

[kyle-sexton]

Commits the ladder-climb-roadmap PLAN (Brief + five snowball-ordered phases) per the 2026-07-21 operator approval.

What's in it

• Brief: interview-ratified (25/25, verification-backed); ledger committed alongside (interview-checklist.md) so the rulings' audit trail survives .work sweeps.
• Phase I ignition (autonomy: ignite the 2-to-3 loop — first standing routine (hourly C2 drain) + C2-promotion evidence drain on the proving ground #778): native-first Desktop scheduled task, unattended-execution design surfaces named (availability, catch-up/overlap, partial-run reconciliation, spend bounding, evidence-write serialization); sub-topic autonomy-ignition to follow.
• Phase II enforcement rail (autonomy pipeline: no dedicated security-review pass — automated code review only #509): step-0 consumer sweep + check-context-name capture added ahead of the ADR-0002-ordered three-repo chain.
• Phases III–V: gated outlines (trust promotions, step-3 guardrails, trigger-gated 3→4 births).
• Fresh-context plan review: 3 CRITICAL / 7 IMPORTANT / 4 SUGGESTION — all verified and folded; one finding corrected against the fetched desktop-scheduled-tasks doc (catch-up/overlap natively bounded).

Related

No related issue: this PR commits a roadmap plan; the issues below are referenced for context and are not closed here (each proceeds under its own plan).

• autonomy: ignite the 2-to-3 loop — first standing routine (hourly C2 drain) + C2-promotion evidence drain on the proving ground #778 (Phase I ignition — proceeds under its own sub-topic plan; not closed here)
• autonomy pipeline: no dedicated security-review pass — automated code review only #509 (Phase II enforcement rail ruling), ADR 0002 (ordering guard)
• work-readiness burn list — split-gauge classification of the open backlog (tower-maintained, week of 7/20) #627 (7/26 gauge), program: fresh-eyes checkpoint audit — tag skill actions for same-context bias and retrofit delegation #304 (Phase IV member), autonomy: context-pull leg of 2-to-3 — let Claude read wikis and discussions #779 (deferred context-pull leg)

🤖 Generated with Claude Code

https://claude.ai/code/session_01RdeVMaDzwP26bNiDjqM59Q

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[claude]

Claude finished @kyle-sexton's task in 1m 35s —— View job

---

PR Review

• Gather context
• Read changed files
• Review PLAN.md
• Review design-resolution.md
• Review interview-checklist.md
• Post findings

---

Summary

This is a docs-only commit adding a five-phase program roadmap plan and its supporting interview ledger. No plugin code, manifests, or settings are touched. The structure is internally solid and the stress-test documentation is unusually thorough. Three issues are worth addressing before merge.

---

Findings

1. Stale .work path in design-resolution.md — Medium

design-resolution.md:9

resolved in the interview ledger
(`.work/ladder-climb-roadmap/interview-checklist.md`, 25/25 resolved,

The .work/ tree is gitignored and is swept periodically (see PLAN.md:295). The stated reason for committing interview-checklist.md alongside the plan is precisely so the rulings survive .work sweeps. design-resolution.md still points to the draft .work path rather than the committed location. A fresh session following this pointer finds nothing.

Fix: change the path to the committed location: docs/topics/ladder-climb-roadmap/interview-checklist.md (or a relative ../interview-checklist.md since design-resolution.md sits one level deeper).

Fix this →

---

2. C22 listed as VERIFIED but flagged "not visually confirmed" — Low

interview-checklist.md:106

VERIFIED: … C22 NIST SP 800-218A same-bar (medium-high; PDF not visually confirmed).

Placing a claim inside VERIFIED: while noting the source PDF was not visually confirmed is self-contradictory and undermines the ledger's use as an audit trail. The UNVERIFIABLE block already exists for exactly this case.

Fix: move C22 NIST SP 800-218A same-bar out of the VERIFIED line and into the UNVERIFIABLE block with the reason (PDF access unavailable; accepted on secondary sources).

---

3. Unresolved FALLBACK item references an unlinkable file — Low

PLAN.md:285

[FALLBACK — confirm or override] Scout finding: the routines contract binds SIX adapter
obligations (trigger-dispatch.md:45), while #778's body says "seven obligations" …

trigger-dispatch.md:45 has no repo-relative path or link. A fresh session can't verify the discrepancy. The item is also left open without an operator decision recorded in this PR.

Fix: either resolve the conflict now (add "operator decision: six" or "operator decision: seven" to the line) and add the repo-relative path to trigger-dispatch.md, or open a follow-up issue to track it and link the issue here so it doesn't silently disappear.

---

Notes (no action required)

• Fresh-docs URL not cited in PLAN.md Brief (PLAN.md:8): the Brief says "desktop-scheduled-tasks doc fetched 2026-07-21" without the URL. The URL does appear in interview-checklist.md:44 (code.claude.com/docs/en/desktop-scheduled-tasks). Technically the CLAUDE.md fresh-docs mandate asks for a URL citation; the ledger carries it, so the PLAN.md Brief is fine as a summary, but it's worth noting for consistency.
• docs/topics/autonomy-ignition/PLAN.md does not yet exist (PLAN.md:93): correctly noted as "authored at Phase I start" — not a broken reference, just a forward declaration.
• Phase execution shape and snowball ordering look sound. Phase II's new step-0 consumer sweep + check-context-name capture before any restructure is a good defensive addition.

---

[claude]

Claude finished @kyle-sexton's task in 1m 31s —— View job

---

PR Review

• Gather context and read changed files
• Check whether prior findings were addressed
• Review current state of all three files
• Post findings

---

What changed in the latest push

Commit 05aa695 adds blank lines to PLAN.md and interview-checklist.md to satisfy markdownlint blank-line rules. design-resolution.md was not touched. No substantive content changed — the three findings from the prior review remain open.

---

Open findings (all three carry forward)

1. Stale .work path in design-resolution.md — Medium

design-resolution.md:9–10

(`.work/ladder-climb-roadmap/interview-checklist.md`, 25/25 resolved,

.work/ is gitignored and periodically swept. The ledger was committed to docs/topics/ladder-climb-roadmap/interview-checklist.md precisely so the rulings survive those sweeps — but design-resolution.md still points at the draft path. A fresh session following this pointer finds nothing.

Fix: change the path to ../interview-checklist.md (relative, since design-resolution.md lives one level deeper under design/).

Fix this →

---

2. C22 placed in VERIFIED block while acknowledged as not visually confirmed — Low

interview-checklist.md:112

C22 NIST SP 800-218A same-bar (medium-high; PDF not visually confirmed).

C22 sits inside the VERIFIED: line but the parenthetical admits the source PDF was not directly read. This is self-contradictory and undermines the ledger as an audit trail. The UNVERIFIABLE block at line 116 exists for exactly this case.

Fix: remove C22 NIST SP 800-218A same-bar from the VERIFIED: line and append it to the UNVERIFIABLE: block with note (PDF access unavailable; accepted on secondary sources).

Fix this →

---

3. FALLBACK item cites trigger-dispatch.md:45 without a repo-relative path — Low

PLAN.md:288–290

[FALLBACK — confirm or override] Scout finding: the routines contract binds SIX adapter
obligations (trigger-dispatch.md:45), while #778's body says "seven obligations" …

trigger-dispatch.md:45 has no repo-relative path. A fresh session cannot locate or verify the discrepancy. The item is also still marked [FALLBACK — confirm or override] with no operator decision recorded.

Fix (either):

• Record the operator decision inline (six is authoritative — correct #778) and add the full path to trigger-dispatch.md; or
• Open a follow-up issue tracking the discrepancy and link it here so it doesn't silently disappear.

Fix this →

---

Notes (no action required)

• The 05aa695 markdownlint commit is clean — blank-line additions are correct and complete for the two files it touches.
• design-resolution.md was not included in the markdownlint pass; it has no blank-line issues that need addressing beyond the path fix above.
• The forward reference to docs/topics/autonomy-ignition/PLAN.md (PLAN.md:93) remains a valid forward declaration — not a broken reference.

---