docs(readme): submission perf/claim honesty hygiene (claim-tightening only)#19
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR tightens and clarifies the README’s performance/scale claims by explicitly labeling benchmark figures as prior, software-only measurements and by separating demonstrated benchmark scope from estimate/roadmap statements, with pointers to the in-tree claim boundary and evidence packet.
Changes:
- Rewords the “Performance Snapshot” intro to emphasize point-in-time, re-run-on-submission-commit requirements and the lack of a custom Cargo
[profile.bench]. - Updates the “full tick” interpretation to avoid implying end-to-end, sensor/RF/platform I/O validation.
- Adds explicit “Scale (estimate / roadmap, not demonstrated)” language and links to the canonical claim boundary and evidence packet.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…ive bound Wave-2 A2 (STRIX perf/claim honesty hygiene) under DIANA D0 claim-freeze. DOCS-ONLY, claim-TIGHTENING. Submission-facing README only. - Performance Snapshot: mark numbers as prior-measured software results with reproduction command (`cargo bench`); add explicit "re-run on the exact submission commit" marker. Use neutral "Criterion benchmark profile" framing (no custom [profile.bench] verified in-repo) instead of optimized-vs-unoptimized assertion, to avoid reintroducing a prior honesty-round mismatch. - Tighten the 1.15 ms/20-drone prose: drop "comfortably fits ... significant headroom"; state it is a software-only figure with no sensor/RF/platform-I/O budget, to be re-confirmed. - Surface the ~400-500 single-node ceiling as an AUDIT-DERIVED ESTIMATE and 2000+ as a roadmap target, NEVER demonstrated, where scale is discussed. Cited to the in-tree canonical claim map (CAPABILITY_BOUNDARY.md) and EVIDENCE_PACKET.md item 7. The audit file (docs/audit-2026-03-29.md) is gitignored and not in the submission tree, so it is not linked. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
59dc64b to
f10b1e2
Compare
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.
Documentation-only claim-tightening for submission-facing README (Wave-2 A2). No source/capability code. ADVOCATE diff-gate PASS (dafc164d1119); CONDUCTOR GO (4504bed10454).
Citations point to in-tree Project_Docs/CAPABILITY_BOUNDARY.md + EVIDENCE_PACKET.md. press-releases/ untouched. Rebased onto current origin/main 140583d (A1 demo artifacts preserved).