From f10b1e2956b597bf51c1d1f14b6aaa12619740ba Mon Sep 17 00:00:00 2001
From: RMANOV <96174405+RMANOV@users.noreply.github.com>
Date: Mon, 15 Jun 2026 23:26:03 +0300
Subject: [PATCH] =?UTF-8?q?docs(a2):=20perf/scale=20claim=20honesty=20in?=
 =?UTF-8?q?=20README=20=E2=80=94=20provenance=20+=20conservative=20bound?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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>
---
 README.md | 26 ++++++++++++++++++++++++--
 1 file changed, 24 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 254ecce..d8fa66f 100644
--- a/README.md
+++ b/README.md
@@ -57,7 +57,12 @@ Public releases should be traceable to the official upstream and maintainer rele
 
 ## Performance Snapshot
 
-All measurements below are from Criterion benchmarks on a single core, using the default optimized `bench` profile (opt-level 3; no custom `[profile.bench]`, so not a debug/test profile).
+All measurements below are **prior-measured** software results from the
+Criterion benchmark profile on a single core, reproduced with `cargo bench`
+(the repository defines no custom `[profile.bench]`, so the standard Criterion
+`bench` profile applies). They are point-in-time figures, not final live facts,
+and must be **re-run on the exact submission commit** before being quoted as
+current.
 
 | Benchmark | Configuration | Time |
 |-----------|--------------|------|
@@ -71,7 +76,24 @@ All measurements below are from Criterion benchmarks on a single core, using the
 | Full swarm tick | 10 drones | 580 us |
 | Full swarm tick | 20 drones | 1.15 ms |
 
-The full tick benchmark covers estimation, regime updates, assignment, coordination, safety clamps, and trace capture. At 1.15 ms per tick for 20 drones, the system comfortably fits inside a 10 Hz orchestration loop with significant headroom for sensor processing and platform I/O.
+The full tick benchmark covers estimation, regime updates, assignment,
+coordination, safety clamps, and trace capture. The prior-measured ~1.15 ms per
+tick for 20 drones fits inside a 10 Hz orchestration loop, but this is a
+software-only benchmark figure to be re-confirmed on the submission commit, not
+a demonstrated end-to-end field result; it carries no sensor, RF, or platform-I/O
+budget.
+
+**Scale (estimate / roadmap, not demonstrated).** The largest full swarm-tick
+benchmark above is 20 drones at ~1.15 ms; the combinatorial auction benchmark
+reaches 50 drones, and the `swarm_tick` benchmark source exercises up to 100
+drones. A practical single-node ceiling of **~400–500 agents** at 10 Hz is an
+**audit-derived estimate**, and **2000+** agents is a **forward roadmap target**
+— neither is a demonstrated or benchmark-backed capability. These bounds are
+governed by the canonical claim map in
+[Project_Docs/CAPABILITY_BOUNDARY.md](Project_Docs/CAPABILITY_BOUNDARY.md) and
+detailed in
+[Project_Docs/provenance/validation/EVIDENCE_PACKET.md](Project_Docs/provenance/validation/EVIDENCE_PACKET.md)
+(item 7). They must never be stated as fact.
 
 ## Quick Start