feat: Current Status sections for 6 edition-drift anchors (batch 2 of #603)#605
Conversation
…LLM-Coding#603) Six anchors whose referent has editions or successors now state what is current, which edition an LLM's training-data prior most plausibly serves, and how to disambiguate in prompts. Every fact and link was researched and fetch-verified by parallel research agents: - OWASP Top 10: 2025 edition is current (finalized around the turn of 2025/26); bare category IDs are ambiguous across editions - ISO/IEC 25010: 2023 revision has nine characteristics (Safety added, Usability and Portability renamed); the prior serves the withdrawn 2011 model - MADR: 4.0.0 current; the prior reproduces the 2.x-era template - Effective Go: deliberately frozen since 2009 (golang/go #28782); predates generics and modules - Bloom's Taxonomy: 1956 nouns vs 2001 verbs; priors blend both - Cockburn Use Cases: Use-Case 2.0 anchors on its own; the official Use Case 3.0 ebook (2024) exists but its prior is thin Also establishes the contribution convention: every new anchor requires a criticism / edition-drift research step (CONTRIBUTING EN+DE, anchor template, CLAUDE.md checklist) — and fixes the batch-1 Wolf Schneider source to the concrete Sprachlog post naming Schneider directly. Refs LLM-Coding#603 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Caution Review failedPull request was closed or merged during review No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (19)
WalkthroughDas PR implementiert eine Konvention zur Dokumentation von Kritik und aktuellem Status bei Semantic-Anchors. Neue Beitragspflichten werden in den Contributing-Richtlinien und Checklisten festgelegt, die AsciiDoc-Vorlage wird mit strukturierten Forschungsblöcken erweitert, und elf bestehende Anker werden mit „Current Status"- oder verfeinerten „Criticism"-Abschnitten aktualisiert. Alle Quellen werden vor dem Commit verifiziert. ChangesBeitragsrichtlinien, Vorlagen und Anker-Dokumentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related issues
Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
Second batch of the catalog triage in #603: the six anchors with the clearest edition drift now carry a Current Status section (EN:
== *Current Status*:, DE:== *Aktueller Stand*:). Each section answers three questions: what is current, which edition the LLM's training-data prior most plausibly serves, and how to disambiguate in prompts.All facts and links were researched by six parallel agents with a mandatory fetch-verification step (the batch-1 lesson, applied from the start this time) — every URL below was retrieved and content-checked before it went into a file.
Anchors covered
owasp-top-10iso-25010madreffective-goblooms-taxonomycockburn-use-casesAlso in this PR
docs/anchors/_template.adoc, and the CLAUDE.md checklist.Verification
node scripts/render-docs.jsrenders all 317 anchor fragments without errorsRefs #603 — batch 3 (remaining tables A–C) follows.
🤖 Generated with Claude Code
Summary by CodeRabbit
Dokumentation