From e8a79077e90d1c6aa6b8e278f9f1348ea39d0cd7 Mon Sep 17 00:00:00 2001 From: emeraldleaf Date: Fri, 5 Jun 2026 15:06:36 -0600 Subject: [PATCH] docs(audits): re-audit IDSD article with full content MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit User pasted the full article (~3000 words) shortly after the initial paywall-limited audit. Re-ran the audit against the actual IDSD method definition. New verdict: ⚙️ Parallel methodology with complementary scope. IDSD = Intent-Driven Software Development, built on ICE framework (Intent, Context, Expectations). Article fully defines Intent's 5 parts: description, constraints, failure scenarios, success scenarios, connections. Expectations + Context are flagged for future pieces. Scope comparison: - IDSD = per-feature loop (Intent + Expectations + Context as 3 crafts) - Encoding loop = cross-feature compounding (5 surfaces + enforcement spectrum + "next session smarter") They're complementary, not competitive. Five borrowable framings identified: 1. "Connections" requirement in /feature-spec (traceability gap) 2. Hole-test ("hand it to someone not in your head") 3. "Presence in the loop, not approval at the gate" discipline 4. "Method vs harness" distinction made explicit 5. Academic grounding citations (Larman/Basili 2003, Ostroff/Makalsky/ Paige 2004 XP, METR 2025 trial, OpenAI Symphony case study) Co-Authored-By: Claude Opus 4.7 --- .claude/audits/INDEX.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.claude/audits/INDEX.md b/.claude/audits/INDEX.md index e2fb5730..d86fd216 100644 --- a/.claude/audits/INDEX.md +++ b/.claude/audits/INDEX.md @@ -29,4 +29,4 @@ Persistent log of every `/article-audit` run. One row per audit; full reasoning | 2026-06-03 | [Git commands every engineer should know](2026-06-03-git-commands-reference.md) (Pavle Davitković) + Anton Martyniuk's rebase-on-shared-branches comment | 🔧 Anton's rule (rebase-vs-merge) followed by behavior, no encoding | Opened #105 (after user pushback on initial "no action" verdict) | | 2026-06-03 | [IServiceScopeFactory vs IServiceProvider](2026-06-03-iservicescope-vs-iserviceprovider.md) (LinkedIn DI lifetimes comment follow-up) | 🔧 Partial — mechanism in #103, IServiceProvider anti-pattern not yet | Update #103 body | | 2026-06-05 | [10 harmful .NET packages](2026-06-05-harmful-dotnet-packages.md) (LinkedIn listicle) | ⚙️ 8 of 10 already encoded equivalently; load-bearing disagreement on NSubstitute (article says replace with Moq, project explicitly rejects Moq); tactical divergence on FluentAssertions replacement (project chose AwesomeAssertions fork over article's Shouldly/xUnit) | No action | -| 2026-06-05 | [The Method That Replaces SDD — IDSD](2026-06-05-idsd-replaces-sdd.md) (Kapil Viren Ahuja, Activated Thinker) | ❓ Paywalled — visible intro corroborates project's encoding-loop stance; IDSD methodology itself unauditable | No action; follow-up if article becomes accessible | +| 2026-06-05 | [The Method That Replaces SDD — IDSD](2026-06-05-idsd-replaces-sdd.md) (Kapil Viren Ahuja, Activated Thinker) | ⚙️ **Parallel methodology with complementary scope** — IDSD addresses per-feature loop (Intent + Expectations + Context), encoding loop addresses cross-feature compounding. Re-audited after user pasted full article (initial verdict was paywall-limited). 5 borrowable framings identified | Propose 5 method additions: "Connections" section in /feature-spec, hole-test, "presence in loop" discipline, "method vs harness" doc, academic citations |