Repository navigation
Materialization ladder: cost-floor roster consulted only after nature and topology establish unavoidable recurrence - #9791
Merged
Conversation
…re and topology establish unavoidable recurrence Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QhdaHkmZPoQoeUWz5V2mzF
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.
The materialization decision-order prerequisite between DEMAND-0 (#9790, merged) and DEMAND-1, per the side-chat exact-head ruling ("No separate plan PR is required … This ruling plus the merged DEMAND-0 plan is the approved specification").
Defect (recorded in
docs/plans/demand-minimization-design-placement.md):group_verdictconsultedcost_floor_exemptimmediately after the nature-conflict check, returning greenAcceptedBelowCostFloorbefore demand nature, topology, or the obligation LCA were inspected — so a roster row could green shared-state authored duplication, an unmodeled world read, and a single undeclared pure demand.Repair (decision-order only; every public vocabulary preserved): the roster check moves out of
group_verdictintogroup_redundant_verdict, after the shared-state (AuthoredDuplication) arm and only on the unavoidable-recurrence branch (non-shared-state LCA: isolation boundary or declared emergence), beforedischarge_verdict. Nature-conflict precedence, fresh-effect exemption, and world-read staleness handling are unchanged and now precede the roster by construction.Executed evidence (srv2, fresh clone of
a6d6c68d4d+ this patch,claim_batch --entry dag/test/claim/materialization_ladder_witness_test.dag --functions <all 32>):cost_floor_row_does_not_excuse_shared_state_duplication,cost_floor_row_does_not_excuse_unmodeled_world_read,cost_floor_row_on_single_pure_demand_is_still_single_recomputeall FAIL — each discriminator refuses on the real acceptance path.cost_floor_row_prices_unavoidable_emergent_recurrencepasses both sides: it is the preservation control that the roster still prices genuinely unavoidable recurrence (the existingbelow_cost_floor_duplication_is_typed_acceptancecell, whose LCA is the isolationwfframe, also stays green).Scope is exactly the two files the ruling names. No DEMAND plan, DESIGN, projection, ledger, or shared-root carrier is touched.
🤖 Generated with Claude Code
https://claude.ai/code/session_01QhdaHkmZPoQoeUWz5V2mzF