CI program contract re-anchored: bare minimum computation per required operation; five minutes is the distress ceiling (operator ruling 2026-08-02)

[briansrls]

What

The five-minute-CI program's product-contract sentence presented five minutes as the contract. The operator ruled (2026-08-02, business session): that was a mistake — the vision is on every required operation, perform the bare minimum computation needed to serve it (no redundant computation); five minutes is a "holy crap this is hard / not working well" distress ceiling, scoped by the realization/materialization goals.

This PR re-anchors the contract in all four public carriers of the old sentence, keeping the program's name, node id, sub-lanes, sequence, and staged A/B/C expectations intact:

• dag/gunbc/design_document.dag — the five-minute row's "Product contract:" opening (DESIGN.md regenerated from it in this PR, byte product of generated_artifact_gate.dag main_wet).
• dag/gunbc/roadmap_authority.dag — five_minute_ci_gate_program_note and the five-minute-ci-gate node's headline/boundary. (ROADMAP.md projection carries none of these strings; main_wet confirmed no drift.)
• docs/plans/five-minute-ci-gate-design.md — §Product boundary (hand-authored doc, not in the registered-artifact roster).

Why the reword is safe

dag/test/claim/roadmap_authority_test.dag witness_five_minute_ci_gate_program_chain_is_explicit pins node ids, parent/child edges, and the carrier path — none of the contract strings. Node id five-minute-ci-gate and the doc path are unchanged.

What does NOT change

Sub-lane sequence ((1) #7522 → (2) #7599 → (3) bounded native cutover → (4) #7534 materialization → (5) per-entry assembly → (6) registration), staged expectations, and Stage C keeping 5:00 as its checkpoint bound. The change is the anchor: reaching 5:00 does not complete the program while redundant computation remains on a required path — wall-clock is derived from the no-redundancy invariant, not the definition of done.

Operator ruling, verbatim: "the vision i had was, on every required operation, we perform the bare minimum computation to serve it - i.e. no redundant computation - 5 minutes is a 'holy crap this is hard/not working well' - i would scope that given the realization/materialization goals we have"

🤖 Generated with Claude Code

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[gunbai-bot]

Addressed review 47439: step 6 of the program sequence no longer states the five-minute objective — it now names the bare-minimum-computation contract as the objective, with five minutes retained only as the Stage C distress checkpoint bound (commit after 750a1e0). The other five-minute mentions in the doc are the re-anchored §Product boundary itself and the Stage C checkpoint conditions, which state the demotion explicitly.