Skip to content

feat: Current Status sections for 6 edition-drift anchors (batch 2 of #603)#605

Merged
rdmueller merged 1 commit into
LLM-Coding:mainfrom
raifdmueller:feat/603-current-status-batch2
Jun 11, 2026
Merged

feat: Current Status sections for 6 edition-drift anchors (batch 2 of #603)#605
rdmueller merged 1 commit into
LLM-Coding:mainfrom
raifdmueller:feat/603-current-status-batch2

Conversation

@raifdmueller

@raifdmueller raifdmueller commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

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

Anchor Key finding
owasp-top-10 2025 edition is final (RC markers removed Dec 2025); prior serves 2021. Bare category IDs are ambiguous: A03 = Injection (2021) vs Software Supply Chain Failures (2025). Stale "current edition 2021" claim in the anchor body fixed.
iso-25010 2023 revision: nine characteristics (Safety new; Usability → Interaction Capability, Portability → Flexibility); 2011 withdrawn — yet still what most material (and Wikipedia) describes
madr 4.0.0 current; renamed twice (3.x "Any", 4.0 back to "Architectural"); prior reproduces the 2.x-era template (inline Status/Deciders bullets, split consequences)
effective-go Deliberately frozen — exact on-page disclaimer quoted; golang/go #28782 confirmed still open; modern complements linked (Go Code Review Comments, Google Go Style)
blooms-taxonomy 1956 nouns vs 2001 verbs; priors plausibly blend both; Krathwohl 2002 overview linked (verified university-hosted PDF — the usual Vanderbilt link is dead)
cockburn-use-cases Use Case 3.0 officially exists (IJI ebook, de Mendonca & Jacobson, v1.0, June 2024) — but with a thin prior; correct framing is "exists since 2024, supply the definition in the prompt". Use-Case 2.0 anchors on its own.

Also in this PR

  • New contribution convention (the user-requested process change): every new anchor proposal includes a criticism / edition-drift research step; findings land in Criticism / Current Status sections with named, fetch-verified linked sources. Documented in CONTRIBUTING (EN + DE), docs/anchors/_template.adoc, and the CLAUDE.md checklist.
  • Batch-1 source fix: the Wolf Schneider criticism now links the concrete Sprachlog post in which Stefanowitsch calls Schneider the "oberster Sprachnörgler der deutschsprachigen Journaille" (Sprachbrocken 49/2012) instead of a category archive that never names him.

Verification

  • node scripts/render-docs.js renders all 317 anchor fragments without errors
  • All 12 new sections confirmed present in rendered EN + DE HTML output, links spot-checked

Refs #603 — batch 3 (remaining tables A–C) follows.

🤖 Generated with Claude Code

Summary by CodeRabbit

Dokumentation

  • Dokumentation
    • Neue Pflichtanforderung für Semantic Anchors: Recherche und Dokumentation von Kritik und aktuellem Stand (Versionen, Ausgaben, Nachfolger) mit verifizierten, verlinkten Quellen.
    • Aktualisierte Anker-Dokumentationen (Bloom's Taxonomy, Cockburn Use Cases, Effective Go, OWASP Top 10, ISO 25010, MADR, Gutes Deutsch) mit erweiterten „Current Status"- und „Criticism"-Abschnitten.
    • Contributing Guidelines ergänzt mit präzisen Vorgaben zur Quellenverifikation und Formatierung.

…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>
@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 38f2d0ec-8ff6-4773-b236-2174d2209a5f

📥 Commits

Reviewing files that changed from the base of the PR and between 0d569f1 and 5b11030.

📒 Files selected for processing (19)
  • CLAUDE.md
  • CONTRIBUTING.adoc
  • docs/anchors/_template.adoc
  • docs/anchors/blooms-taxonomy.adoc
  • docs/anchors/blooms-taxonomy.de.adoc
  • docs/anchors/cockburn-use-cases.adoc
  • docs/anchors/cockburn-use-cases.de.adoc
  • docs/anchors/effective-go.adoc
  • docs/anchors/effective-go.de.adoc
  • docs/anchors/gutes-deutsch-wolf-schneider.adoc
  • docs/anchors/gutes-deutsch-wolf-schneider.de.adoc
  • docs/anchors/iso-25010.adoc
  • docs/anchors/iso-25010.de.adoc
  • docs/anchors/madr.adoc
  • docs/anchors/madr.de.adoc
  • docs/anchors/owasp-top-10.adoc
  • docs/anchors/owasp-top-10.de.adoc
  • docs/changelog.adoc
  • website/public/CONTRIBUTING.de.adoc

Walkthrough

Das 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.

Changes

Beitragsrichtlinien, Vorlagen und Anker-Dokumentation

Layer / File(s) Zusammenfassung
Beitragspflichten und Prüfliste
CLAUDE.md, CONTRIBUTING.adoc, website/public/CONTRIBUTING.de.adoc
Neue Checklisten-Punkte für neue Anker: Recherche zu dokumentierter Kritik und Edition-Drift ist verpflichtend, Abschnitte müssen mit zitierfähigen, verlinkten Quellen ergänzt werden oder komplett entfallen, wenn keine verifizierten Quellen gefunden werden.
Anchor-Vorlage mit Forschungsblöcken
docs/anchors/_template.adoc
AsciiDoc-Template erweitert um optionale „Criticism"- und „Current Status"-Untersektionen mit Anleitungen zur Quellenrecherche, Bullet-Formaten für verlinkte Kritik, Jahr und Kurzzitate sowie für Edition/Nachfolger-Referenzen.
Current-Status-Erweiterungen (Versionsunterschiede)
docs/anchors/blooms-taxonomy.adoc, docs/anchors/blooms-taxonomy.de.adoc, docs/anchors/cockburn-use-cases.adoc, docs/anchors/cockburn-use-cases.de.adoc, docs/anchors/effective-go.adoc, docs/anchors/effective-go.de.adoc, docs/anchors/iso-25010.adoc, docs/anchors/iso-25010.de.adoc, docs/anchors/madr.adoc, docs/anchors/madr.de.adoc, docs/anchors/owasp-top-10.adoc, docs/anchors/owasp-top-10.de.adoc
Sechs Anker-Paare (je EN und DE) erhalten oder erweitern „Current Status"-Abschnitte, um Editions-Verschiebungen (Blooms: 1956 vs. 2001; ISO 25010: 2011 zurückgezogen, 2023 aktuell; OWASP: 2021 vs. 2025; MADR: 4.0.0 seit September 2024), parallele Nutzung älterer Versionen in LLM-Trainingsdaten und Empfehlungen zur Disambiguierung in Prompts zu dokumentieren.
Kritik-Verfeinerung und Changelog
docs/anchors/gutes-deutsch-wolf-schneider.adoc, docs/anchors/gutes-deutsch-wolf-schneider.de.adoc, docs/changelog.adoc
Kritik-Abschnitte für Gutes Deutsch werden präzisiert: Stärkere Hervorhebung der Ablehnung mit Stefanowitsch-Zitat und aktualisiertem Link. Changelog vermerkt die neuen Current-Status-Abschnitte und die verfeinerte Quellenangabe zur Wolf-Schneider-Kritik.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related issues

  • LLM-Coding/Semantic-Anchors#603: Das PR implementiert direkt die in Issue #603 vorgeschlagene Konvention für verpflichtende Kritik- und Current-Status-Abschnitte mit verifizierten Quellen und Beispiel-Anker-Updates.

Possibly related PRs

  • LLM-Coding/Semantic-Anchors#604: Beide PRs führen Criticism-Abschnitte zu mehreren Ankern ein, einschließlich „Gutes Deutsch (Wolf Schneider)"; PR #604 konzentriert sich auf die Erweiterung einzelner Anker, während dieses PR die Richtlinienfundamente und Template-Struktur etabliert.
  • LLM-Coding/Semantic-Anchors#572: Überschneidung in den Blooms-Taxonomy-Anker-Dateien (blooms-taxonomy.adoc und .de.adoc): Dieses PR fügt Current-Status-Abschnitte hinzu, während PR #572 die ursprüngliche Anker-Dokumentation eingeführt hat.
  • LLM-Coding/Semantic-Anchors#586: Beide PRs modifizieren Cockburn-Use-Cases-Anker-Dokumentation (cockburn-use-cases*.adoc) durch Hinzufügen neuer strukturierter Abschnitte (dieses PR: Current Status; PR #586: Further Reading).

Suggested reviewers

  • JensGrote
🚥 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 Der Titel beschreibt präzise den Hauptzweck: Ergänzung von "Current Status"-Abschnitten für 6 Anker mit Edition-Drift.
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

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.

❤️ Share

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

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.

2 participants