Skip to content

DEMAND-1: apply the demand-minimization paragraph to DESIGN §2 and consume the plan - #9792

Merged
gunbai-bot[bot] merged 5 commits into
mainfrom
demand1/apply-section2
Aug 31, 2026
Merged

gunbai-bot[bot] merged 5 commits into
mainfrom
demand1/apply-section2

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Aug 31, 2026 •

Copy link
Copy Markdown
Contributor

DEMAND-1, the terminal consumer of the merged DEMAND-0 plan (#9790), executed after its declared prerequisites landed on main: #9791 (materialization decision-order repair) and #9822 (frontier authority repair — the ledger board now renders honestly from the repaired producer).

The final transaction is exactly the three authorized paths:

  • dag/gunbc/design_document.dag — one row added to section_2_blocks, immediately after the horizontal/deep list and before the "net concepts must not grow" test: the approved demand-minimization paragraph, applied verbatim from the merged plan blob (verified by string equality at splice time).
  • DESIGN.md — the corresponding two-line generated addition.
  • docs/plans/demand-minimization-design-placement.md — deleted, consumed by this PR per its own dissolution condition.

Terminal receipts at exact head c1c2b6d14556159fa9c83cfd383d88131270ce31, directly parented on main@5637e826fc3fcf530c99ddd48a2d09439646b9e7: fresh-clone srv2 main_wet exits 0 with a fully empty git status over the whole committed-artifact population (the tree is a generated fixed point of an honest authority), and the same run's ledger readback shows typeck 233 remaining / borrowck not yet reached.

Execution-provenance refresh (2026-08-31, third cycle). Generated fixed-point evidence is bound to both the generator mechanism and its authority inputs, so three successive main advances each voided the prior receipt: compiler/runtime changes (cli_run.rs, entry_resolve.rs, v1_compiler_emit_rust.rs, v1_interpreter.rs); then #9828 (compile-frontier census identity moved from emission-order to canonical set identity, new ledger digest, changed witness population); then #9819/#9813/#9829 (emit_rust, cli_run, required_floor_runner, infer/parse/resolve). This head is a merge commit over main@0b4366efb8f4e6f3d2224e94d210fe6500323376, with the approved DEMAND commit byte-unchanged (no rebase, no force-push), and every receipt below was re-derived on it.

  • Contribution unchanged: git diff --stat 0b4366efb8...HEAD is exactly the three authorized paths, +3/-65.
  • Fixed point: full-population main_wet at this exact head, gunbc built from this same tree, tree verified clean before the run: GEN_EXIT=0, 35 committed artifacts written, zero panicked lines in the raw log, git status --porcelain zero lines after.
  • Positive controls, both required by the ruling: the honest phase standing typeck 233 remaining / borrowck not yet reached, and census_identity_digest is a set identity: fold the phase census over a canonical order #9828's canonical census-digest representation Census identity digest (self-host-compile-phase-census-canonical-identity-set-v1): 6daa51e6ebaea2e3.
  • CI on this exact head: run 33428172184, fabric-evidence checked explicitly rather than inferred from the aggregate. No check is carried over from any earlier head.

No §3 paragraph, §6 bullet, recurring-failure-mode row, or shared-root carrier is touched; shared-root activation remains separately scheduled.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QhdaHkmZPoQoeUWz5V2mzF

…nsume the plan

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QhdaHkmZPoQoeUWz5V2mzF
@gunbai-bot
gunbai-bot Bot force-pushed the demand1/apply-section2 branch from b6ebc42 to c1c2b6d Compare August 31, 2026 16:26
@gunbai-bot
gunbai-bot Bot merged commit eced9d2 into main Aug 31, 2026
5 checks passed
@gunbai-bot
gunbai-bot Bot deleted the demand1/apply-section2 branch August 31, 2026 20:14
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.

0 participants