docs: record decision to reject parse-don't-validate seam#29
Merged
Conversation
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.
Records the architecture review's Candidate 3 (type-enforce the validate->emit seam via a typed
CheckedDocumentthat emit consumes) as a rejected decision with a revisit trigger, so future reviews don't re-suggest it.Rationale (in the decision file): the service-key registry (#27) and the complete validation gate (#28) already delivered the practical safety — a direct
emit_scripton a malformed doc now fails cleanly, and emit no longer re-derives shape knowledge. Candidate 3's residual unique benefit (blocking a valid-but-unvalidated dict from reaching emit) is CLI-unreachable and not worth a typed-model rewrite of the just-built registry plus a breaking public API. Revisit if a second emit consumer/output format appears, or the validate-before-emit convention causes a real bug.planning/decisions/2026-07-10-reject-parse-dont-validate.md. Docs-only.🤖 Generated with Claude Code