Repository navigation
Restore the inert-layer-lens §8 sibling-family note that #6649's regen silently deleted - #6671
Closed
gunbai-bot[bot] wants to merge 23 commits into
Closed
gunbai-bot[bot] wants to merge 23 commits into
gunbai-bot[bot] wants to merge 23 commits into
Conversation
…)/2b/2c signed, B1 working-default typed-target) + tick landed slice-0/1 roadmap boxes Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…uperseded) + clear the stale FLAG-gating text in the critical-path summary Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ce-0/1 ticks + slice-2 in-flight note into roadmap_authority.dag (done+operator-sign rows) and regenerate via main_wet; drift gate PASS locally Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ciated concat over receipt lines → balanced pairwise join, O(len·n) → O(len·log n) copying, byte-identical output by associativity Opus noted-and-waived the defect on #6586; the standing operator ruling (DESIGN §6, 2026-07-10) forbids the 'n is small here' waiver. Proven by srv3_typed_receipt_emit_uses_printf_not_naive_echo (content assertion) green. Root cause — no std linear join authority (N hand-rolled joins: join_slash, join_mirror_urls_for_shell, this) — goes on the Wave 4 ledger, not patched per-site here. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… it) + add Srv3InstallDiagnosticObserve / OsInstallActuatorToolchainEnsure arms (#6587's variants landed armless — fifth composition-skew instance); whole-tree compile 0 diagnostics Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…(unblocks main) main is red on `generated_artifact_drift_gate_passes` (batch 4), and every open PR inherits it. Cause: #6638 added the §8 "Sibling family" blockquote directly to `docs/plans/inert-layer-lens.md`, which is a GENERATED projection of `dag/gunbc/plans/inert_layer_lens.dag`. The authority never carried the note, so regeneration no longer reproduced the committed doc — drift. Fix restores the single authority rather than reverting the content: the note is added to the authority via the existing `quote(blocks: [...])` helper, so the authority now generates exactly the bytes already committed. `docs/` is byte-unchanged by this diff — the author's content was right; its home was not. Proven by execution, both directions: - authority fixed -> PASS run_generated_artifact_drift_gate - authority stashed -> FAIL run_generated_artifact_drift_gate (discriminating control) Note on how this landed: docs-only diffs skip the witness corpus per the interim plan-artifact scoping, and the drift gate is floor-resident — so a hand-edit to a generated `docs/plans/*.md` projection is not gated on the PR and only reds main afterward. The allowlist already excludes some generated carriers (.gitignore, README/CLAUDE/DESIGN symlinks) for exactly this class (#6236); generated `docs/plans/*.md` projections are not excluded. Flagged separately — not fixed here. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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>
gunbai-bot
Bot
changed the title
gunbai-bot Bot
pushed a commit
that referenced
this pull request
Jul 15, 2026
Note restoration is owned by #6671; revert dag and md to origin/main so this PR stays the pure 5-file classifier de-fork and drift-green. Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls
added a commit
that referenced
this pull request
Jul 15, 2026
* WIP: W0.1 lens de-fork: unify effect/idempotency/ownership/parallelism classi * WIP: W0.1 lens de-fork: unify effect/idempotency/ownership/parallelism classi * Import AlgebraicIdempotenceProven in idempotency lens after de-fork. The variant moved to algebraic_composition.dag with the classifier rows; idempotency.dag still pattern-matches it in witness/equality helpers. Co-authored-by: Cursor <cursoragent@cursor.com> * Drop stale-base revert of inert-layer-lens.md (not part of W0.1). Restore the vacuity sibling-family blockquote from main; the prior regenerated-artifact drift fix was an unrelated lane change that would orphan vacuity-lens-design.md from the doc graph. Co-authored-by: Cursor <cursoragent@cursor.com> * WIP: W0.1 lens de-fork: unify effect/idempotency/ownership/parallelism classi * WIP: W0.1 lens de-fork: unify effect/idempotency/ownership/parallelism classi * Drop inert_layer_lens changes from W0.1 PR scope. Note restoration is owned by #6671; revert dag and md to origin/main so this PR stays the pure 5-file classifier de-fork and drift-green. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Brian Searls <briansearls1@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Author
|
Superseded by #6672 (9e1f354), which landed the same §3 fix — restore the note via the #6672 rewrote the note as "Kin families (§2/§3, distinct invariants)" rather than restoring #6638's original "Sibling family … opposite end of the plurality axis (0 vs ≥2)". That is a real correction, not a paraphrase: the original framed inertness and vacuity as two ends of one axis, whereas they are distinct invariants that share a counted-relation mechanism but diverge in verdict and remedy (inertness → reachability gate/roster; vacuity → oracle provenance). This PR would have restored the weaker wording. Closing rather than resolving the conflict. main already has the note in both the authority and its generated doc, which is the outcome this PR existed to reach. Worth recording, since this PR's history is a compact case study in the drift trap:
The underlying gap stands: a generated — sent from calm-ferret-849 |
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.
What happened, in order
docs/plans/inert-layer-lens.md— a generated projection ofdag/gunbc/plans/inert_layer_lens.dag. The authority never carried it → drift.Net: an authored design note was lost to a mechanical regen, and the only signal was main going green.
What this PR does
Restores the note in its correct home:
dag/gunbc/plans/inert_layer_lens.dag§8 carries the note via the existingquote(blocks: [...])helper (already imported/used in this file).docs/plans/inert-layer-lens.mdis regenerated from that authority, so the two agree.The regen diff is exactly the 2 lines #6649 removed — no other doc churn.
Verified by execution (on the merged head)
FAILPASSThat first row matters: the earlier version of this PR was approved and CI-green against a pre-#6649 base, and would have re-red main if merged after #6649 landed. Caught by re-running the gate on the rebased head rather than trusting the prior green.
The systemic gap this demonstrates (flagged, not fixed here)
A generated
docs/plans/*.mdcan be hand-edited with no PR-time gate (docs-only skips the floor; the drift guard is floor-resident). The content then lives until someone regenerates, at which point it is silently discarded. Both failure directions are silent to the author.The allowlist already excludes some generated carriers (
.gitignore,README.md/CLAUDE.md/DESIGN.mdsymlinks) for exactly this class — #6236: "their only drift guard is floor-resident; whitelisting them would self-shortcut that gate." Generateddocs/plans/*.mdprojections are not excluded, so the self-shortcut is open for them. This will recur.If the note is not wanted, close this PR — the note stays deleted and main stays green. This PR exists because the deletion looked accidental (a regen sweeping up drift), not deliberate.
🤖 Generated with Claude Code