HuiJun · Oct 13, 2026 · Oct 9, 2026 · Oct 9, 2026 · Oct 9, 2026 · Oct 12, 2026
diff --git a/changes/unreleased/perf-0.10.0-record.added.md b/changes/unreleased/perf-0.10.0-record.added.md
@@ -0,0 +1 @@
+- **The release-gate performance record of 0.10.0 against 0.9.2.** `docs/project/performance-release-0.10.0-vs-0.9.2.md` measures the `v0.10.0` tag against the `v0.9.2` tag: every benchmark on both revisions under `benchstat`, the rows in doubt re-run interleaved, the stress constellation, and whole-binary validation, start-up and size, with a column for the release merge before the state-machine and inherited-step work where that work moved a row. Nothing in it blocks the release. Loading is 15–18% more allocations per element on connector-dense models (`sysml -validate` +14–15%), executing a step +40–66%, lowering an action chain twice the bytes for the inherited steps it now carries (linear in the chain), checks with arguments 1 016 → 1 440 B each, workspace edits beside a large document 3.0 times the bytes, the import-ambiguity warning firing 134 times on the Annex A vehicle example, and the exact-numeric calcs, each with its cause named; the fleet's hydration is 19–33% fewer allocations and the interpreted `Fib(25)` 8% faster.
diff --git a/docs/internals/performance.md b/docs/internals/performance.md
@@ -5,7 +5,7 @@ say about where the remaining cost is. Figures below were taken on an
 `Intel Xeon Platinum 8559C`, Go 1.25, `GOMAXPROCS=8`; treat them as
 ratios rather than absolutes. Each release is measured against the one before it
 in a record under `docs/project/`; the latest is
-[release 0.9.1 against release 0.9.0](../project/performance-release-0.9.1-vs-0.9.0.md).
+[release 0.10.0 against release 0.9.2](../project/performance-release-0.10.0-vs-0.9.2.md).
 How far one realistic model scales — a satellite constellation with every
 spacecraft modeled to its components, from 2 to 12 800 satellites — and where
 validation, satisfaction checking and editing each stop being practical is in

diff --git a/docs/project/README.md b/docs/project/README.md
@@ -90,9 +90,10 @@ within these records and means nothing outside this repository.
 - **[StateMachines library](statemachines-library.md)** — pseudostates as bundled
   `SemanticMetadata`, so a state machine's `choice`, `junction` and history pseudostates
   spell standard, conforming SysML v2
-- **[Performance: 0.9.2 against 0.9.1](performance-release-0.9.2-vs-0.9.1.md)** — the release-gate
-  measurement of the 0.9.2 patch line against 0.9.1: every benchmark on both revisions, the rows in
-  doubt re-run interleaved, and whole-binary scaling; the
+- **[Performance: 0.10.0 against 0.9.2](performance-release-0.10.0-vs-0.9.2.md)** — the release-gate
+  measurement of 0.10.0 against 0.9.2: every benchmark on both revisions, the rows in doubt re-run
+  interleaved, whole-binary scaling, and each confirmed regression with the change responsible; the
+  [0.9.2 against 0.9.1](performance-release-0.9.2-vs-0.9.1.md),
   [0.9.1 against 0.9.0](performance-release-0.9.1-vs-0.9.0.md),
   [0.8.0 against 0.7.0](performance-release-0.8-vs-0.7.0.md),
   [0.6 against 0.4.2](performance-release-0.6-vs-0.4.2.md) and
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		- The release-gate performance record of 0.10.0 against 0.9.2. `docs/project/performance-release-0.10.0-vs-0.9.2.md` measures the `v0.10.0` tag against the `v0.9.2` tag: every benchmark on both revisions under `benchstat`, the rows in doubt re-run interleaved, the stress constellation, and whole-binary validation, start-up and size, with a column for the release merge before the state-machine and inherited-step work where that work moved a row. Nothing in it blocks the release. Loading is 15–18% more allocations per element on connector-dense models (`sysml -validate` +14–15%), executing a step +40–66%, lowering an action chain twice the bytes for the inherited steps it now carries (linear in the chain), checks with arguments 1 016 → 1 440 B each, workspace edits beside a large document 3.0 times the bytes, the import-ambiguity warning firing 134 times on the Annex A vehicle example, and the exact-numeric calcs, each with its cause named; the fleet's hydration is 19–33% fewer allocations and the interpreted `Fib(25)` 8% faster.