Repository navigation
vacuity lens - #6638
Merged
Merged
vacuity lens#6638
Conversation
…not testing technique Operator generalization (2026-07-14): a vacuous test is a second representation of a fact the code already carries — moves 1:1 with the code (a change-detector, not a check). The discriminator is 'independent referent': behavioral (expected output for a specific input) or external authority = legit; absent (self-count/read-back) = vacuous. Reflexive/shared-authority/literal-restatement collapse to one absent-referent class, decomposed by decidability into wall vs advisory. Census + live instance (coverage_domain_equivalence_test.dag:110; hand-deleted class bf3e33e). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…edDuplication on the authored-fact substrate Operator (2026-07-14): any test duplicating an authority (structural count, model field, datasheet-grounded value) is dual authority (DESIGN 3) — the datasheet carve-out was wrong. Vacuity is not a new law: it is the ladder's plurality primitive generalized from demand-per-computation-identity to authority-per-fact-identity; a hardcoded test value is AuthoredDuplication, fix = rewire to single authority = 5 construction-over-validation. Vacuity is a new detector feeding the existing Materialization verdict, not a forked law. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ms not meanings REQUEST_CHANGES (2026-07-15) accepted on all blocking points: - reachability != cardinality: inert is root-relative reachability (global fixpoint), NOT in-degree count (root=indeg0 healthy, cycle=indeg1 dead, diamond=indeg2 healthy). Share only a typed Count<Relation>; keep ReachVerdict/LadderVerdict/oracle verdicts distinct. Consolidation doc reframed to 'consolidate mechanisms, not meanings' + the corrected invariant/verdict map (adds relational-conformance and algebraic-composition axes the four-axis model dropped). - signal #1 false-positived rung_5 (identical lhs/rhs observed via emit-vs-eval): operand equality is not a wall until the observation/consumer relation is modeled. Vacuity doc rebuilt around VacuityEvidence = ProvenDuplicate | ProvenIndependent | Unknown; only ProvenDuplicate gates, Unknown refuses/advisory (never green), classifier total over all 5 TestClaim variants, with the adversarial falsification suite as the RED controls. - VacuousArm name collision: mint own VacuityEvidence, do not reuse coverage_defect_vacuous_arm. - wrong remedy: AuthoredDuplication->Share makes f(x)==f(x) MORE tautological; vacuity's remedy is independent-oracle/construction/deletion -> a distinct verdict, not LadderVerdict. - self-contradictions fixed: datasheet read-back = ProvenDuplicate vs two independent transcriptions = parallel-authority debt (distinct defect). Next safe step per review: ground TestClaimObservationRelation, land signal #1 only as a consumer-aware candidate census. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
marked this pull request as ready for review
July 15, 2026 05:10
|
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. |
This was referenced Jul 15, 2026
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Jul 15, 2026
…all full-floor PRs) Main's tree (post #6638/#6664) fails generated_artifact_drift_gate_passes on every full floor: the vacuity lane hand-added a 'Sibling family' paragraph to the GENERATED docs/plans/inert-layer-lens.md without updating its generating Plan row (dag/gunbc/plans/inert_layer_lens.dag) — committed != regenerated. Their docs-only PRs merged through the docs-only shortcut, which skipped both the drift gate and the doc-graph wall. 1. Regenerate inert-layer-lens.md (paragraph removed; byte-identical to warm-crab-65's independent main_wet regen on #6658 — same blob 2b36cf2). 2. That hand-edit was ALSO the only doc-graph anchor for the vacuity lane's two design docs; regen alone orphans vacuity-lens-design.md and (via its link chain) lens-consolidation-design.md. Re-anchored with a bind: provenance row in dag/std/materialization_ladder.dag — the file whose AuthoredDuplication verdict the vacuity doc's load-bearing correction is about — migrating to the vacuity lens .dag carrier when it lands. Verified by build_doc_graph_report replication: doc_count=110, orphan_count=0, dangling=0. Follow-up for the vacuity lane: re-add the sibling-family paragraph via the inert_layer_lens Plan row (the authority), not the generated md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 15, 2026
Merged
briansrls
added a commit
that referenced
this pull request
Jul 15, 2026
…fact emit. Vacuity #6638 hand-edited docs/plans/inert-layer-lens.md (a committed PlanArtifact projection from gunbc.plans.inert_layer_lens); batch-4 generated_artifact_drift_gate failed on the 2-line manual insert. Regen removes the prose — sibling-family note belongs in vacuity-lens-design.md, not a second authority on the generated plan file. Co-authored-by: Cursor <cursoragent@cursor.com>
6 tasks
briansrls
added a commit
that referenced
this pull request
Jul 15, 2026
… (the authority) The vacuity lane (#6638/#6664) hand-added a 'Sibling family (§2 redundancy, the other half)' blockquote to the GENERATED docs/plans/inert-layer-lens.md §8 without updating the authoritative dag/gunbc/plans/inert_layer_lens.dag. Per DESIGN §6 (mark on the carrier is the authority), restore this paragraph via the Plan row in the DAG so future regenerations include it. The blockquote connects inertness (0 reach) to its dual (≥2 authorities / redundancy), grounding the vacuity lens as the test-substrate instance of the redundancy family. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jul 15, 2026
Rebased onto main after #6649 (f62330d) landed. That PR resolved the drift by regenerating docs/plans/inert-layer-lens.md from its authority — which DISCARDED the §8 sibling-family note #6638 had hand-added to the generated doc. main went green by losing the content, not by homing it. This PR's purpose therefore changes: it is no longer a main-unblock (main is green), it RESTORES the lost note and puts it in the right home. The authority carries the note; the generated doc is regenerated to match. Both agree, gate green. Verified by execution on the merged head: - authority-only (pre-regen) -> FAIL run_generated_artifact_drift_gate (i.e. merging the prior version of this PR would have RE-RED main) - authority + regenerated doc -> PASS run_generated_artifact_drift_gate - the regen diff is exactly the 2 lines #6649 removed, no other doc churn Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jul 15, 2026
… Plan row (the authority). Context: the vacuity lane (#6638/#6664) hand-added a 'Sibling family (§2 redundancy, the other half)' blockquote to the GENERATED docs/plans/inert-layer-lens.md §8 without updating dag/gunbc/plans/inert_l (#6672) * Restore vacuity sibling-family paragraph to inert_layer_lens Plan row (the authority) The vacuity lane (#6638/#6664) hand-added a 'Sibling family (§2 redundancy, the other half)' blockquote to the GENERATED docs/plans/inert-layer-lens.md §8 without updating the authoritative dag/gunbc/plans/inert_layer_lens.dag. Per DESIGN §6 (mark on the carrier is the authority), restore this paragraph via the Plan row in the DAG so future regenerations include it. The blockquote connects inertness (0 reach) to its dual (≥2 authorities / redundancy), grounding the vacuity lens as the test-substrate instance of the redundancy family. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * Fix: reconcile sibling-family paragraph with inertness definition and vacuity verdict Address REQUEST_CHANGES review feedback (cursor/composer-2.5): 1. Reframe inertness correctly: root-relative reachability (§1 definition), not authority-count / plurality axis. The consolidation design (§25) explicitly corrects this: "reachability is not cardinality." 2. Stop conflating vacuity with AuthoredDuplication. Vacuity has its own oracle-provenance verdict (VacuityEvidence: ProvenDuplicate | ProvenIndependent | Unknown), distinct remedy (independent oracle/construction/deletion, never Share), and sits on a different invariant axis. The vacuity design explicitly rejects the unification (§1.1 & §13). 3. Keep the kin relationship but ground it correctly: inertness and vacuity share the counted-relation mechanism (lens consolidation: "consolidate mechanisms, not meanings"), but verdicts and remedies are distinct. Both flow from §2/§3 redundancy concerns but are opposite endpoints of distinct invariants. Rename section to "Kin families" to reflect multiple distinct invariants, not one plurality axis. Reference lens-consolidation design for the principled distinction between shared mechanism and separate meaning. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> * Regenerate inert-layer-lens.md to match updated Plan authority Sync the generated markdown output with the DAG authority (dag/gunbc/plans/inert_layer_lens.dag:101). This fixes the parallel-representation defect where the hand-edited markdown "Sibling family" text with incorrect semantics was actively disagreeing with the corrected Plan row. The regenerated section 8 now uses the authoritative "Kin families (§2/§3, distinct invariants)" framing: - Inertness as root-relative reachability verdict (not authority count) - Vacuity with distinct VacuityEvidence verdict (not AuthoredDuplication) - Shared mechanism, distinct meanings (per lens-consolidation design) Per DESIGN §6: mark on the carrier is the authority; generated artifacts must match. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> --------- Co-authored-by: Brian Searls <briansrls@gunb.ai> Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jul 15, 2026
…rule, convergence map (#6654) * WIP: map reduce * WIP: map reduce * WIP: map reduce * WIP: map reduce * machine-shape plan: end shape agreed, no-kind rule, convergence map to existing carriers - §2 terminal model pinned (operator rulings 2026-07-15): one locality lattice (lifted to std, converging BOTH existing latency enums), divergence/idle-lane/ crossing laws, Placement dissolution trigger, kind-erasure at the ComputeHost→MachineShape derivation boundary - convergence map: every end-shape element bound to its existing carrier (HardwareThreadCount reused for lane_count; PlacementSupplyRow identified as the degenerate single-domain MachineShape; PTX ThreadHierarchyShape/PtxCost gain their consumer; MemoryKind.UnifiedShared flagged as topology-in-technology) - MemoryLevel.sharing dropped: sharing derives from SharedLevelEdge graph structure (single authority) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * WIP: map reduce * machine-shape plan: address operator request-changes (7 blocking findings) - MachineShape is now a representable graph: DomainId/LevelId identities, explicit edge endpoints, SharedLevelEdge references the owner's level by id (embedding duplicated it), InterconnectLink coproduct holds NetworkAttach (LinkEdge was PcieLink-only while the map claimed NetworkInterface as a fill), terminal Placement = DomainId reference; dangling refs refuse - Phase 3 batching vs signed scheduling authority: conflict acknowledged, now an EXPLICIT supersession proposal (topology = pure fn of declared shape; MeasuredBy banned from topology; schedule_eq generalized to equal-given-equal- declared-inputs) gated on operator sign-off, with a confined fallback - both §5 fallback arms converted to refusals: Priced|PricingRefused{missing} (no term-incomplete Predicted accounts), Placed|PlacementRefused{missing} (no stay-at-current-domain answer) - Quantified<T> restructured: Precision (Exact|Interval) x Evidence (Cited|MeasuredBy{ExecutionReceiptDigest}|DerivedFrom) — evidence-bearing constructors make the authored-literal RED enforceable - locality/latency split into two axes: latency = per-level magnitude with one std class projection (converging ReadLatencyClass + network LatencyClass); locality = graph-derived, domain-relative (no universal total order) - OperandFlow total derivation spelled out: operand_root (fail-closed), hash- authority convergence precondition (v2.std.node.Hash vs ContentHash — the fnv1a64 thread), edge->root mapping for node_keyed_graph_transitive_bytes, OperandFlowRefused rows - AssociativityEvidence subject-bound: {combine, inhabitant, law, receipt}, license requires structural identity with the scheduled combine; keyed-patch witness scoped to mechanism-precedent-only; within-fold expansion scoped kernel-internal (never central Schedule topology) - corrections: PlacementSupplyRow has zero production callers (grep -l overcount); document-level dissolution trigger added (Plan-row registration = part of Phase 1 definition of done) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * de-orphan machine-shape plan doc + correct doc_reachability lying live-tree stamp Two fixes from the docs-enforcement audit (operator-directed): 1. bind: provenance row in accelerator_demo_plan.dag makes docs/plans/machine-shape-orthogonal-scheduling.md doc-graph-reachable (the established hand-authored-design-md convention: accelerator_demo_plan :51, live_read_classification.dag:66). Registration as a gunbc.plan.Plan row stays the md's declared Phase-1 dissolution — registering now would flip the actively-evolving doc into a generated artifact prematurely. Verified by build_doc_graph_report replication: doc_count=107, orphan_count 1->0, dangling 0. 2. doc_reachability_witness_test live_tree_disposition: SubstrateInputsOnly -> ReadsLiveTree. The 2026-07-12 machine stamp (#6479 entry-text batch) was false: every test fn reads the live docs/ tree via doc_graph_* host builtins — the exact classifier blind spot live_tree.dag:5 declares. The false stamp made the orphan wall predict-skippable, which composed with the docs-only floor shortcut into a pre-merge false-green (this PR minted an orphan with green CI). ReadsLiveTree restores the never-skip tooth: the wall now runs on every full floor, including this PR's. This diff leaves the docs-only shortcut class, so this PR runs the full floor with the corrected stamp — the wall itself verifies the de-orphan by execution, pre-merge. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * bind main's orphaned no-smuggled-programs-wall.md from its lens carrier The doc merged to main orphaned (docs-only shortcut + then-lying doc_reachability stamp — the same false-green class this PR fixes). With the stamp corrected, the orphan wall's first live pre-merge run (this PR's floor) caught it: 1 of 1880 witnesses red. Bound from medium_structure_containment.dag, the wall the design doc signs — same bind-from-carrier convention as accelerator_demo_plan.dag:51. Verified by build_doc_graph_report replication on the merged tree: doc_count=108, orphan_count 1->0, dangling 0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * WIP: map reduce * machine-shape plan: apply #6663 review amendments 1+2 - Amendment 1: the 'evidence carried by construction' claim is gated on the record-field wall (witness-realization P0 / #6663 audit F1) — the typechecker checks field NAMES only (refuted-by-execution: Known omitting evidence compiles at 0 diagnostics); P0 named a Phase-1 acceptance precondition. Asymmetry recorded: the no-kind wall rests on field-name checking, which DOES hard-error — it holds today; evidence-required does not. - Amendment 2: Phase 2 claims the DerivedFrom fill of CostAccount.space only; the AIMD governor's dissolve-on additionally requires MeasuredBy per-runnable peaks (witness-realization P1) — derived operand footprint and measured peak are different space facts (receipt: 6.25GB VmSize vs KB operands — retention, not operands; the v1 run-stability axis). - Cross-refs: P4 composition note in the supersession paragraph; P1 named third party to the Quantified/CostBasis convergence (one carrier, not three; realization_measurement.dag merge-order flagged); Energy/Watt divergence deduped with audit F3 (owner TBD). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * WIP: map reduce * heal main's composed drift + re-anchor vacuity design docs (unblocks all full-floor PRs) Main's tree (post #6638/#6664) fails generated_artifact_drift_gate_passes on every full floor: the vacuity lane hand-added a 'Sibling family' paragraph to the GENERATED docs/plans/inert-layer-lens.md without updating its generating Plan row (dag/gunbc/plans/inert_layer_lens.dag) — committed != regenerated. Their docs-only PRs merged through the docs-only shortcut, which skipped both the drift gate and the doc-graph wall. 1. Regenerate inert-layer-lens.md (paragraph removed; byte-identical to warm-crab-65's independent main_wet regen on #6658 — same blob 2b36cf2). 2. That hand-edit was ALSO the only doc-graph anchor for the vacuity lane's two design docs; regen alone orphans vacuity-lens-design.md and (via its link chain) lens-consolidation-design.md. Re-anchored with a bind: provenance row in dag/std/materialization_ladder.dag — the file whose AuthoredDuplication verdict the vacuity doc's load-bearing correction is about — migrating to the vacuity lens .dag carrier when it lands. Verified by build_doc_graph_report replication: doc_count=110, orphan_count=0, dangling=0. Follow-up for the vacuity lane: re-add the sibling-family paragraph via the inert_layer_lens Plan row (the authority), not the generated md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Brian Searls <briansearls1@gmail.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jul 16, 2026
… evidence carriers, Energy, scheduling-invariant refinement) (#6685) * WIP: map reduce * WIP: map reduce * WIP: map reduce * WIP: map reduce * machine-shape plan: end shape agreed, no-kind rule, convergence map to existing carriers - §2 terminal model pinned (operator rulings 2026-07-15): one locality lattice (lifted to std, converging BOTH existing latency enums), divergence/idle-lane/ crossing laws, Placement dissolution trigger, kind-erasure at the ComputeHost→MachineShape derivation boundary - convergence map: every end-shape element bound to its existing carrier (HardwareThreadCount reused for lane_count; PlacementSupplyRow identified as the degenerate single-domain MachineShape; PTX ThreadHierarchyShape/PtxCost gain their consumer; MemoryKind.UnifiedShared flagged as topology-in-technology) - MemoryLevel.sharing dropped: sharing derives from SharedLevelEdge graph structure (single authority) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * WIP: map reduce * machine-shape plan: address operator request-changes (7 blocking findings) - MachineShape is now a representable graph: DomainId/LevelId identities, explicit edge endpoints, SharedLevelEdge references the owner's level by id (embedding duplicated it), InterconnectLink coproduct holds NetworkAttach (LinkEdge was PcieLink-only while the map claimed NetworkInterface as a fill), terminal Placement = DomainId reference; dangling refs refuse - Phase 3 batching vs signed scheduling authority: conflict acknowledged, now an EXPLICIT supersession proposal (topology = pure fn of declared shape; MeasuredBy banned from topology; schedule_eq generalized to equal-given-equal- declared-inputs) gated on operator sign-off, with a confined fallback - both §5 fallback arms converted to refusals: Priced|PricingRefused{missing} (no term-incomplete Predicted accounts), Placed|PlacementRefused{missing} (no stay-at-current-domain answer) - Quantified<T> restructured: Precision (Exact|Interval) x Evidence (Cited|MeasuredBy{ExecutionReceiptDigest}|DerivedFrom) — evidence-bearing constructors make the authored-literal RED enforceable - locality/latency split into two axes: latency = per-level magnitude with one std class projection (converging ReadLatencyClass + network LatencyClass); locality = graph-derived, domain-relative (no universal total order) - OperandFlow total derivation spelled out: operand_root (fail-closed), hash- authority convergence precondition (v2.std.node.Hash vs ContentHash — the fnv1a64 thread), edge->root mapping for node_keyed_graph_transitive_bytes, OperandFlowRefused rows - AssociativityEvidence subject-bound: {combine, inhabitant, law, receipt}, license requires structural identity with the scheduled combine; keyed-patch witness scoped to mechanism-precedent-only; within-fold expansion scoped kernel-internal (never central Schedule topology) - corrections: PlacementSupplyRow has zero production callers (grep -l overcount); document-level dissolution trigger added (Plan-row registration = part of Phase 1 definition of done) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * de-orphan machine-shape plan doc + correct doc_reachability lying live-tree stamp Two fixes from the docs-enforcement audit (operator-directed): 1. bind: provenance row in accelerator_demo_plan.dag makes docs/plans/machine-shape-orthogonal-scheduling.md doc-graph-reachable (the established hand-authored-design-md convention: accelerator_demo_plan :51, live_read_classification.dag:66). Registration as a gunbc.plan.Plan row stays the md's declared Phase-1 dissolution — registering now would flip the actively-evolving doc into a generated artifact prematurely. Verified by build_doc_graph_report replication: doc_count=107, orphan_count 1->0, dangling 0. 2. doc_reachability_witness_test live_tree_disposition: SubstrateInputsOnly -> ReadsLiveTree. The 2026-07-12 machine stamp (#6479 entry-text batch) was false: every test fn reads the live docs/ tree via doc_graph_* host builtins — the exact classifier blind spot live_tree.dag:5 declares. The false stamp made the orphan wall predict-skippable, which composed with the docs-only floor shortcut into a pre-merge false-green (this PR minted an orphan with green CI). ReadsLiveTree restores the never-skip tooth: the wall now runs on every full floor, including this PR's. This diff leaves the docs-only shortcut class, so this PR runs the full floor with the corrected stamp — the wall itself verifies the de-orphan by execution, pre-merge. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * bind main's orphaned no-smuggled-programs-wall.md from its lens carrier The doc merged to main orphaned (docs-only shortcut + then-lying doc_reachability stamp — the same false-green class this PR fixes). With the stamp corrected, the orphan wall's first live pre-merge run (this PR's floor) caught it: 1 of 1880 witnesses red. Bound from medium_structure_containment.dag, the wall the design doc signs — same bind-from-carrier convention as accelerator_demo_plan.dag:51. Verified by build_doc_graph_report replication on the merged tree: doc_count=108, orphan_count 1->0, dangling 0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * WIP: map reduce * machine-shape plan: apply #6663 review amendments 1+2 - Amendment 1: the 'evidence carried by construction' claim is gated on the record-field wall (witness-realization P0 / #6663 audit F1) — the typechecker checks field NAMES only (refuted-by-execution: Known omitting evidence compiles at 0 diagnostics); P0 named a Phase-1 acceptance precondition. Asymmetry recorded: the no-kind wall rests on field-name checking, which DOES hard-error — it holds today; evidence-required does not. - Amendment 2: Phase 2 claims the DerivedFrom fill of CostAccount.space only; the AIMD governor's dissolve-on additionally requires MeasuredBy per-runnable peaks (witness-realization P1) — derived operand footprint and measured peak are different space facts (receipt: 6.25GB VmSize vs KB operands — retention, not operands; the v1 run-stability axis). - Cross-refs: P4 composition note in the supersession paragraph; P1 named third party to the Quantified/CostBasis convergence (one carrier, not three; realization_measurement.dag merge-order flagged); Energy/Watt divergence deduped with audit F3 (owner TBD). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * WIP: map reduce * heal main's composed drift + re-anchor vacuity design docs (unblocks all full-floor PRs) Main's tree (post #6638/#6664) fails generated_artifact_drift_gate_passes on every full floor: the vacuity lane hand-added a 'Sibling family' paragraph to the GENERATED docs/plans/inert-layer-lens.md without updating its generating Plan row (dag/gunbc/plans/inert_layer_lens.dag) — committed != regenerated. Their docs-only PRs merged through the docs-only shortcut, which skipped both the drift gate and the doc-graph wall. 1. Regenerate inert-layer-lens.md (paragraph removed; byte-identical to warm-crab-65's independent main_wet regen on #6658 — same blob 2b36cf2). 2. That hand-edit was ALSO the only doc-graph anchor for the vacuity lane's two design docs; regen alone orphans vacuity-lens-design.md and (via its link chain) lens-consolidation-design.md. Re-anchored with a bind: provenance row in dag/std/materialization_ladder.dag — the file whose AuthoredDuplication verdict the vacuity doc's load-bearing correction is about — migrating to the vacuity lens .dag carrier when it lands. Verified by build_doc_graph_report replication: doc_count=110, orphan_count=0, dangling=0. Follow-up for the vacuity lane: re-add the sibling-family paragraph via the inert_layer_lens Plan row (the authority), not the generated md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * WIP: map reduce * machine-shape plan: record operator rulings 5-8 (2026-07-15) - R5 compute_fabric relationship: Shape IS the degenerate one-axis MachineShape; market stays thin (no #5904 rebuild); Fabric = outermost rung of the recursive supply tower. Convergence-map row added. - R6 evidence carriers: staged convergence (Quantified for greenfield, P1 receipts reuse Evidence.MeasuredBy, CostBasis migrates on forced join); owner = #6663 lane. - R7 Energy: derived quantity (Power x Time), lands Phase 1, is the F3 dedupe. - R8 scheduling invariant REFINED not superseded (operator: determinism was being conflated with input-invariance — different machines are different inputs). Surviving wall: no UNSTABLE (MeasuredBy) inputs to topology; declared shape is a stable input; cross-host schedule_eq demoted to corollary under equal declared shapes. Phase 3 UNBLOCKED. Open list rewritten: law-carrier home, SymbolIndex sequencing, hash convergence (dispatched), P0 field wall (#6663) remain. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * WIP: map reduce * machine-shape plan: reconcile §2/§3/§5/§8 with rulings 6-8 (cursor review on #6685) Five stale spots aligned: Energy divergence now records ruling 7 (was 'flagging for operator'); the Quantified/CostBasis rows in §2 and the convergence map record ruling 6's staged convergence (was 'open Q1'); §5's batching rule reads 'under the refinement' (was 'supersession'); §8's schedule_eq wall restated per ruling 8 (corollary under equal declared shapes, not unconditional). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Brian Searls <briansearls1@gmail.com> Co-authored-by: Claude Fable 5 <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
eager-koi-809.Pushing to
session/eager-koi-809advances 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