Watch list: repeated cures, counted until stated once

NOTE: repeated cures are flagged (NOTE: watch <name> beside the strained rule) and counted here per specification until stated once; at five specifications (the table titled Thresholds in method.md) it is stated once, in the Execution Contract or this document, by the mayor under settle.md Repeats (Scott, 2026-11-03 17:15Z); the maintainer is told, not asked. Departed names, their council reads and superseded counts: the grammar’s history. Flag first, count recurrence, admit nothing until the corpus forces it (Principle 1 through 3). A line’s count is the specifications carrying its flag, or the count of the tool the line names; lint.py’s W-stale-census checks the label-family counts on every run.

  • the state a refusal leaves: a refused write binding record state read alone; the open question is whether refusal answers on a record in another state or none. Two: Consent (Operation 32) and Provisional Commitment (Operation 30); Invitation’s Operation 37 was deleted to Execution Contract Read 4 at its Final Critique 8, a refused call writing nothing.
  • condition negation: guards a plain negative cannot carry; the open question is one refusal answering in two rows of one precedence chain. Four: Approval Step, Audit Trail, Consent and State Machine.
  • applicability: WHERE-shaped gating written with subject or relative clause. Two: Audit Trail and Recoverable Invocation.
  • persistent state: WHILE-shaped duration written with a term or phrase. One: Audit Trail.
  • cardinality: a need beyond EVERY, EXISTS, EXACTLY ONE and EXACTLY ONE OF. Three: Audit Trail, Credential (Operation 70) and Authenticated Actor (Term current credential).
  • satisfaction: what a violation of WITHIN is, compensate or nonconform. One: Audit Trail.
  • addressable sections: a rule naming a section, where the grammar labels rules and nothing labels a section. One: Recoverable Invocation.
  • position scoping: every rule of a family scoped by a condition on position. One: Recoverable Invocation.
  • negative capability: an obligation to discard a reply already in hand. One: Recoverable Invocation.
  • rule inheritance: one action’s rules restated for another, where the grammar has no inheritance form. Two: Preference-Aware Notification Fanout (Action wiring 54) and Recoverable Invocation.
  • event versus state: where the distinction matters enough that declared terms alone become awkward. None flagged.
  • the order an atom forbids: an atom’s rule that it MUST NOT order a read’s answer, beside a closure row or entry reading the answer unordered, which Execution Contract Read 5’s default order governs wherever the specification names no order. Three flagged: Notification (Operation 21, its Final Critique 9), Tamper Evidence (Concurrent seal 2, its Final Critique 16) and Favorite (Operation 25, its Final Critique 1). The same cure stands unflagged on Cart (Non-goal 14) and Personal Todo (Non-goal 10), and Subscription (Operation 23, its closure row reading unordered) carries the unreconciled form; flag each site when its pattern is next touched.
  • contradiction: two rules normalizing to X MUST a and X MUST NOT a under identical conditions. None found.
  • the wire layer: a term entry’s Projection: line and the Wire: pinned field, with no naming convention of the layer’s own. Fifty-three documents at council read 101; two findings against the layer itself, each a read’s filter keys no line gave, keyed since by the Projection lines (Term filter axes): Selective Disclosure’s Final Critique 7 and Provenance’s Final Critique 12.
  • the term entry grammar: a term entry’s fields drifting per document on the nothing surface. Nine at council read 12; the superset recurs in every migrated specification.
  • a term entry’s kind: Kind: Field carrying stored, derived and pinned values alike. Four: Cart, Consent, Retention Window and Session.
  • the cited line: the Term cited: line written in two shapes this document never states, runs of names each closed by the owner, or a document and what it supplies. Eighteen specifications: four write the first shape, sixteen the second, two both.
  • the frozen surface’s edge: which families a cross-spec citation freezes. None standing since council read 13.
  • the auditor’s vocabulary: the verbs a Generation acceptance section needs, richer than an atom’s own rules use, with nothing owning the split. Not counted.
  • a label family recurring across specs outside the standard set: a concept the corpus keeps declaring by heading: Clock semantics (24), Clock dependence (9), Atomic writes (4), Indeterminate outcome (9), Expiry (4), Instance (3), Correction (2), Durability (1), Instance start (2), Primitive policy (24), Verification caching (2). The counts are tools/grace/cites.py --drift’s, and lint.py’s W-stale-census compares them with the corpus on every run.
  • the malformed predicate: a rule writing “is malformed” over a reference, a predicate Term condition operator does not list, with Execution Contract Input 1 and Query 5 owning it. Twenty-three specifications; Reaction (Operation 23 through 28) flags it as open Ledger line 2026-11-14-a at its Final Critique 1. Past five, and the open question is whether the grammar admits the predicate or each atom writes the refusal over the type its input carries. The arm ok (open line 2026-11-14-b, 167 atoms) is a question of the same class.
  • the comparator written in English: past, longer than, more than etc. in a rule (check.py’s W-comparator). Twenty-nine sites in eight specifications: Recoverable Invocation 14, Audit Trail 8, Defensible Retention 2, and one each in Consent, Lease, Permissions, Session and Subscription.
  • the unadmitted modal: can, could, would, should inside a rule’s subordinate clause (check.py’s W-modal). Eight sites in three specifications: Recoverable Invocation 6, Capability 1 and Audit Trail 1.
  • who gates a write: two postures on one question with nothing declaring the fork — attribution on every write, or the identifier as the whole authorization. Two: Legal Hold requires attribution on every write, and Message Preference accepts the identifier as the whole authorization.
  • the modifier class: a declared noun under an undeclared modifier, with nothing saying whether a modifier owes a declaration (tools/grace/nouns.py). 4,211 of 20,841 noun phrases at council read 105.
  • the side-channel qualifier: a value riding beside an outcome on its own channel, which may not fold into a reason, promote to an outcome or be carried by not-known. Two: Audit Trail’s (compensation-window) and Chain of Custody’s Term attestation verification (Action wiring 44, its Final Critique 19: the Term carried the qualifier inside the value, so Action wiring 45’s EQUALS verified read two ways).
  • the window reading: a two-member value set reading a deadline against now with the boundary instant on the lapsed side, declared by each specification for itself. Three: Provisional Commitment (open lapsed), Invitation and Credential (live lapsed); both halves of Principle 2 are satisfied.
  • the outcome that carries a value: a signature arm carrying a value inside or beside the outcome, which Closed vocabulary 21 parses as one opaque token. Three: Invitation’s already-resolved(stored terminal), Audit Trail’s (compensation-window) and Session’s invalid(validation failure), whose members the rules land as answers; Actor Identity, Capability, Credential and Tamper Evidence carry the form unflagged.
  • the wire surface: the places a name keeps its code spelling, which no rule enumerates. Nine instances across four sweeps, and Shared Cart’s Term cart event (its Final Critique 1); a finding against the set itself is still missing.
  • the external answer that moves: a verification reading a source the atom does not own, whose answer can change between two calls while the binding and consistency invariants were written as if it could not. Four: Actor Identity (Invariant 2.1, 3.1 and 7.1, Check 1.2, 1.3, 3.1 and 3.2), Tamper Evidence (Invariant 3.1 and 7.1), Audit Trail (Invariant 6.3, its Final Critique 52) and Session-Gated Authorization (Check 1.1, External check 6 and 7, its Final Critique 9).
  • the host’s state: a rule keeping a verification from the host’s state beside a verification set closed with and nothing else that takes in a value the host injects. Two: Actor Identity (Invariant 6.2) and Tamper Evidence (Invariant 4.2).
  • the fresh holder value: a composing pattern stating for itself that each take of a Lease carries a holder value no earlier take on the key carried, which Lease Identity 6 asks of every caller and Lease Composition note 5a makes the composing pattern’s to own. Five: Audit Trail (Per-act critical section 1c, Concurrency 1f), Defensible Retention (Concurrency 11), Recoverable Invocation (Term operator run id, Term run id), Resolve a Person’s Data Rights (Concurrency 4) and Multi-Party Approval (Capability requirement 32, its Final Critique 14). Not stated once: its owner is Lease Composition note 5a, an atom’s rule, so a method page cannot discharge it; the mayor’s 2026-11-04 entry says why and Scott may overrule.
  • the blank id: a not-known rule held off a blank identifier, so a blank id answers its blank-input refusal ahead of not-known though the refuses line lists not-known first. Four: Legal Hold (Operation 13), Medication Order (Operation 12), Party Identity (Operation 12, and Operation 16 and Operation 18 at its Final Critique 9) and Owed Record (Operation 12 and Operation 21, its Final Critique 1).
  • the unreadable registry: an atom deciding on what a registry the host reads at the seam answers, with no answer for a call whose registry the host cannot read, so one build answers a refusal its caller reads as final and another the database’s own failure; each cure answers it with the atom’s own registry-unavailable, listed on the refuses line ahead of the refusals the registry’s answer decides. Three: Actor Identity (Operation 33, its Final Critique 5), Retention Window (Operation 24b, its Final Critique 8) and Provisional Commitment (Operation 42, its Final Critique 6).
  • the purged co-member: a live event’s covering range one member of which the audit horizon destroyed, checked member by member against the caller’s presentation, so the event reads as a payload not supplied whatever the caller presents and the substrate’s unverifiable(partially-purged-coverage) is never reached; each cure calls the verification where the record read answers partially-purged coverage and checks the presentation only over a whole covering range. Two: Immutable Ledger (Action wiring 34, Action wiring 35, its first passes of 2026-10-07) and Chain of Custody (Action wiring 41, Action wiring 56, its Final Critique 10).
  • the check over a derived index: a Generation acceptance check reading a derived index whole, which the Execution Contract puts outside the action’s atomicity surface and whose lost entry is a rebuild trigger (the section titled Composition state in execution-contract.md), so a conforming deployment that has lost an entry fails it; each cure reads the subject the index derives from, or only the entries that stand. Four: Capability-Backed Sharing (Check 2.5, its Final Critique 7), Chain of Custody (Check 5.3, its Final Critique 10; Check 1.1, its Final Critique 11), Login (Check 1.1 and Check 2.3, its Final Critique 10) and Reserve from Pool (Check 1.1, its Final Critique 9).
  • the integer range: a sequence number range’s ends compared with PRECEDES, which the grammar gives instants (Earned vocabulary 18), where a sequence number is a quantity; each cure writes one rule per axis that carries a range, EXCEEDS for the integers and PRECEDES for the instants. Two: Provenance (Operation 48 and Operation 60, its Final Critique 9) and State Machine (Operation 45 and Operation 58, its Final Critique 6).
  • the optional field no rule records: an input a call may supply, which a MAY rule lets the record carry and no rule records, so one build keeps the supplied value and another drops it while each obeys every rule (Term MAY rule); each cure records the supplied value by an Operation rule on the admitted action. Four: Provenance (Operation 61, its Final Critique 10), State Machine (Operation 56, its Final Critique 5; Operation 59, Operation 60 and Operation 61, its Final Critique 6), Approval Step (Operation 61, its Final Critique 8) and Compensable Workflow (Non-goal 21, its Final Critique 5, closed by a named non-goal and its owner in place of a recording); one atom writes the gap uncured (Legal Hold, State 3).
  • the unnamed purged half: a derived index whose entries outlive their purged source events, kept by the pattern’s own rebuild rule and by Execution Contract Database 3 and 4, with its live half alone classified, so its truth-bearing half names no atom, against pressure-testing’s frozen A derived index splits at the horizon and the Execution Contract, which counts unflagged truth-bearing records a conformance finding; each cure classifies the purged half extraction-pending against Erasure Tombstone. Two: Multi-Party Approval (Composition state 11, its Final Critique 12) and Execute Gated Workflow (Composition state 21, its Final Critique 12).
  • the reconciliation’s own run: a liveness sum that budgets the reconciliation’s cadence and one write but not the reconciliation’s own run, its enumeration and its closures’ writes, so on a conforming deployment whose run outlasts the slack an owed record lands past its escalation instant unescalated, or is escalated as it lands; each cure counts a disclosed run bound in the sum in the write’s place. Six: Chain of Custody (Term liveness sum, its Final Critique 10), Execute Gated Workflow (Term liveness sum, its Final Critique 13), Multi-Party Approval (Term liveness sum, its Final Critique 14), Propagate Consent Revocation Downstream (Term liveness sum, its Final Critique 11), Preference-Aware Notification Fanout (Term liveness sum, its Final Critique 13) and Capability-Backed Sharing (Term escalation reach, its Final Critique 12); no pattern writes the sum uncured now. Provisional Commitment’s atom carries the flag too (Term reclamation sum). At five the Repeats rule owes a rule stated once, written in a unit of its own.
  • the horizon against the escalation: a start condition that sets the compensation window against a liveness sum while the sweep’s reach stops at the horizon, so a conforming deployment whose window runs past the horizon leaves a marker opened at the owed record’s start unescalated for good, one build escalating it and another never examining it; each cure counts the escalation reach (the window, the cadence and the disclosed run bound) and starts the instance only where the horizon exceeds it. Seven: Audit Trail (Instance start 22), Execute Gated Workflow (Capability requirement 25), Multi-Party Approval (Capability requirement 29, its Final Critique 14), Chain of Custody (Capability requirement 29, its Final Critique 11), Propagate Consent Revocation Downstream (Capability requirement 34, its Final Critique 11), Capability-Backed Sharing (Capability requirement 19, its Final Critique 9) and Preference-Aware Notification Fanout (Capability requirement 52, its Final Critique 14, the audit horizon against the reconciliation window). Multi-Party Approval, Chain of Custody, Propagate Consent Revocation Downstream, Capability-Backed Sharing and Preference-Aware Notification Fanout carry the flag; the other two sites are unflagged. At five the Repeats rule owes a rule stated once, written in a unit of its own.
  • the segregation policy: Approval Step Composition note 3, which obliges a composing pattern to own the segregation policy over a submitter reference and an approver reference, met by a pattern that passes its initiator as a step’s submitter and states no policy, so one build refuses an initiator naming itself an approver and another admits it; each cure closes it by a named non-goal and its owner. Three: Multi-Party Approval (Non-goal 13, its Final Critique 12), Execute Gated Workflow (Non-goal 9, its Final Critique 13) and Privileged Access Provisioning (Non-goal 17, its Final Critique 3).
  • the adopter’s policy note: a constituent’s Composition note obliging its composing pattern to own a policy over the constituent’s records, met by a pattern that states none, so a build discharging the note picks a policy the pattern never states; each cure closes it by a named non-goal and its owner. Six: Multi-Party Approval (Non-goal 13, Approval Step Composition note 3’s segregation policy, its Final Critique 12), Execute Gated Workflow (Non-goal 9, the same note, its Final Critique 13), Authenticated Actor (Non-goal 15, Actor Identity Composition note 4’s retention of an attestation, its Final Critique 7), Compensable Workflow (Non-goal 17 through 20, State Machine Composition note 4’s call authorization and note 7’s retention of the workflow records, its Final Critique 5), Session-Gated Authorization (Non-goal 14, Session Composition note 9’s retention of the session records, its Final Critique 9) and Resolve a Person’s Data Rights (Non-goal 9 and Non-goal 10, Selective Disclosure Composition note 5’s tamper seal and Consent Composition note 4’s propagation of a withdrawal, its Final Critique 1); the first two carry the segregation policy as well. At six the Repeats rule owes a rule stated once. It is not yet stated: a draft (a Term and two Standard labels in this document, saying a composing pattern applies no policy a Composition note leaves it and the deployment owns it) failed the gate on its verbs (Closed vocabulary 8) and left its owner open, so the question waits for the maintainer (rounds/escalations.md, 2026-11-04).
  • the listing page: a listing read answering EVERY matching record up to the page size, with an order and a continuation key and no rule saying the page starts at the earliest matching key or holds no other record, so one build answers the latest matches and another pads the page with records outside the query; each cure names the matching record in a term and answers the earliest listing keys with no record outside it. Four: Condition Register (Term matching record, Operation 28 and Operation 29, its Final Critique 1), Owed Record (Term matching owed record, Operation 31 and Operation 39, its Final Critique 1), Erasure Tombstone (Term matching erasure tombstone, Operation 15 and Operation 24, its Final Critique 1) and Party Identity (Term matching party, Operation 51 and Operation 61, its Final Critique 11).
  • the read-back’s other arm: a read-back after a retention-step answer (invalid-request carrying step-4) with a rule for one of its two results and none for the other, so one build answers storage-failure carrying intent and retries while another answers carrying outcome and re-enters; each cure adds the missing arm’s own rule, answering the position the writes before it fix. Two: Recoverable Invocation (refuse step 3.3, round 2026-10-18-2205, the arm for the record found) and External Onboarding (Audit arm 25 and Resume 50, its Final Critique 5, the arm for the record absent).
  • the escalation outside the window: a term entry glossing the reconciliation’s output as awaited within the compensation window while its list names an escalation of an overdue partial, which Term overdue partial and the escalation rule put at the first run past the window, so a conforming deployment whose escalation lands at the window plus the cadence plus the run bound breaks the term’s await, one build escalating at the last run inside the window and another at the first run past it; each cure awaits the escalation by the later bound (the escalation reach, the alert bound) and leaves the window for the outputs that land inside it. Four: Resolve a Person’s Data Rights (Term reconciliation, the alert bound), Capability-Backed Sharing (Term reconciliation, its Final Critique 13), Chain of Custody (Term reconciliation, its Final Critique 17) and Propagate Consent Revocation Downstream (Term reconciliation, its Final Critique 15). Capability-Backed Sharing, Chain of Custody and Propagate Consent Revocation Downstream carry the flag; the other site is unflagged.
  • a generated value against an overridable cap: a string the composition itself generates (a rule reason, a cascade reason) carried into a constituent call whose string cap a deployment may declare below the generated value’s length (Execution Contract Input 2 floors a cap only by values a record already holds), so the constituent refuses the call inside the commit with a code the pattern’s closure table calls unreachable; the cure is a capability requirement that forbids the cap and a row owner that names it. One: Multi-Party Approval (Capability requirement 44, its Final Critique 20); flagged.
  • the sweep’s run reading: a reconciliation leg that reads the sweep’s run reading of now, in a rule that names neither whose reading it is nor how the leg comes by it, while the leg’s own reads answer no run reading, so one build has the host inject a second reading at the leg’s seam and another judges entries against its own instant; each cure names Recoverable Invocation’s run as the owner (Recoverable Invocation Primitive policy 18: the sweep reads now once per run at its own seam). Two: Multi-Party Approval (Reconciliation 46, its Final Critique 19) and Chain of Custody (Reconciliation 31, its Final Critique 22); the same rule stands unscoped in Capability-Backed Sharing (Reconciliation 37), Customer Onboarding (Reconciliation 35) and Propagate Consent Revocation Downstream (Reconciliation 39); flagged on Chain of Custody.