Skip to content

Docket: the pending discharge collapses a Pending slot and a Declined slot into one requirement element (§9, ratified 4.2 L1966-1971) #73

Description

@dhh1128

Filed per the disposition of round 42-6's reconciliation census, finding F-6, which records this as live repair content the ratified text lacks and names the carriage-encoding round as its plausible home.

The span. spec/custos-4.2.md §9, L1966–1971: an unsatisfied operator group "discharges as a pending finding whose typed requirement set enumerates exactly the unfilled slots — each element naming the slot's required schema, its expected issuer, and the citing clause."

The defect. "Unfilled" is not a state the cited grammar has. The profiled operator conventions put every slot in exactly one of three dispositions: Pending, an anticipated endorsement that has not arrived; Endorsed, whose weight enters the sum; and Declined, an authenticated refusal by the same candidate, which records attributable dissent and whose weight does not enter the sum.

"Unfilled" collapses Pending and Declined. They have opposite cure paths — a pending slot is cured by the candidate acting, a declined slot is never cured by waiting, because the candidate has acted and the act was a refusal. The clause's own promise is that the cure path is readable off the finding, and for one of the two cases it is not.

Repair shape. Name the slot's disposition as a component of each requirement element, citing the profiled operator conventions rather than transcribing them, since R20 already makes those semantics a pinned external dependency. Drafted text is in PR #70, which the census dispositions merge-as-record.

Why it needs a disposition rather than a drafting pass. S3-1 routes the translation-profile questions — slot order, issuer qualification, revoked and undisclosed slot behavior — to the chartered encoding round (#57). The disposition question is adjacent to those and probably belongs with them, but no ruling has taken it, and the ratified text meanwhile carries a promise it cannot keep for declined slots.

A second-order exposure, recorded not resolved. §8.2 makes species a mandatory field and R3 puts it in the dedup key and as the final component of the canonical order, so species is load-bearing for byte-identity. Nothing states which species a slot disposition maps to. Pending is plausibly absent; Declined is plainly not, since the bytes arrived and are authenticated. Two engines choosing differently emit requirement sets that differ in a key component — finding #27's divergence class, one tier up.

Relates to #42, #57, PR #70.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    majorDoctrine loss or contradiction

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions