Skip to content

XL-N Manager - #10410

Closed
briansrls wants to merge 4 commits into
mainfrom
rr375
Closed

briansrls wants to merge 4 commits into
mainfrom
rr375

Conversation

@briansrls

Copy link
Copy Markdown
Contributor

Auto-opened by session-dashboard for session bright-ram-778.
Pushing to rr375 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.

Brian Searls and others added 4 commits September 4, 2026 07:49
… a correct producer and a re-absorbing consumer produce together

The class was found by review 59831 on gunbc#10146 and diagnosed by swift-otter-365,
whose repair is the instance recorded here: carried_structural_type_name was fixed to
return empty at its depth-16 ceiling -- correct in isolation -- while its parent frame
converted that empty back to `here`, so declared_alias_target_matches_produced kept
receiving a fabricated shallow identity and alias admission kept succeeding. The first
fix was itself an instance of the class it was fixing.

Filed as its own row rather than by widening #10146, so the carrier stays one row per
file and that PR keeps its single subject.

Bounded against absorbing_fallback deliberately: there a FAILURE ARM widens instead of
refusing and the producer is the defect; here the producer already refuses correctly and
a CONSUMER undoes it. No single capability retires both.

The next-rung trigger is stated as a capability -- the compiler decides whether every
consumer on every path either propagates a refusal or refuses -- because a trigger naming
this one parent frame would be satisfied while every other producer-consumer pair in the
tree stayed exposed.

The projection docs/design-failure-modes.md is left to heal-generated-artifacts to derive
from the merged authorities rather than regenerated locally.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WgiDD3VoavwLrcu832nJ2V
…8-refusal-reabsorbed

# Conflicts:
#	dag/gunbc/recurring_failure_mode/roster.dag
# Conflicts:
#	dag/gunbc/recurring_failure_mode/roster.dag
#	docs/design-failure-modes.md
@gunbai-bot

gunbai-bot Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Closing as a stray: this branch rr375 is my local working-branch name, auto-pushed by the session harness, and its head bf1717b is an ANCESTOR of session/bright-ram-778-refusal-reabsorbed (ea8fc13) — it carries nothing unique. The real PR is #10375. Deleting the branch so it cannot later auto-open a revert of work merged past it.

@gunbai-bot gunbai-bot Bot closed this Sep 4, 2026
@gunbai-bot
gunbai-bot Bot deleted the rr375 branch September 4, 2026 12:22
@gunbai-bot gunbai-bot Bot mentioned this pull request Sep 4, 2026
6 tasks
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.

1 participant