docs(adrs): reconstruct decision records from existing specs#81
Merged
Conversation
Backfill the permanent ADR spine established in kagenti#79 by distilling one Architecture Decision Record from each design spec in docs/specs/. - 23 ADRs, numbered chronologically (0001–0023) by spec date, each recording a single headline decision under the ADR template (Context / Decision / Alternatives considered / Consequences) and linking back to its source spec for the full reasoning. - Status derived from reality: Implemented (17, built/merged) and Accepted (6, design-only Z-track + capability-charter reprioritization). - Supersession notes where the milestone registry records one (MCP code-mode ⊃ parent MCP gateway; credentialed egress ⊃ parent M9; inference injector realizes parent M8). - Add an index table to docs/adrs/README.md. The requirements/evidence doc (pipeline-archetypes) is intentionally not given an ADR — it records requirements, not a decision. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Paolo Dettori <dettori@us.ibm.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Backfills the permanent ADR spine established in #79 by reverse-engineering one Architecture Decision Record from each design spec in
docs/specs/. Docs-only; no runtime changes.0001–0023by the source spec's date (numbers are permanent).Implemented(built/merged) and 6Accepted(the design-only Z-track credential plane + the capability-charter reprioritization).docs/adrs/README.md.The
pipeline-archetypes-requirementsdoc is intentionally excluded — it records requirements/evidence, not a decision. PR #78's gRPC transport spec is not onmain, so it's out of scope here.How it was produced
The specs total ~20k lines. Rather than distilling them in one pass, the decisions were extracted per-spec against the ADR template, then verified as a set: all 23 present, every template section populated, all
../specs/links and index links resolve, statuses cross-checked against the registry, and titles normalized to sentence case.Closes the ADR-backfill follow-up to #79.
Assisted-By: Claude Code