Repository navigation
Declare the rung drop D13 cut (c) took on the Network requirement - #12175
Merged
Merged
Conversation
Cut (c) (#11993) and its final-base census (#12125) deleted an authored uses row when derived demand was NONEMPTY. They did not check that the derived set covers each resource the row named. A direct resource operation surfaces in service_names under the resource's name (Filesystem, Clock, Urandom), but Network never does: only the services it reaches appear. So the Network requirement of every deleted net: Network identity is represented nowhere. Population: 312 identities / 82 modules in the #11993 diff and 165 / 31 in #12125's. DESIGN 4b(3): declared rather than silent. previous MechanicallyPreventable, temporary Mitigatable, LostAsPassenger on the deleted rows. The restoration trigger names the capability: DependencyDemand derives each resource requirement keyed on the resource declaration's identity, established by a census over the deleted identities. Restoring authored rows, or adding Network to service_names by spelling, does not discharge it. Found by smart-tern-891 (#12047), confirmed against the census data, ruled a silent loss by snappy-deer-443. Co-Authored-By: Claude Opus 5.5 (1M context) <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.
D13 cut (c) (#11993) and its final-base census (#12125) deleted an authored
usesrow whenever the function's derived service demand was nonempty. They never checked that the derived set covers each resource the row named.ItemInfo.service_namesunder the resource's own name.Filesystem,ClockandUrandomall appear in the census data.Networknever appears. Only the services a Network effect reaches do (ssh.Session,http.Client,redfish.Http, ...).So every deleted
net: Networkidentity lost its Network requirement with no derived stand-in. That is a silent rung loss on main. smart-tern-891 found it while modeling #12047; I confirmed it against the census data, and snappy-deer-443 ruled it a loss that must be declared.The declaration
gunbc.rung_drop.network_requirement_unrepresented_after_uses_cut, enrolled ingunbc.rung_drop.roster, projected intodocs/design-rung-drops.md:MechanicallyPreventable, temporaryMitigatable. The function is still known to be effectful through its services; the Network requirement itself is unrepresented.LostAsPassenger, riding on the deleted rows.net: Networkidentities across 82 modules in the Primitive-egress wind-down (split A): OpenBMC Optional repairs, roadmap authority, main repairs, EFFECTS-1 cut (c) #11993 diff, and 165 across 31 in D13 cut (c) final-base census: restatement uses rows deleted, the rest retained at row identity #12125's. The rows name both landed commits.DependencyDemandderives each resource requirement keyed on the resource declaration's identity, established by a census over the deleted identities. Two things are explicitly excluded: restoring authored rows, which would reinstate the restatement D13 deleted; and adding Network toservice_namesby spelling.I chose a declared drop over restoring the clauses. Restored rows would put a second authority back beside the derived carrier, and the capability that closes the loss is derivation. Building that carrier is EFFECTS-1's, and it is currently unowned. #12047 has been reduced to the emit-time refusal; its typecheck wall returns later as a consumer of the carrier.
🤖 Generated with Claude Code