Thore CimbalandClaude Opus 4.8
cffb507310
Resolving W6 earlier today I added the addendum rule straight into docs/aar/template.md — a framework file pinned byte-identical to the neckbeard baseline, and pruefe_upstream_drift.py exists precisely to catch that. Its docstring even cites the question that prompted it: whether agents would rewrite AGENTS.md. So the check caught exactly the thing it was built for, and the fix is to put the rule where project-specific rules belong. Template restored byte-identical; the addendum practice now lives in the project section of AGENTS.md, with a note saying why it is not in the template. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
35 lines
910 B
Markdown
35 lines
910 B
Markdown
---
|
|
type: aar
|
|
status: open # open | harvested
|
|
date: YYYY-MM-DD
|
|
related: [] # design docs, issues, ADRs involved
|
|
---
|
|
|
|
<!-- Copy to docs/aar/YYYY-MM-DD-slug.md. Delete comments when filling in.
|
|
Standalone AARs are for incidents and major deviations only —
|
|
normal undertakings get their AAR as Gate 5 inside the design doc. -->
|
|
|
|
# AAR: Title
|
|
|
|
## What was planned / expected
|
|
|
|
## What happened
|
|
|
|
<!-- Facts and timeline, not blame. -->
|
|
|
|
## Why the difference
|
|
|
|
<!-- Root cause. For failures, name the routing class:
|
|
intent issue / spec issue / code issue. -->
|
|
|
|
## Learnings
|
|
|
|
<!-- What future-you should know. Blunt beats polite. -->
|
|
|
|
## Actions
|
|
|
|
<!-- Concrete: wiki pages updated (FAQ, Stolpersteine) with links,
|
|
framework issues opened, tests added. When all actions are done,
|
|
set status: harvested. The refinement session walks all AARs
|
|
still marked open. -->
|