chore(claude): encode 10 borrowings from IDSD series — disciplines + /feature-spec rigor + lineage

[emeraldleaf]

Summary

Outcome of auditing all 5 articles in Kapil Viren Ahuja's IDSD vs SDD series (Activated Thinker, March–May 2026) plus our own deliberation. 10 method additions across 3 surfaces. One originally-proposed change (Connections section in `/feature-spec`) dropped — Ahuja himself walked it back in "The Anatomy of Intent" article.

Changes by file

`CLAUDE.md` — 2 new disciplines under Debugging Discipline (+4 lines)

• Presence in the loop, not approval at the gate — names the distinction between pattern-conforming features (gate review fine) and non-pattern-conforming features (stay present during build). Ties to `/feature-spec`'s Significance Check.
• Continue is the verb that gets you in trouble. Build is not. — prototypes need a token budget + stop-time set up front. From The Trap: "Nobody approves that. It approves itself, one month at a time."

CLAUDE.md size: 301 → 305 (well under the 400 soft cap).

`.claude/commands/feature-spec.md` — 6 additions

• Step 1 prepended with Value gate (3 CXO questions): who needs this, would we still build it at engineering-time cost, who owns saying no. Source: The Trap.
• Goal section gets the two-implementations test — if only one implementation can satisfy this, you wrote a spec disguised as a goal. Source: Anatomy of Intent.
• Acceptance criteria gets the constraints-vs-failure-conditions decision rule callout. Source: Anatomy of Intent.
• Affects gets a new "Upstream dependencies (assumptions that could shift)" subsection — names load-bearing context so the AI flags during build if any moves. Source: SDD Will Collapse.
• New Non-functional constraints section (optional, 5-7 lines max, business language, not implementation patterns). Source: Anatomy of Intent.
• Step 5 added: Hole-test — final completeness check before shipping the spec. Source: Anatomy of Intent. "Closing the loop" renumbered to step 6.

`docs/dev-loop.md` — 2 additions

• "This is a method, not a harness" section right after At a glance — encoding loop is the method; Claude Code, CodeRabbit, GitHub Actions, Spec Kit, BMAD, Kiro, Garura are harnesses. Source: Ahuja's framing.
• "Lineage and grounding" section before Source links — Larman/Basili 2003, Ostroff/Makalsky/Paige 2004 XP, METR 2025, Anthropic September 2025 postmortem, OpenAI Symphony April 2026, Uber 2026 budget burn, IDSD series. Includes the decay warning (every method eventually decays toward what it replaced — Agile → spec-process-with-shorter-cycles, etc.) and the encoding loop's defenses against decay.

Also corrected stale "six destinations" in At a glance → "five surfaces" to match the 5-surface encoding model shipped in #114.

What was deliberately NOT added

• Connections section in `/feature-spec` — Ahuja walked this back in "The Anatomy of Intent": "For every team that already had a service mesh, the slot bled straight into Context, and the line stopped being sharp."
• Acceptance split into Failure Conditions + Success Scenarios — Ahuja's reward-hacking argument (compartmenting evals) doesn't map to NextAurora's stack (Claude Code + CodeRabbit + deterministic CI gates). Adds visible ceremony for theoretical benefit. Revisit if team rollout surfaces friction with the unified Acceptance section.

Verification

• `wc -l CLAUDE.md`: 305 lines (soft cap 400, hard fail 500)
• Broken-link audit on full repo: exit 0
• All cross-references resolve

What this is NOT

• Not a Spec Kit competitor — encoding loop is the method, harnesses (Claude Code, CodeRabbit, GitHub Actions) carry it out
• Not a re-adoption of per-feature SDD — `/feature-spec` remains the lean handoff document, now with better completeness checks
• Not the final form — Ahuja's own decay-warning applies; periodic `/check-rules` audits should catch drift if these rules accumulate ceremony

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Expanded feature specification template with validation gates, constraint classification, and completeness checks to improve specification quality.
  • Enhanced debugging discipline rules documentation with additional best practices.
  • Updated development methodology documentation with improved encoding surface references and lineage/grounding context.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[coderabbitai]

Ready to act? Review this PR in Change Stack to turn feedback into patch suggestions you can inspect and refine.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: c566660a-3436-4b8d-894f-ddbcc76fc3f3

📥 Commits

Reviewing files that changed from the base of the PR and between e189e31 and 6e46e55.

📒 Files selected for processing (3)

• .claude/commands/feature-spec.md
• CLAUDE.md
• docs/dev-loop.md

---

Walkthrough

This PR refines the continuous rule-encoding methodology documentation across three files. The feature-spec command template gains validation gates and completeness checks; the debugging discipline rules expand from three to five; and the development-loop documentation aligns surface counts and adds historical lineage and decay-resistance explanations.

Changes

Continuous Rule-Encoding Methodology Refinement

Layer / File(s)	Summary
Feature Spec Template Enhancements .claude/commands/feature-spec.md	The feature-spec command template is expanded with a value gate requiring three scoping questions before drafting, a two-implementations goal test, constraint-vs-failure classification, upstream dependencies tracking, optional non-functional constraints, and a hole-test completeness scan to detect guess-points in acceptance criteria, affects surfaces, security predicates, and endpoint contracts.
Debugging Discipline Rules Expansion CLAUDE.md	Three new bolded rules are added to the Debugging Discipline section, and the final summary is updated from "All three rules" to "All five rules".
Development Loop Documentation & Lineage docs/dev-loop.md	The reflexive-step lead-in is adjusted to reference five encoding surfaces instead of six destinations. A new "Lineage and grounding" section is appended, documenting prior methodologies, a decay-pattern warning about methods reverting to earlier forms, and explicit defenses explaining how the encoding loop's cross-feature compounding resists decay through surfaces and enforcement disciplines.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• emeraldleaf/NextAurora#115: Continues evolving the .claude/commands/feature-spec.md template, adding and expanding validation sections like the value gate, two-implementation test, and hole-test within the spec-generation flow.
• emeraldleaf/NextAurora#54: Directly updates docs/dev-loop.md around the project's continuous rule-encoding surfaces and associated guideline text.
• emeraldleaf/NextAurora#114: Updates the same rule-encoding documentation in CLAUDE.md and docs/dev-loop.md around the five-surface loop discipline.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main purpose: encoding 10 borrowings from IDSD series across three repository surfaces (CLAUDE.md discipline rules, feature-spec rigor improvements, and dev-loop lineage section).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/encode-idsd-borrowings

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}