docs(scaling): measured perf baselines across corpus profiles - #35
Merged
Conversation
Three measured data points (sparse production app, small subproject, dense synthetic corpus) showing the deterministic gate flat at ~1-2s across opposite profiles, with the synthetic corpus described precisely enough to regenerate. Re-record the two scaling.md-scoped verdicts. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XUFtq5xDd1rvWbW6Vqu5Ws
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
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.
Adds a Measured baselines section to
docs/scaling.md: wall-clock for the full deterministic gate on three corpus profiles — a sparse-specced ~600k-line production application (~1.4s), a 40k-line subproject (~1.0s), and a reproducible dense synthetic corpus with 3,000 requirements across 2,000 annotated test files (~1.7–2.0s). The spread is the point: spec/annotation volume, not repository size, is what adopters are budgeting, and all three sit well inside the enforced sub-5s perf requirement. The synthetic corpus is described precisely enough to regenerate, and the numbers are version/date-stamped with a re-measure caveat.Editing
docs/scaling.mdinvalidated its two review-scoped verdicts (REQ-008.2.1, REQ-008.2.2); fresh-context re-reviews passed and the re-recorded verdicts are in this diff.🤖 Generated with Claude Code
https://claude.ai/code/session_01XUFtq5xDd1rvWbW6Vqu5Ws