Skip to content

docs(adr): reader-centric status accuracy (ADR-0032 + ADR-0036)#152

Draft
BinHsu wants to merge 1 commit into
mainfrom
docs/adr-accuracy-hygiene
Draft

docs(adr): reader-centric status accuracy (ADR-0032 + ADR-0036)#152
BinHsu wants to merge 1 commit into
mainfrom
docs/adr-accuracy-hygiene

Conversation

@BinHsu

@BinHsu BinHsu commented Jun 19, 2026

Copy link
Copy Markdown
Owner

Reader-centric ADR status hygiene (docs for a cold future reader / token-paying agent): a doc's true status should be visible without cross-checking code.

  • ADR-0032 — one-line "Superseded by ADR-0036" redirect banner at the top (the Status cell already says it, but verbosely; the banner is the cheapest signal).
  • ADR-0036 — Status Proposed → Accepted (realized 2026); aegis-platform-aws + aegis-core-deploy are live on main.

Deliberately NOT edited (verified against the files): ADR-0019 already leads with its partial-supersede + has a Supersession note; ADR-0033 already has a prominent Revision section and a "kube-prometheus → Alloy" edit would risk inaccuracy (core-deploy's collector may genuinely be kube-prometheus — the prometheus-vs-mimir category error). No decision substance changed.

DRAFT for async review.

🤖 Generated with Claude Code

https://claude.ai/code/session_014AQtyw8bug7HhRFQbtMJqy

A cold future reader (or a token-paying agent) should see a doc's true status
without cross-checking code. Two minimal, no-substance edits:

- ADR-0032: add a one-line "Superseded by ADR-0036" redirect banner at the very
  top, so a reader landing on the file sees it's superseded before reading the
  verbose Status cell.
- ADR-0036: Status Proposed -> Accepted (realized 2026) — the topology is live
  (aegis-platform-aws + aegis-core-deploy on main); the ldz#214 items pending at
  write time are resolved.

Deliberately NOT touched: ADR-0019 (Status already leads with the partial
supersede + has a Supersession note) and ADR-0033 (already carries a prominent
Revision section; a "kube-prometheus -> Alloy" edit risks inaccuracy since
core-deploy's collection layer may genuinely be kube-prometheus — a category
error to avoid).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014AQtyw8bug7HhRFQbtMJqy
@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7cd66109-8ca4-494a-b8e7-738804f94715

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/adr-accuracy-hygiene

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.

1 participant