186. A pull request's required verdict is the feedback lane, a gate whose inputs did not change is reused as inputs_unchanged, and the proof lane judges the combined top before it lands
Context
Owner orders of 10-08, 10-10 (under 5 min) and 10-11. One validate serves three time horizons: a 10-12 min structure job, four shards of 94-148 min, and a 39-min ui-audit (c228#3, dated). ADR 0041 keeps proven and inputs_unchanged as two states. ADR 0167 lands work in combined tops.
Decision
Each gate declares a lane. The required pull-request verdict needs every feedback-lane gate green and every other selected gate either run or reused as inputs_unchanged: a recorded passing result whose inputs, toolchain and meaning are byte-identical. The proof lane (full suite, full browser sweep, macOS, coverage, installer) is required on the combined top before landing and on release. Unknown impact selects everything. The target is 300 s p95 from validation start, queue time apart.
Alternatives rejected
- More runners, timeouts or shards first (c228#3)
- Moving required validation to nightly or making it non-blocking (c195#2)
- Recomputing every proof on every pull request (c228#3)
- Running every gate for every intent (c130#3)
Consequences
I2348 and I2350 become the implementation. The landing seat's combined-top run carries the proof. A proof-lane red blocks the next landing (rule project.never-reported-is-not-green applies to every skipped gate's proof).
Sources
Promoted on 2026-10-18 from the owner's ChatGPT project (workspace chatgpt-majordomus, issue I3100). The owner has not accepted it; it is proposed for the owner's decision.
chatgpt-majordomus:c130#3chatgpt-majordomus:c228#3