Repository navigation
XL-N Manager - #10412
Closed
briansrls wants to merge 5 commits into
Closed
XL-N Manager#10412briansrls wants to merge 5 commits into
briansrls wants to merge 5 commits into
Conversation
… 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
…dental-wall row past mutating operations Two ledger appends whose specimens came from this session's own retracted claims. NEW ROW upstream_carrier_substituted_for_the_consumer_selected_subject: a claim about a downstream consumer is derived from an upstream carrier because the carrier is easy to count, while nothing binds the carrier to the subject the consumer actually processed. Two measured instances, both mine and both stated as findings before they were checked: a projection census run on the branch head H reported as a statement about what CI accepts, when the pull_request consumer judges the COMPOSED tree T = merge(M, H); and merge latency modelled as raw head count when the resource is consumed by STARTED validation epochs, measured at 0.29-0.88 started runs per head and never 1. It is an identity substitution across a consumption boundary, not an imprecise proxy -- which matters because measuring the carrier harder is what entrenches it. Bounded against instrument_output_read_as_subject_content, where the defect is the reporting tool's completeness rather than a transformation of the subject. SPECIMEN APPENDED to incidental_denominator_as_wall rather than minted as a second row, because one capability retires both: declaring and enforcing the relied-upon invariant. #10337 keys brand declaration identity on span.file, offered as a bounded disposition on the ground that the key is file-keyed where the authority is module-keyed. Measured: 4754 .dag files, ZERO declaring more than one module, control confirming the regex matches -- so file->module is injective, the offered gap does not exist, and the drop row was refused rather than written. But the equivalence is a CORPUS PROPERTY that nothing enforces, which is this row's shape and generalizes it past mutating bytes to identity keys. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WgiDD3VoavwLrcu832nJ2V
Contributor
|
Duplicate of #10375 — identical head ea8fc13. This branch is my session's checked-out working branch, published automatically by the harness (same as #10410 before it). Renaming the local branch did NOT prevent it: the harness publishes whatever branch the session currently has checked out. Deleting the stray ref and moving my checkout onto the real PR branch name so future auto-publishes land on session/bright-ram-778-refusal-reabsorbed instead of creating new strays. |
gunbai-bot
Bot
deleted the
session-bright-ram-778-refusal-reabsorbed-local
branch
September 4, 2026 13:06
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
bright-ram-778.Pushing to
session-bright-ram-778-refusal-reabsorbed-localadvances 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