You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
id: design: the standard server baseline (from #5685) #5894
Follow-on design ticket from #5685 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.
What this design must settle
The reference environment, workload suite, scales, and baseline versioning that all measurements cite.
Context from the parent
The parent programme fixes the adversarial DoS suite and the per-interface benchmark programme as CI regression gates sharing one load/measurement machinery. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
Decision record expected
Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.
Relations
Parent: #5685. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
Expectation: handed off to the opencode execution lane; the laptop claimant launches the bound opencode session, which drives task 10296 to its terminal state.
Expectation: the bound worker session works task 10296 to a terminal queue state and must not claim another task. It revalidates the issue/PR before acting.
Existing precedent, not completion: current main (00a294ab6a38b23b3a3f855ff5e6102d5aed78c5) has pkgs/id/benches/world_bench.rs, pkgs/id/benches/BASELINES.md, and pkgs/id/benches/baseline.txt. These cover the F11.8 world/in-process benchmarks, a fleet-laptop machine class, and non-blocking >20% CI regression reporting. They do not establish design(id): DoS suite & performance benchmark programme — adversarial CI coverage and per-interface regression gates #5685's standard network-server baseline across its representative identity, capability, journal, world-sync, and blob-transfer workloads or the per-interface programme. Reuse the existing machine-class, noise, and re-baselining lessons; do not treat that narrower baseline as satisfying this design.
No code change or duplicate follow-up issue/task is warranted by this triage. The issue remains open for its own design decision record; implementation timing remains separate, as the issue body says.
Activity
developing-today commentedon Nov 5, 2026
CODE-1577
developing-today commentedon Nov 5, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 5, 2026
🤖 Agent note · state: handed off
dezren39 commentedon Nov 5, 2026
Agent note - handed off
ses_e5e5390ebb5ffdfS0GRsvVlGlgdezren39 commentedon Nov 5, 2026
Triage findings (verified against current GitHub state and current
main, 2026-11-05)main(00a294ab6a38b23b3a3f855ff5e6102d5aed78c5) haspkgs/id/benches/world_bench.rs,pkgs/id/benches/BASELINES.md, andpkgs/id/benches/baseline.txt. These cover the F11.8 world/in-process benchmarks, a fleet-laptop machine class, and non-blocking >20% CI regression reporting. They do not establish design(id): DoS suite & performance benchmark programme — adversarial CI coverage and per-interface regression gates #5685's standard network-server baseline across its representative identity, capability, journal, world-sync, and blob-transfer workloads or the per-interface programme. Reuse the existing machine-class, noise, and re-baselining lessons; do not treat that narrower baseline as satisfying this design.No code change or duplicate follow-up issue/task is warranted by this triage. The issue remains open for its own design decision record; implementation timing remains separate, as the issue body says.