docs(decisions): keep per-instrument axis, reject framework-adapter inversion#131
Merged
Merged
Conversation
…nversion Records the rejection of architecture-review candidate 3 with its load-bearing reason so future reviews don't re-suggest inverting the instrument x framework matrix. Decision-only; no code change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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.
What
Records a
planning/decisions/entry rejecting architecture-review candidate 3 (invert the instrument × framework matrix to per-framework adapters). Decision-only — no code change.Why
The 2026-06-23 architecture review surfaced candidate 3. Grilling it showed the premise and payoff don't hold:
render_health_check_data(), provider setup, config validation); the per-framework subclasses hold only the genuinely-different binding.The entry carries a Revisit trigger (bindings start converging, or a new framework shares an existing one's attach mechanism) so the decision is reopened only when the calculus actually changes — and a future review won't re-suggest it in the meantime.
🤖 Generated with Claude Code