Repository navigation
roadmap reflection + analysis - #5467
Merged
Merged
Conversation
…complexity) Generalizes DESIGN §5's wall/lens/undecidable trichotomy into a methodology: partition any modeling discipline's instances into ① wall (decidable+ constructive) / ② lens-residue (decidable, presentable iff the fix is determined not searched) / ③ undecidable-review, BEFORE gating. Mis-pricing is the §5 'never'-trap (③ as ①) or §6 coverage-by-illusion (①/② left in ③). Anemic-modeling (round-trip homomorphism ① ↔ leaf-decomposition ③) and complexity (budget-dominance ① ↔ optimality/Rice ③) are the first two instances. Short ROADMAP line under §0-meta + the plan doc. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…d rewrite vs surfaced ceil/floor choice The division rows of the op→op_T table don't auto-rewrite: byte_size(count÷n) hid whether to ceil (per-shard demand) or floor (fit count) — a §5 fail-closed decision, not just redundancy. The lens presents both + the demand-ceils/width-floors rule and forces author intent. Sharpens the §2 presentability law (single rewrite vs surfaced choice) and the §3 anemic ② cell. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…tween lenses Operator observation: anemic-modeling, complexity, and manual-wrapping share a shape — each names a 'preferred' (§1-minimal) form and flags deviation as a displaced cost. The lenses are §1 projected onto its three time-costs (cost/safety/complexity). A lens is the schema ⟨preferred form · deviation witness · displaced §1-cost · frontier location · drag fix⟩; the frontier is its 4th field. Payoff: adding a lens = filling the schema, and two lenses on one ⟨axis, preferred form⟩ are a meta-fork (§3 on the lens corpus). Also folds quick-ant's measure refinement: the (2)/(3) operation-signature split (split- into-k vs how-many-fit = different return types) walls the dimensional conflation as a TYPE error (① not ②); the residual ② is the 3-way rounding choice (demand ceils, capacity/fit floor). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jun 21, 2026
* ROADMAP: terse pass — every row to one scannable line + pointer (no dual-rep) Operator reads the roadmap constantly and wants a quick what/where scan. Collapsed every multi-line, multi-clause bullet (some ~900 chars) into one line = short what + status + PR/plan-doc pointer; all density relocated to the already-linked plan docs (the roadmap's own no-dual-representation rule). Longest line now <200 chars (was ~900); no bullet spans multiple rendered lines. Preserved exactly: every checkbox + its state (19 [x] / 61 [ ]), the dependency indentation, all §-anchors, PR-number anchors, and plan-doc pointers. Verified item-for-item against origin/main (incl. #5462/#5463/#5467 content: trimmed CI-fabric line, the §1 selection-vs- scheduling reframe, the §0 expressibility-frontier line). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * ROADMAP terse pass: restore the 5 owner attribution tags (bright-stag gatekeeper fix) Owner review (bright-stag-194, ROADMAP owner): the terse pass dropped 5 owner attributions (quick-ant-298 ×4 on stage0-clone-census / gate-hygiene / nightly-lane / tree-scoped-builtin, fierce-hawk-540 ×1 on stage0) — those are tracking metadata, not density. Restored verbatim (~16 chars each, still scannable). Longest line still <200. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Brian Searls <briansrls@gunb.ai> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jun 21, 2026
…rewrap fork Mint two §3①-wall ops in std/measure.dag (expressibility-frontier #5467), both generic <Q,S> with M=Nat: measure_scale_fraction_floor(m, num, den) -> Measure (Measure×num/den→Measure, capacity floors) measure_fit_count_floor(capacity, each) -> Nat (Measure÷Measure→count, fit floors) Repoint std/realization_width.dag: budget×4/5 and safe_budget÷peak now go through the lifted ops — no unwrap (byte_size_count) → raw arith → rewrap (byte_size) round-trip, no ByteSize→Int projection (byte_size_count_int deleted). The dimension stays attached across the arithmetic; only dimensionless shard counts surface as Nat/Int. Names endorsed by warm-lark-306 as #5467 authority; the _floor suffix reserves a future _ceil sibling for the demand consumer (realization_measurement.dag:84, owned by quick-ant lane) with no fork. Witnesses: dsl/test/claim/measure_lifted_algebra_test.dag pins floor-not-round + zero-divisor fail-closed + <Q,S> genericity; existing realization_width witnesses pass unchanged through the repointed ops. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
6 tasks
briansrls
added a commit
that referenced
this pull request
Jun 21, 2026
…s the measure unwrap→raw-arith→rewrap §3 fork). Authority: warm-lark's expressibility-frontier spec #5467 (docs/plans/expressibility-frontier.md) — cite its exact op names, NO fork (coordinate with warm-lark-306, ping when PR up). (#5470) * WIP: std.measure expressibility slice (§1 spawn-width foundation; dissolves t * std.measure: lifted floor algebra dissolves spawn-width unwrap→arith→rewrap fork Mint two §3①-wall ops in std/measure.dag (expressibility-frontier #5467), both generic <Q,S> with M=Nat: measure_scale_fraction_floor(m, num, den) -> Measure (Measure×num/den→Measure, capacity floors) measure_fit_count_floor(capacity, each) -> Nat (Measure÷Measure→count, fit floors) Repoint std/realization_width.dag: budget×4/5 and safe_budget÷peak now go through the lifted ops — no unwrap (byte_size_count) → raw arith → rewrap (byte_size) round-trip, no ByteSize→Int projection (byte_size_count_int deleted). The dimension stays attached across the arithmetic; only dimensionless shard counts surface as Nat/Int. Names endorsed by warm-lark-306 as #5467 authority; the _floor suffix reserves a future _ceil sibling for the demand consumer (realization_measurement.dag:84, owned by quick-ant lane) with no fork. Witnesses: dsl/test/claim/measure_lifted_algebra_test.dag pins floor-not-round + zero-divisor fail-closed + <Q,S> genericity; existing realization_width witnesses pass unchanged through the repointed ops. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * measure: explicit M=Nat dissolution trigger + i64 overflow note (review #5470) Address quick-ant review: mark the M=Nat specialization with a §6 dissolution trigger (widen to <M> where M:CommutativeSemiring when where-clause syntax lands; deferred on the algebra-inhabitance substrate gap, NOT silent debt), and document Nat=i64 machine-width with the spawn-width overflow headroom (~8 orders below the ceiling); a general checked-Nat guard belongs at the numeric-tower layer, not forked per-op. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Brian Searls <briansrls@gunb.ai> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jun 21, 2026
…n-width) #5470 landed the FLOOR family (measure_scale_fraction_floor / measure_fit_count_floor) and explicitly parked the demand-CEIL op — "no consumer demands it" (DESIGN §6: no carrier ahead of demand). The consumer now exists: std.realization_measurement.concurrent_memory_ peak_per_share derives a per-share memory peak (whole VmHWM ÷ concurrency) that feeds the spawn-width fold. It was doing a raw unwrap→divide→re-ground round-trip (§3 ① fork) AND flooring (§5 fail-OPEN): an under-estimated per-share demand makes ⌊budget÷peak⌋ too high ⇒ the width fold over-fits ⇒ OOM. - measure.dag: mint measure_scale_fraction_ceil<Q,S> — the SAME Measure×num/den→Measure shape as the capacity floor, OPPOSITE rounding (ceil via (a+den-1)/den), and OPPOSITE fail-closed direction (zero den → the un-divided whole, the pessimistic demand, not 0). Update the three-rounding-cases comment: all three are now minted, each by a demanding consumer. - realization_measurement.dag: migrate concurrent_memory_peak_per_share to the lifted ceil op — dimension stays attached (no round-trip), demand rounds UP. Committed per-share value unchanged (8.4e9 ÷ 4 is exact; ceil only bites on a remainder). Witness gains an indivisible case (10÷4 → 3, not 2) that goes RED on a floor impl. - measure_lifted_algebra_test.dag: 5 ceil witnesses — the money-pair discriminator (same inputs: floor→3, ceil→4), remainder-to-one, opposite zero-den fail-closed, <Q,S> genericity. Authority: warm-lark's expressibility-frontier spec #5467 (§3 ② demand ceils). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jun 21, 2026
…≠floor money-pair after #5470 landed the FLOOR family). Builds DIRECTLY on merged #5470 (measure.dag now has measure_scale_fraction_floor + measure_fit_count_floor). Authority: warm-lark's #5467 (docs/plans/expressibility-frontier. (#5478) * WIP: std.measure demand-CEIL follow-up (§1 spawn-width; completes the ceil≠fl * std.measure demand-CEIL: completes the ceil≠floor money-pair (§1 spawn-width) #5470 landed the FLOOR family (measure_scale_fraction_floor / measure_fit_count_floor) and explicitly parked the demand-CEIL op — "no consumer demands it" (DESIGN §6: no carrier ahead of demand). The consumer now exists: std.realization_measurement.concurrent_memory_ peak_per_share derives a per-share memory peak (whole VmHWM ÷ concurrency) that feeds the spawn-width fold. It was doing a raw unwrap→divide→re-ground round-trip (§3 ① fork) AND flooring (§5 fail-OPEN): an under-estimated per-share demand makes ⌊budget÷peak⌋ too high ⇒ the width fold over-fits ⇒ OOM. - measure.dag: mint measure_scale_fraction_ceil<Q,S> — the SAME Measure×num/den→Measure shape as the capacity floor, OPPOSITE rounding (ceil via (a+den-1)/den), and OPPOSITE fail-closed direction (zero den → the un-divided whole, the pessimistic demand, not 0). Update the three-rounding-cases comment: all three are now minted, each by a demanding consumer. - realization_measurement.dag: migrate concurrent_memory_peak_per_share to the lifted ceil op — dimension stays attached (no round-trip), demand rounds UP. Committed per-share value unchanged (8.4e9 ÷ 4 is exact; ceil only bites on a remainder). Witness gains an indivisible case (10÷4 → 3, not 2) that goes RED on a floor impl. - measure_lifted_algebra_test.dag: 5 ceil witnesses — the money-pair discriminator (same inputs: floor→3, ceil→4), remainder-to-one, opposite zero-den fail-closed, <Q,S> genericity. Authority: warm-lark's expressibility-frontier spec #5467 (§3 ② demand ceils). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Brian Searls <briansrls@gunb.ai> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Auto-opened by session-dashboard for session
warm-lark-306.Pushing to
doc/expressibility-frontieradvances this PR.Worker attestation
Before flipping this PR to ready for review, confirm each item:
npm test,cargo test) and the result.Closes #Ndirective.Summary
TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.
Test plan