docs(design): where the control's application for round 3's new rows comes from - #1852
Merged
Merged
Conversation
…comes from The first pinned application has no sign-in or customers, so the security and data-protection rows cannot move on it. Design 5.7 now says their trees are built from one uncounted calibration trial on the extended spec, and why the reference implementation cannot serve instead; 5.8 and the decisions table point to it. Part of #1767. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
braboj
added
P2
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.
Part of #1767.
The owner's 2026-09-24 decision that the security and data-protection rows' control trees are built from one uncounted calibration trial was recorded only as a comment on #1767. This puts it in the design:
No CHANGELOG entry: the benchmark design is this repository's own, and no consuming project can observe it.
Checks run: smoke 33/33; conformance 0 failed, its three readings read (one file changed, no test changed, no release in progress).
🤖 Generated with Claude Code