Skip to content

docs: the Phase 9 drill gap is closed, so stop documenting it as open - #44

Merged
MCKRUZ merged 1 commit into
mainfrom
docs/phase-9-drill-record
Aug 1, 2026
Merged

docs: the Phase 9 drill gap is closed, so stop documenting it as open#44
MCKRUZ merged 1 commit into
mainfrom
docs/phase-9-drill-record

Conversation

@MCKRUZ

@MCKRUZ MCKRUZ commented Aug 1, 2026

Copy link
Copy Markdown
Owner

Completes the cross-repo half of claude-code-sdlc#35, which explicitly called for it: "Either way, docs/phase-9-example.md in the standard repo needs correcting to match."

Stacked on #43 — the companion Steps tabs — because the drill-record claims live in both the pre-existing Example tab (on main) and the new Steps tab (only on #43's branch). Merge #43 first; GitHub will retarget.

Depends on claude-code-sdlc#37. Do not merge this before that one, or the standard will describe a step the plugin does not yet ship.

What changed and why

The standard described drill-record.md as optional with nothing producing it — 4 places in docs/phase-9-example.md, 7 in docs/companion/phase-9.html. That was accurate when written. SDLC PR #37 ships Step 4: Alert Drill, an artifact spec, a template, and promotes the artifact to required, so it is now wrong.

Phase 9 also went from seven numbered steps to eight; the example's procedure preamble said seven.

What I deliberately kept

  • The gap callout survives as a closed-gap note rather than vanishing. The gap is why the step exists, and Harbor's silent-night bug is the evidence that justified it. Deleting the history would make the step look arbitrary.
  • The fatigue-review record is still marked . It genuinely remains optional with nothing writing it — that claim is still true and was left alone. Only drill-record changed.
  • "A green gate is not a finished phase" stands. The gate still cannot tell whether the drill actually happened, or whether the record was written from memory the morning of the gate. Step 4 says to write it as it runs; nothing can enforce that, and the page now says so explicitly rather than implying the step solved it.

Test plan

  • Standard test suite: 46 passed
  • scripts/check_standard.py: No drift — all 6 checks ok
  • Companion page tags balanced (4 <main>, 49 <section>, 295 <div>, each matched)
  • Zero remaining "nothing writes it" / "no step runs the drill" / "specified by nothing" claims about the drill
  • Human read-through of the two rewritten callouts

🤖 Generated with Claude Code

The standard described drill-record.md as optional with nothing producing
it, in four places in the worked example and seven in the companion page.
That was accurate when written and is now wrong: claude-code-sdlc PR #37
ships Step 4 (Alert Drill), an artifact spec, a template, and promotes the
artifact to required.

The "gap that should alarm you most" callout becomes a closed-gap note
rather than disappearing — the gap is the reason the step exists, and the
Harbor silent-night bug is the evidence for it.

The Steps tab no longer tells a reader to write the file by hand with no
specification; it points at Step 4 and the shipped template.

What stays: the fatigue-review record really is still optional with nothing
writing it, and the gate still cannot tell whether a drill happened or
whether the record was written from memory the morning of the gate. Step 4
says to write it as it runs; nothing can enforce that.

46 passed; check_standard.py reports no drift; tags balanced.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FEA6GZUG9NKNQYrJKyDGdb
@MCKRUZ
MCKRUZ changed the base branch from docs/companion-runbook-tabs to main August 1, 2026 21:03
@MCKRUZ
MCKRUZ merged commit 60f96b4 into main Aug 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant