Repository navigation
docs(fold): ergonomics lane charter — generic-inference keystone + ranked focus - #5545
Merged
Merged
Conversation
…s (generic-inference keystone) Captures the fold-ergonomics lane analysis (two tree-wide sweeps) the ROADMAP ✦ lane named but did not rank: the fold spine is already real (fold_node 69+, bind_outcome 246+, coercion_fold 50+), the two roots are A) realization-side not folded (~120 silent-false Value bridges, the fail-open) and B) weak generic inference (the friction that keeps producing it), and the ranked focus puts the generic-inference fix at #1 (the root with measured fan-out: qualified_name/ParseTable/cached_stage collapse; prereq for the realization grounding). Mirrors the #5533 CI-map pattern (consolidating charter + ROADMAP pointer). ROADMAP ✦ Ergonomics LANE: de-"proposed" → placed (lead lane, upstream of §0, no renumber); charter pointer added (orphan-doc gate); generic-inference elevated from buried fix-half item to the fix keystone (#1). Density stays in the charter (lines-short rule). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Jun 22, 2026
…ers(List<Pointer>) + lead_lanes machinery
Fixes the stale-base lossiness (warm-lark/bright-stag): re-transcribe §1-§8 from
current main (245 ln) with ZERO content loss, applying only C1-C5 + benign rewrap.
Model:
- PlanDocCarrier -> List<Pointer{label,path}> (dissolves NoCarrier/PlanDoc 2-state;
label is data, varies per ROADMAP; multi-pointer items supported)
- RoadmapDocument gains lead_lanes: List<RoadmapSection>, rendered with a
projection-derived ✦ sigil (sigil-from-position); ✦ Ergonomics LANE content HELD
pending #5545 merge (transcribe post-#5545 bytes natively)
- emit no longer force-bolds derivable titles; bold is authored in the title string
(the §5 fence, consistent with AuthoredLine) -> matches main's per-item bolding
Restored: §1 (was entirely stale: title reverted, host-op band G1-G5, shared
abstractions), §2 P1/P2/M4.1/M5/P3 cache subtree, §3 subject-producer/gates-whole,
§4 anemia-lens, §5 adjacent-lane + de-fork children + emitted-crate subtree, §6
Medium<A><->Medium<B>, preamble clauses, §0 dropped descriptions + cardinality item
+ all dropped pointers (incl gate-hygiene merge-freshness + DESIGN §6 + axiom scope).
All 5 roadmap witnesses green by execution; gate drift-clean + red-receipt teeth.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Jun 22, 2026
…ired-facts pointer - ✦ Ergonomics lane authored into lead_lanes (renders upstream of §0 per both owners' lead-lane ruling; ✦ sigil from projection position). Content byte-faithful to post-#5545 main modulo accepted benign-rewraps (line-wrap, blank-after-heading, uniform-blank-after-sub-group-label). - §5 "dissolve seed hand-patches": fold in the required-facts pointer + emit_rust hand-sync caveat text that a recent merge added to main (was dropped on regen). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jun 22, 2026
…n flagship capstone) (#5535) * WIP: Continue the ROADMAP inversion lane - successor to archived quiet-hawk-4 * WIP: Continue the ROADMAP inversion lane - successor to archived quiet-hawk-4 * wip: roadmap gate floor wiring (gate_is_heavy_resolve arm) * roadmap gate: comply with #5534 comment-ban (strip gunbc/tools comments; boundary lives in gate reason-string + witness) * WIP: Continue the ROADMAP inversion lane - successor to archived quiet-hawk-4 * WIP: Continue the ROADMAP inversion lane - successor to archived quiet-hawk-4 * WIP: Continue the ROADMAP inversion lane - successor to archived quiet-hawk-4 * ROADMAP authority: re-transcribe faithfully from current main + carriers(List<Pointer>) + lead_lanes machinery Fixes the stale-base lossiness (warm-lark/bright-stag): re-transcribe §1-§8 from current main (245 ln) with ZERO content loss, applying only C1-C5 + benign rewrap. Model: - PlanDocCarrier -> List<Pointer{label,path}> (dissolves NoCarrier/PlanDoc 2-state; label is data, varies per ROADMAP; multi-pointer items supported) - RoadmapDocument gains lead_lanes: List<RoadmapSection>, rendered with a projection-derived ✦ sigil (sigil-from-position); ✦ Ergonomics LANE content HELD pending #5545 merge (transcribe post-#5545 bytes natively) - emit no longer force-bolds derivable titles; bold is authored in the title string (the §5 fence, consistent with AuthoredLine) -> matches main's per-item bolding Restored: §1 (was entirely stale: title reverted, host-op band G1-G5, shared abstractions), §2 P1/P2/M4.1/M5/P3 cache subtree, §3 subject-producer/gates-whole, §4 anemia-lens, §5 adjacent-lane + de-fork children + emitted-crate subtree, §6 Medium<A><->Medium<B>, preamble clauses, §0 dropped descriptions + cardinality item + all dropped pointers (incl gate-hygiene merge-freshness + DESIGN §6 + axiom scope). All 5 roadmap witnesses green by execution; gate drift-clean + red-receipt teeth. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * WIP: Continue the ROADMAP inversion lane - successor to archived quiet-hawk-4 * revert §2 to flat authored (temp green) — awaiting owner call on plain-bullet approach bright-stag+warm-lark want byte-exact plain bullets for the 2 compact lines (hermetic, blockers). The SectionGroup restructure (real nested checkboxes) was withdrawn (7th delta). But byte-exact mixed task/plain lists need a std.markdown heterogeneous-list capability — out of brief, escalating to owners. Holding the 2 lines at flat-authored (green) until they rule std-change vs roadmap-layer-plain. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * §6 roadmap-inversion: option (B) — plain-bullet RoadmapItem (no phantom checkbox) The two compact §2 bullets (hermetic, blockers) carry inline [x]/[ ] glyphs that a TaskListBlock would falsely wrap in a leading checkbox — a §5 mixed-state fail-open. Add a PlainLine RoadmapItem variant + roadmap-layer run-partitioning (consecutive task/plain nodes → adjacent TaskListBlock/UnorderedListBlock) so they render as faithful plain bullets. No std.markdown touch (the heterogeneous-list unification is a separate parked defect per owner ruling). hermetic (nested under P2) is byte-exact (md_item joins nested blocks with "\n"); blockers (top-level) gets one structural blank line (block_separator "\n\n") — classified [benign-rewrap], the std-heterogeneous-list fix deferred. 5 witnesses green; gate drift-clean + red-receipt intact. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: reclassify the 2 compact bullets as option (B) implemented Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * §6 roadmap-inversion: transcribe ✦ Ergonomics lane natively + §5 required-facts pointer - ✦ Ergonomics lane authored into lead_lanes (renders upstream of §0 per both owners' lead-lane ruling; ✦ sigil from projection position). Content byte-faithful to post-#5545 main modulo accepted benign-rewraps (line-wrap, blank-after-heading, uniform-blank-after-sub-group-label). - §5 "dissolve seed hand-patches": fold in the required-facts pointer + emit_rust hand-sync caveat text that a recent merge added to main (was dropped on regen). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: ✦ lane transcribed natively — update completeness diff (placement + §5 catch) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * §6 roadmap-inversion: remove the review artifact — capstone finalized Both owners signed (warm-lark gate-integrity + independent faithfulness verify; bright-stag content+placement). The completeness-diff was a review aid; the authority + gate are the durable record. ROADMAP.md is now a CI-enforced projection of gunbc.roadmap_authority — drift unwritable via RoadmapGate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * §6 roadmap-inversion: fold #5560 content into authority (re-home before #5535) #5560 hand-edited ROADMAP.md on main (FreeMonoid grounding ruling + keystone/CI milestones) with intent to "re-home into .dag after #5535" — but it landed BEFORE #5535, so transcribe its content into the authority now or the generated ROADMAP.md would drop/drift it (zero-content-loss). Folded all 5 edits: - §0 rust-gate: run-all-at-nextest-speed CI-green line (#5427) - ✦ Milestones + generic-inference fix: #5552 keystone green - §1 G2: + cross-host placement (proud-tern-439) - §5 de-fork restructure: grounding cluster UNPARKED → Root A / Root B / v1-coupled All 8 #5560 phrases present + matching; 2 superseded items removed; whole-doc audit zero missing refs/paths; 5 witnesses green; gate drift-clean + red-receipt intact. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Brian Searls <briansearls1@gmail.com> Co-authored-by: Claude Opus 4.8 (1M context) <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.
Answers "did the fold-ergonomics analysis get into the fold lane?" — it partially had: the ✦ Ergonomics LANE named the generic-inference item but (1) buried it as the last fix-half bullet rather than ranking it the keystone, (2) had no charter doc capturing the analysis, (3) was still tagged "(proposed; bright-stag to number/place)". This fixes all three.
New:
docs/plans/fold-ergonomics.md— the charter, mirroring the #5533 CI-map pattern (consolidating doc + ROADMAP pointer):fold_node69+ sites/7 stages,bind_outcome246+,coercion_fold50+ (the model-side coercion fold is built), Mgr-§1: dissolve 06_translate.dag onto fold_node (keystone cleanup, dep-graph-2026-06-11 §1) #4699 / compile front-end as a typed then_outcome stage fold (+ live cached_stage seam); measure.dag single-authority; cardinality-refinement MVP #5512 / Numeric-tower grounding: ground Nat construction-side so native form == modeled form (§0) #5428 /merge_envs.falseValuebridges (the fail-open, incl. theValue::Null~131-site split); B) generic inference is weak — the friction that keeps producing residue (FreeMonoid<Symbol>won't instantiate → 55 hand-rolled lines inqualified_name; same root →ParseTable).ROADMAP
✦ Ergonomics LANE: de-"proposed" → placed (lead lane, upstream of §0, no global renumber); charter pointer added (orphan-doc gate); generic-inference elevated to the fix keystone (#1). Lines kept short, density in the charter.Docs-only. Coordinated with warm-lark/merry-deer so the active ROADMAP-inversion (#5535) models the final ✦-lane shape.
🤖 Generated with Claude Code