Skip to content

docs(adr-001): BENCHMARK.md — phase-2 SubLinear numbers + class catalog - #36

Merged
ruvnet merged 1 commit into
mainfrom
adr/benchmark-sota-polish
May 19, 2026
Merged

ruvnet merged 1 commit into
mainfrom
adr/benchmark-sota-polish

Conversation

@ruvnet

@ruvnet ruvnet commented May 19, 2026

Copy link
Copy Markdown
Owner

Summary

Closes the last "fully SOTA" gap from the ADR-001 status preamble. BENCHMARK.md was stuck at the Linear-only baseline (NeumannSolver / OptimizedConjugateGradientSolver) and didn't reflect the change-driven SubLinear paths shipped in PRs #26–#35.

Changes

  1. Change-driven solve paths — Linear vs SubLinear. Numbers from PR bench(adr-001 #2/#6): empirical SubLinear delta-solve comparison #31's `delta_solve` criterion group: cold_full / warm_full / sparse_closure across n = 64, 256, 1024. Demonstrates the architectural property that `sparse_closure` stays roughly constant while the Linear paths grow with n.

  2. Event-driven anomaly example numbers (PRs docs(adr-001): event-driven anomaly example using SubLinear primitives #33, docs(adr-001): wire coherence-gated skip into event-driven example #35): baseline 88 µs Linear, gate `<1 µs` `O(|δ|)`, per-event ~2-3 ms SubLinear.

  3. Complexity-class catalog enumerating every phase-2 primitive with its declared class, plus the MCP enforcement / surfacing surface.

ADR-001 SOTA status

Item Status
All 6 roadmap items SubLinear-or-stronger end-to-end ✅
Phase-2 MCP budget enforcement on solve handlers ✅
Wire-queryable catalog via `estimateComplexityClass` ✅
Empirical SubLinear bench receipt ✅
README complexity-class language ✅
BENCHMARK.md complexity-class language ✅ (this PR)
Pi hwmon J/solve backend hardware-dependent — needs Pi runner

Test plan

  • Markdown renders correctly in GitHub preview
  • Full CI (docs-only, no code touched)

🤖 Generated with claude-flow

Closes the last "fully SOTA" gap from the ADR-001 status preamble.
The BENCHMARK.md sections were stuck at the Linear-only baseline
(NeumannSolver / OptimizedConjugateGradientSolver) and didn't reflect
the change-driven SubLinear paths shipped in PRs #26–#35.

Adds three sections:

1. Change-driven solve paths — Linear vs SubLinear. Numbers from the
   delta_solve criterion group (PR #31): cold_full / warm_full /
   sparse_closure across n = 64, 256, 1024. Demonstrates the
   architectural property that sparse_closure stays roughly constant
   while the Linear paths grow with n.

2. Event-driven anomaly example numbers (PRs #33, #35): baseline
   88 µs Linear, gate <1 µs O(|δ|), per-event ~2-3 ms SubLinear.

3. Complexity-class catalog enumerating every phase-2 primitive with
   its declared class, plus the MCP enforcement / surfacing surface.

After this PR, README.md and BENCHMARK.md both reflect the ADR's
SubLinear delivery; the only remaining "fully SOTA" gap is the Pi
hwmon J/solve backend (hardware-dependent, needs a Pi runner).

Co-Authored-By: claude-flow <ruv@ruv.net>
@ruvnet
ruvnet merged commit 2965808 into main May 19, 2026
11 of 12 checks passed
@ruvnet
ruvnet deleted the adr/benchmark-sota-polish branch May 19, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant