Repository navigation
docs(v0.49): ratify approved 59/min acceptance floor, retain 60/min target - #22
Merged
grove merged 1 commit intoOct 22, 2026
Conversation
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.
Record owner-approved S1 throughput floor in v0.49 authoritative plan
The owner explicitly authorized minimum 59 cases/minute, with 60 cases/minute remaining the offered workload and performance target, on 2026-10-22. This documentation-only dependent PR adds a dated, explicit amendment to
plans/v0.49.0.md; it does not silently rewrite historical measurements, change SQL/runtime, production config, the frozen workload, or React/MDM/pg-trickle pins.Only the throughput acceptance decision changes. For 59–<60/min a candidate qualifies that rate condition only when the frozen 60/min failure is the sole raw failure, all 300 admissions / 1,200 sources / 300 cases are exact, zero future receipts, original due-burst p95 <=150s and max <=180s, permissions, supervision, resource budgets and paired-control evidence hold; retain raw benchmark exit 1 and disclose the approved-floor outcome. Below 59 is still a failure, >=60 requires the ordinary clean exit-0 run.
The archived ~59.36/min test at pg-trickle source
2d102645ccc6779c508514ee22b4a55603bdc281now meets the amended numerical floor but is not final-current-source qualification. pg-trickle PR #1213 updates the checker, test boundaries, workflow and performance docs against #1191's feature branch. The approved 10-CPU ARM64 full-current-source test, source/image identities, clone/restore safety, complete operating envelope and React #12 remain independently required.Base: draft React #14 feature
issue/11-explicit-escalation-time. Keep this PR draft until exact head checks pass; merge only into that feature branch, never directly tomain, and do not activate production.