Skip to content

Enforce the two decidable sub-cases of stale_claim_survives_its_own_correct_edit (declared-symbol citations; lifecycle-bounded referents modeled, not stringly) - #10595

Closed
gunbai-bot[bot] wants to merge 1 commit into
mainfrom
session/tidy-heron-873
Closed

gunbai-bot[bot] wants to merge 1 commit into
mainfrom
session/tidy-heron-873

Conversation

@gunbai-bot

@gunbai-bot gunbai-bot Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Auto-opened by session-dashboard for session tidy-heron-873.
Pushing to session/tidy-heron-873 advances this PR.

Worker attestation

Before flipping this PR to ready for review, confirm each item:

  • Title describes the change (not the session id or branch).
  • PR body summarises what and why (replace the TODO below).
  • Tests run: name the command (e.g. npm test, cargo test) and the result.
  • If this closes a work item, the body contains a Closes #N directive.
  • No commits on this branch are surprises (no fork/cherry-pick I did not make).
  • No secrets / credentials / large binaries staged.

Summary

TODO: replace this paragraph with one or two sentences naming the change and its motivation. Reviewers read this first.

Test plan

  • TODO: list the commands that ran (or "no tests changed; relied on CI") and the outcome.

…on one

The second decidable sub-case of
gunbc.recurring_failure_mode.stale_claim_survives_its_own_correct_edit: a
citation naming a DECLARED SYMBOL is already decided at ingestion by
v1_compiler.cli_run.declaration_index inside the required-CI parse phase, while
a citation naming a LIFECYCLE-BOUNDED REFERENT is decidable the same way only if
such referents are modeled rather than spelled into a String.

gunbc.guarantee_stall carried both halves of a next-rung trigger in one String,
so "node://adhoc-a3b0e05f-374 lands: the wall materializes the operation" read
as a trigger whose satisfaction condition was a work item reaching DONE. The
roster's own dated reading records three such lanes reaching done with their
conditions unmet, and had to state in a paragraph the split no field expressed.

NextRungTrigger now carries the operative half as `capability` and the asked
lanes as modeled DashboardWorkItemReferent rows in `awaiting`, reusing
gunbc.roadmap_model RoadmapNodeId rather than minting a second identity.
stall_trigger_admission refuses a capability that spells the declared
dashboard-node URI scheme, and every_stall_trigger_is_admitted folds it over the
live roster. Four rows were migrated by that wall -- the roster paragraph counted
three, which the migration falsified and the paragraph now records.

Evidence: test.claim.guarantee_stall_witness_test gains a discriminating red per
admission arm asserted BY CAUSE, a positive control differing in exactly one
property (referent inside the capability vs beside it), the roster-wide fold in
both directions, and a rendering assertion in both directions so the provenance
half is not lost by the migration.

The residual is declared rather than implied:
gunbc.guarantee_stall.trigger_capability_referent_free_by_construction_stall
records rung 2 with ceiling 3 and a capability-grain trigger.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011ZiUUrreNAiyLhhDBuJDaX
@gunbai-bot

gunbai-bot Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor Author

Closing without flipping to ready: this PR would revert main, not add to it.

The work this session owed landed as #10582, squash-merged at 86be37f, which is an ancestor of main. Verified content-wise rather than by the merge label: dag/gunbc/lifecycle_bounded_referent.dag and dag/gunbc/guarantee_stall/trigger_capability_referent_free_by_construction_stall.dag both exist at origin/main, every_stall_trigger_is_admitted is present in gunbc.guarantee_stall there, and git diff origin/main origin/session/tidy-heron-873 over those paths is EMPTY.

What this PR's diff actually is: session/tidy-heron-873 still points at the pre-squash commit and main has advanced past it. The comparison is 150 files, 14,370 deletions — other lanes' merged work that this branch simply does not have. Merging it would undo them. The file list on the PR is the stale-branch delta, not a change I authored beyond #10582.

No further commits are coming from this session; the node is discharged.

— sent from tidy-heron-873

@gunbai-bot gunbai-bot Bot closed this Sep 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants