{"items": [{"id": "a86m-rate-rate-01-wait-tickets.2", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four tickets in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, the intake bot made four tickets. A clearance to act again is in hand until the day ends.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets rate-cap(4; hour).\nDuring the hour just before now, the intake bot made four tickets. A clearance to act again is in hand until the day ends.", "question": "Suppose the intake bot does nothing for one full hour. What room is left under the cap then?", "options": ["Room for three more", "Room for exactly one more", "None — the cap is already full", "The statement does not settle it", "The full allowance of four is open"], "answer": "The full allowance of four is open", "settlement_stratum": "rate", "frame": "rate-01-wait", "probe": "wait", "domain": "tickets", "scope": "global", "oracle": {"kind": "rate", "probe": "wait", "N": 4, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-01-wait-probes.2", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five probes in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, this monitor made five probes. A clearance to act again is in hand until the day ends.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes rate-cap(5; hour).\nDuring the hour just before now, this monitor made five probes. A clearance to act again is in hand until the day ends.", "question": "Suppose this monitor does nothing for one full hour. What room is left under the cap then?", "options": ["Room for four more", "Room for exactly one more", "None — the cap is already full", "The full allowance of five is open", "The statement does not settle it"], "answer": "The full allowance of five is open", "settlement_stratum": "rate", "frame": "rate-01-wait", "probe": "wait", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "wait", "N": 5, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-01-wait-renders", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four renders in any day; the allowance refills as the day goes by; the note does not say whether the day follows the clock or rolls.\nDuring the day just before now, the night worker made four renders. A clearance to act again is in hand until the day ends.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders rate-cap(4; day).\nDuring the day just before now, the night worker made four renders. A clearance to act again is in hand until the day ends.", "question": "Suppose the night worker does nothing for one full day. What room is left under the cap then?", "options": ["The statement does not settle it", "Room for three more", "Room for exactly one more", "The full allowance of four is open", "None — the cap is already full"], "answer": "The full allowance of four is open", "settlement_stratum": "rate", "frame": "rate-01-wait", "probe": "wait", "domain": "renders", "scope": "global", "oracle": {"kind": "rate", "probe": "wait", "N": 4, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-01-wait-backfills", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four backfills in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, this migration job made four backfills. A clearance to act again is in hand until the day ends.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills rate-cap(4; hour).\nDuring the hour just before now, this migration job made four backfills. A clearance to act again is in hand until the day ends.", "question": "Suppose this migration job does nothing for one full hour. What room is left under the cap then?", "options": ["Room for exactly one more", "The full allowance of four is open", "Room for three more", "None — the cap is already full", "The statement does not settle it"], "answer": "The full allowance of four is open", "settlement_stratum": "rate", "frame": "rate-01-wait", "probe": "wait", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "wait", "N": 4, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-01-wait-invites", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five invites in any day; the allowance refills as the day goes by; the note does not say whether the day follows the clock or rolls.\nDuring the day just before now, the workspace bot made five invites. A clearance to act again is in hand until the day ends.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites rate-cap(5; day).\nDuring the day just before now, the workspace bot made five invites. A clearance to act again is in hand until the day ends.", "question": "Suppose the workspace bot does nothing for one full day. What room is left under the cap then?", "options": ["Room for four more", "The statement does not settle it", "The full allowance of five is open", "None — the cap is already full", "Room for exactly one more"], "answer": "The full allowance of five is open", "settlement_stratum": "rate", "frame": "rate-01-wait", "probe": "wait", "domain": "invites", "scope": "global", "oracle": {"kind": "rate", "probe": "wait", "N": 5, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-01-wait-locks", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four locks in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, this editor made four locks. A clearance to act again is in hand until the day ends.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks rate-cap(4; hour).\nDuring the hour just before now, this editor made four locks. A clearance to act again is in hand until the day ends.", "question": "Suppose this editor does nothing for one full hour. What room is left under the cap then?", "options": ["The full allowance of four is open", "Room for three more", "Room for exactly one more", "None — the cap is already full", "The statement does not settle it"], "answer": "The full allowance of four is open", "settlement_stratum": "rate", "frame": "rate-01-wait", "probe": "wait", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "wait", "N": 4, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-01-wait-replays.1", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four replays in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, the analysis bot made four replays. A clearance to act again is in hand until the day ends.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays rate-cap(4; hour).\nDuring the hour just before now, the analysis bot made four replays. A clearance to act again is in hand until the day ends.", "question": "Suppose the analysis bot does nothing for one full hour. What room is left under the cap then?", "options": ["The full allowance of four is open", "Room for exactly one more", "Room for three more", "None — the cap is already full", "The statement does not settle it"], "answer": "The full allowance of four is open", "settlement_stratum": "rate", "frame": "rate-01-wait", "probe": "wait", "domain": "replays", "scope": "global", "oracle": {"kind": "rate", "probe": "wait", "N": 4, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-01-wait-uploads.1", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five uploads in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, this uploader made five uploads. A clearance to act again is in hand until the day ends.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads rate-cap(5; hour).\nDuring the hour just before now, this uploader made five uploads. A clearance to act again is in hand until the day ends.", "question": "Suppose this uploader does nothing for one full hour. What room is left under the cap then?", "options": ["The full allowance of five is open", "Room for exactly one more", "None — the cap is already full", "The statement does not settle it", "Room for four more"], "answer": "The full allowance of five is open", "settlement_stratum": "rate", "frame": "rate-01-wait", "probe": "wait", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "wait", "N": 5, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-02-wait-tickets", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four tickets in any hour; the allowance refills as the hour goes by; a fresh tally begins with each clock hour.\nWithin the clock hour that is running, the intake bot made four tickets. Those hour boundaries occur on the hour.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets rate-cap(4; hour). per-clock(hour).\nWithin the clock hour that is running, the intake bot made four tickets. Those hour boundaries occur on the hour.", "question": "Suppose the intake bot does nothing for one full hour. What room is left under the cap then?", "options": ["None — the cap is already full", "The statement does not settle it", "The full allowance of four is open", "Room for three more", "Room for exactly one more"], "answer": "The full allowance of four is open", "settlement_stratum": "rate", "frame": "rate-02-wait", "probe": "wait", "domain": "tickets", "scope": "global", "oracle": {"kind": "rate", "probe": "wait", "N": 4, "scope": "global", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-02-wait-probes", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five probes in any hour; the allowance refills as the hour goes by; a fresh tally begins with each clock hour.\nWithin the clock hour that is running, this monitor made five probes. Those hour boundaries occur on the hour.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes rate-cap(5; hour). per-clock(hour).\nWithin the clock hour that is running, this monitor made five probes. Those hour boundaries occur on the hour.", "question": "Suppose this monitor does nothing for one full hour. What room is left under the cap then?", "options": ["Room for four more", "Room for exactly one more", "The full allowance of five is open", "The statement does not settle it", "None — the cap is already full"], "answer": "The full allowance of five is open", "settlement_stratum": "rate", "frame": "rate-02-wait", "probe": "wait", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "wait", "N": 5, "scope": "per-identity", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-02-wait-renders.4", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four renders in any day; the allowance refills as the day goes by; a fresh tally begins with each clock day.\nWithin the clock day that is running, the night worker made four renders. Those day boundaries occur at midnight.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders rate-cap(4; day). per-clock(day).\nWithin the clock day that is running, the night worker made four renders. Those day boundaries occur at midnight.", "question": "Suppose the night worker does nothing for one full day. What room is left under the cap then?", "options": ["The full allowance of four is open", "Room for three more", "Room for exactly one more", "The statement does not settle it", "None — the cap is already full"], "answer": "The full allowance of four is open", "settlement_stratum": "rate", "frame": "rate-02-wait", "probe": "wait", "domain": "renders", "scope": "global", "oracle": {"kind": "rate", "probe": "wait", "N": 4, "scope": "global", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-02-wait-backfills.2", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four backfills in any hour; the allowance refills as the hour goes by; a fresh tally begins with each clock hour.\nWithin the clock hour that is running, this migration job made four backfills. Those hour boundaries occur on the hour.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills rate-cap(4; hour). per-clock(hour).\nWithin the clock hour that is running, this migration job made four backfills. Those hour boundaries occur on the hour.", "question": "Suppose this migration job does nothing for one full hour. What room is left under the cap then?", "options": ["The statement does not settle it", "The full allowance of four is open", "None — the cap is already full", "Room for three more", "Room for exactly one more"], "answer": "The full allowance of four is open", "settlement_stratum": "rate", "frame": "rate-02-wait", "probe": "wait", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "wait", "N": 4, "scope": "per-identity", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-02-wait-invites.1", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five invites in any day; the allowance refills as the day goes by; a fresh tally begins with each clock day.\nWithin the clock day that is running, the workspace bot made five invites. Those day boundaries occur at midnight.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites rate-cap(5; day). per-clock(day).\nWithin the clock day that is running, the workspace bot made five invites. Those day boundaries occur at midnight.", "question": "Suppose the workspace bot does nothing for one full day. What room is left under the cap then?", "options": ["The full allowance of five is open", "None — the cap is already full", "Room for four more", "The statement does not settle it", "Room for exactly one more"], "answer": "The full allowance of five is open", "settlement_stratum": "rate", "frame": "rate-02-wait", "probe": "wait", "domain": "invites", "scope": "global", "oracle": {"kind": "rate", "probe": "wait", "N": 5, "scope": "global", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-02-wait-locks.3", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four locks in any hour; the allowance refills as the hour goes by; a fresh tally begins with each clock hour.\nWithin the clock hour that is running, this editor made four locks. Those hour boundaries occur on the hour.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks rate-cap(4; hour). per-clock(hour).\nWithin the clock hour that is running, this editor made four locks. Those hour boundaries occur on the hour.", "question": "Suppose this editor does nothing for one full hour. What room is left under the cap then?", "options": ["The full allowance of four is open", "Room for three more", "Room for exactly one more", "None — the cap is already full", "The statement does not settle it"], "answer": "The full allowance of four is open", "settlement_stratum": "rate", "frame": "rate-02-wait", "probe": "wait", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "wait", "N": 4, "scope": "per-identity", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-02-wait-replays", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four replays in any hour; the allowance refills as the hour goes by; a fresh tally begins with each clock hour.\nWithin the clock hour that is running, the analysis bot made four replays. Those hour boundaries occur on the hour.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays rate-cap(4; hour). per-clock(hour).\nWithin the clock hour that is running, the analysis bot made four replays. Those hour boundaries occur on the hour.", "question": "Suppose the analysis bot does nothing for one full hour. What room is left under the cap then?", "options": ["None — the cap is already full", "The full allowance of four is open", "Room for exactly one more", "The statement does not settle it", "Room for three more"], "answer": "The full allowance of four is open", "settlement_stratum": "rate", "frame": "rate-02-wait", "probe": "wait", "domain": "replays", "scope": "global", "oracle": {"kind": "rate", "probe": "wait", "N": 4, "scope": "global", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-02-wait-uploads.1", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five uploads in any hour; the allowance refills as the hour goes by; a fresh tally begins with each clock hour.\nWithin the clock hour that is running, this uploader made five uploads. Those hour boundaries occur on the hour.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads rate-cap(5; hour). per-clock(hour).\nWithin the clock hour that is running, this uploader made five uploads. Those hour boundaries occur on the hour.", "question": "Suppose this uploader does nothing for one full hour. What room is left under the cap then?", "options": ["The statement does not settle it", "Room for four more", "Room for exactly one more", "The full allowance of five is open", "None — the cap is already full"], "answer": "The full allowance of five is open", "settlement_stratum": "rate", "frame": "rate-02-wait", "probe": "wait", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "wait", "N": 5, "scope": "per-identity", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-03-release-tickets", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four tickets in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nDuring the hour just before now, the intake bot made three tickets, aged nine and sixteen minutes. Moments ago the intake bot closed one of those tickets; the rest was untouched.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets rate-cap(4; hour). per-any(hour).\nDuring the hour just before now, the intake bot made three tickets, aged nine and sixteen minutes. Moments ago the intake bot closed one of those tickets; the rest was untouched.", "question": "What room is left right after that closure?", "options": ["The statement does not settle it", "Room for exactly one more", "The full allowance of four is open", "None — the cap is already full", "Room for three more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-03-release", "probe": "release", "domain": "tickets", "scope": "global", "oracle": {"kind": "rate", "probe": "release", "N": 4, "scope": "global", "alignment": "per-any", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-03-release-probes", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five probes in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nDuring the hour just before now, this monitor made four probes, aged nine and sixteen minutes. Moments ago this monitor closed one of those probes; the rest was untouched.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes rate-cap(5; hour). per-any(hour).\nDuring the hour just before now, this monitor made four probes, aged nine and sixteen minutes. Moments ago this monitor closed one of those probes; the rest was untouched.", "question": "What room is left right after that closure?", "options": ["The statement does not settle it", "Room for four more", "The full allowance of five is open", "None — the cap is already full", "Room for exactly one more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-03-release", "probe": "release", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "release", "N": 5, "scope": "per-identity", "alignment": "per-any", "used_after": 4, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-03-release-renders.3", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four renders in any day; the allowance refills as the day goes by; the day rolls, so any span of one day counts.\nDuring the day just before now, the night worker made three renders, aged nine and sixteen minutes. Moments ago the night worker closed one of those renders; the rest was untouched.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders rate-cap(4; day). per-any(day).\nDuring the day just before now, the night worker made three renders, aged nine and sixteen minutes. Moments ago the night worker closed one of those renders; the rest was untouched.", "question": "What room is left right after that closure?", "options": ["The full allowance of four is open", "Room for exactly one more", "None — the cap is already full", "Room for three more", "The statement does not settle it"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-03-release", "probe": "release", "domain": "renders", "scope": "global", "oracle": {"kind": "rate", "probe": "release", "N": 4, "scope": "global", "alignment": "per-any", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-03-release-backfills", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four backfills in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nDuring the hour just before now, this migration job made three backfills, aged nine and sixteen minutes. Moments ago this migration job closed one of those backfills; the rest was untouched.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills rate-cap(4; hour). per-any(hour).\nDuring the hour just before now, this migration job made three backfills, aged nine and sixteen minutes. Moments ago this migration job closed one of those backfills; the rest was untouched.", "question": "What room is left right after that closure?", "options": ["Room for exactly one more", "The full allowance of four is open", "The statement does not settle it", "Room for three more", "None — the cap is already full"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-03-release", "probe": "release", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "release", "N": 4, "scope": "per-identity", "alignment": "per-any", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-03-release-invites", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five invites in any day; the allowance refills as the day goes by; the day rolls, so any span of one day counts.\nDuring the day just before now, the workspace bot made four invites, aged nine and sixteen minutes. Moments ago the workspace bot closed one of those invites; the rest was untouched.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites rate-cap(5; day). per-any(day).\nDuring the day just before now, the workspace bot made four invites, aged nine and sixteen minutes. Moments ago the workspace bot closed one of those invites; the rest was untouched.", "question": "What room is left right after that closure?", "options": ["The statement does not settle it", "The full allowance of five is open", "Room for exactly one more", "Room for four more", "None — the cap is already full"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-03-release", "probe": "release", "domain": "invites", "scope": "global", "oracle": {"kind": "rate", "probe": "release", "N": 5, "scope": "global", "alignment": "per-any", "used_after": 4, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-03-release-locks.2", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four locks in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nDuring the hour just before now, this editor made three locks, aged nine and sixteen minutes. Moments ago this editor closed one of those locks; the rest was untouched.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks rate-cap(4; hour). per-any(hour).\nDuring the hour just before now, this editor made three locks, aged nine and sixteen minutes. Moments ago this editor closed one of those locks; the rest was untouched.", "question": "What room is left right after that closure?", "options": ["Room for exactly one more", "The statement does not settle it", "None — the cap is already full", "Room for three more", "The full allowance of four is open"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-03-release", "probe": "release", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "release", "N": 4, "scope": "per-identity", "alignment": "per-any", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-03-release-replays.2", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four replays in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nDuring the hour just before now, the analysis bot made three replays, aged nine and sixteen minutes. Moments ago the analysis bot closed one of those replays; the rest was untouched.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays rate-cap(4; hour). per-any(hour).\nDuring the hour just before now, the analysis bot made three replays, aged nine and sixteen minutes. Moments ago the analysis bot closed one of those replays; the rest was untouched.", "question": "What room is left right after that closure?", "options": ["Room for exactly one more", "None — the cap is already full", "Room for three more", "The statement does not settle it", "The full allowance of four is open"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-03-release", "probe": "release", "domain": "replays", "scope": "global", "oracle": {"kind": "rate", "probe": "release", "N": 4, "scope": "global", "alignment": "per-any", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-03-release-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five uploads in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nDuring the hour just before now, this uploader made four uploads, aged nine and sixteen minutes. Moments ago this uploader closed one of those uploads; the rest was untouched.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads rate-cap(5; hour). per-any(hour).\nDuring the hour just before now, this uploader made four uploads, aged nine and sixteen minutes. Moments ago this uploader closed one of those uploads; the rest was untouched.", "question": "What room is left right after that closure?", "options": ["The full allowance of five is open", "Room for four more", "None — the cap is already full", "Room for exactly one more", "The statement does not settle it"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-03-release", "probe": "release", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "release", "N": 5, "scope": "per-identity", "alignment": "per-any", "used_after": 4, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-04-delete-tickets.4", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four tickets in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, the intake bot made three tickets, aged six and twelve minutes. Moments ago the intake bot removed one much older ticket created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets rate-cap(4; hour).\nDuring the hour just before now, the intake bot made three tickets, aged six and twelve minutes. Moments ago the intake bot removed one much older ticket created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "question": "What room is left right after that deletion?", "options": ["Room for exactly one more", "None — the cap is already full", "The statement does not settle it", "The full allowance of four is open", "Room for three more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-04-delete", "probe": "delete", "domain": "tickets", "scope": "global", "oracle": {"kind": "rate", "probe": "delete", "N": 4, "scope": "global", "alignment": "bare", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-04-delete-probes", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five probes in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, this monitor made four probes, aged six and twelve minutes. Moments ago this monitor removed one much older probe created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes rate-cap(5; hour).\nDuring the hour just before now, this monitor made four probes, aged six and twelve minutes. Moments ago this monitor removed one much older probe created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "question": "What room is left right after that deletion?", "options": ["The statement does not settle it", "Room for exactly one more", "The full allowance of five is open", "Room for four more", "None — the cap is already full"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-04-delete", "probe": "delete", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "delete", "N": 5, "scope": "per-identity", "alignment": "bare", "used_after": 4, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-04-delete-renders", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four renders in any day; the allowance refills as the day goes by; the note does not say whether the day follows the clock or rolls.\nDuring the day just before now, the night worker made three renders, aged six and twelve minutes. Moments ago the night worker removed one much older render created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders rate-cap(4; day).\nDuring the day just before now, the night worker made three renders, aged six and twelve minutes. Moments ago the night worker removed one much older render created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "question": "What room is left right after that deletion?", "options": ["The full allowance of four is open", "None — the cap is already full", "The statement does not settle it", "Room for exactly one more", "Room for three more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-04-delete", "probe": "delete", "domain": "renders", "scope": "global", "oracle": {"kind": "rate", "probe": "delete", "N": 4, "scope": "global", "alignment": "bare", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-04-delete-backfills.1", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four backfills in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, this migration job made three backfills, aged six and twelve minutes. Moments ago this migration job removed one much older backfill created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills rate-cap(4; hour).\nDuring the hour just before now, this migration job made three backfills, aged six and twelve minutes. Moments ago this migration job removed one much older backfill created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "question": "What room is left right after that deletion?", "options": ["None — the cap is already full", "Room for exactly one more", "Room for three more", "The full allowance of four is open", "The statement does not settle it"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-04-delete", "probe": "delete", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "delete", "N": 4, "scope": "per-identity", "alignment": "bare", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-04-delete-invites.1", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five invites in any day; the allowance refills as the day goes by; the note does not say whether the day follows the clock or rolls.\nDuring the day just before now, the workspace bot made four invites, aged six and twelve minutes. Moments ago the workspace bot removed one much older invite created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites rate-cap(5; day).\nDuring the day just before now, the workspace bot made four invites, aged six and twelve minutes. Moments ago the workspace bot removed one much older invite created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "question": "What room is left right after that deletion?", "options": ["None — the cap is already full", "The full allowance of five is open", "Room for exactly one more", "Room for four more", "The statement does not settle it"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-04-delete", "probe": "delete", "domain": "invites", "scope": "global", "oracle": {"kind": "rate", "probe": "delete", "N": 5, "scope": "global", "alignment": "bare", "used_after": 4, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-04-delete-locks", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four locks in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, this editor made three locks, aged six and twelve minutes. Moments ago this editor removed one much older lock created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks rate-cap(4; hour).\nDuring the hour just before now, this editor made three locks, aged six and twelve minutes. Moments ago this editor removed one much older lock created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "question": "What room is left right after that deletion?", "options": ["Room for three more", "The statement does not settle it", "None — the cap is already full", "Room for exactly one more", "The full allowance of four is open"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-04-delete", "probe": "delete", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "delete", "N": 4, "scope": "per-identity", "alignment": "bare", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-04-delete-replays", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four replays in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, the analysis bot made three replays, aged six and twelve minutes. Moments ago the analysis bot removed one much older replay created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays rate-cap(4; hour).\nDuring the hour just before now, the analysis bot made three replays, aged six and twelve minutes. Moments ago the analysis bot removed one much older replay created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "question": "What room is left right after that deletion?", "options": ["None — the cap is already full", "Room for three more", "The full allowance of four is open", "The statement does not settle it", "Room for exactly one more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-04-delete", "probe": "delete", "domain": "replays", "scope": "global", "oracle": {"kind": "rate", "probe": "delete", "N": 4, "scope": "global", "alignment": "bare", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-04-delete-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five uploads in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nDuring the hour just before now, this uploader made four uploads, aged six and twelve minutes. Moments ago this uploader removed one much older upload created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads rate-cap(5; hour).\nDuring the hour just before now, this uploader made four uploads, aged six and twelve minutes. Moments ago this uploader removed one much older upload created a week ago. Apart from that, the position stood. The clearance to proceed was cancelled this morning and not reinstated.", "question": "What room is left right after that deletion?", "options": ["The statement does not settle it", "None — the cap is already full", "Room for exactly one more", "Room for four more", "The full allowance of five is open"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-04-delete", "probe": "delete", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "delete", "N": 5, "scope": "per-identity", "alignment": "bare", "used_after": 4, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-05-count-tickets", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four tickets in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nThe intake bot made four tickets: three of them within the last twenty minutes, and one more than two hours ago.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets rate-cap(4; hour). per-any(hour).\nThe intake bot made four tickets: three of them within the last twenty minutes, and one more than two hours ago.", "question": "How much room does the intake bot have at this point?", "options": ["The full allowance of four is open", "Room for exactly one more", "The statement does not settle it", "None — the cap is already full", "Room for three more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-05-count", "probe": "count", "domain": "tickets", "scope": "global", "oracle": {"kind": "rate", "probe": "count", "N": 4, "scope": "global", "alignment": "per-any", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-05-count-probes.1", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five probes in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nThis monitor made five probes: four of them within the last twenty minutes, and one more than two hours ago.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes rate-cap(5; hour). per-any(hour).\nThis monitor made five probes: four of them within the last twenty minutes, and one more than two hours ago.", "question": "How much room does this monitor have at this point?", "options": ["The full allowance of five is open", "Room for exactly one more", "The statement does not settle it", "None — the cap is already full", "Room for four more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-05-count", "probe": "count", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "count", "N": 5, "scope": "per-identity", "alignment": "per-any", "used_after": 4, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-05-count-renders.1", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four renders in any day; the allowance refills as the day goes by; the day rolls, so any span of one day counts.\nThe night worker made four renders: three of them within the last twenty minutes, and one more than two days ago.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders rate-cap(4; day). per-any(day).\nThe night worker made four renders: three of them within the last twenty minutes, and one more than two days ago.", "question": "How much room does the night worker have at this point?", "options": ["Room for exactly one more", "The full allowance of four is open", "None — the cap is already full", "The statement does not settle it", "Room for three more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-05-count", "probe": "count", "domain": "renders", "scope": "global", "oracle": {"kind": "rate", "probe": "count", "N": 4, "scope": "global", "alignment": "per-any", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-05-count-backfills", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four backfills in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nThis migration job made four backfills: three of them within the last twenty minutes, and one more than two hours ago.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills rate-cap(4; hour). per-any(hour).\nThis migration job made four backfills: three of them within the last twenty minutes, and one more than two hours ago.", "question": "How much room does this migration job have at this point?", "options": ["Room for exactly one more", "None — the cap is already full", "The full allowance of four is open", "The statement does not settle it", "Room for three more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-05-count", "probe": "count", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "count", "N": 4, "scope": "per-identity", "alignment": "per-any", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-05-count-invites", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five invites in any day; the allowance refills as the day goes by; the day rolls, so any span of one day counts.\nThe workspace bot made five invites: four of them within the last twenty minutes, and one more than two days ago.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites rate-cap(5; day). per-any(day).\nThe workspace bot made five invites: four of them within the last twenty minutes, and one more than two days ago.", "question": "How much room does the workspace bot have at this point?", "options": ["None — the cap is already full", "The full allowance of five is open", "Room for four more", "Room for exactly one more", "The statement does not settle it"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-05-count", "probe": "count", "domain": "invites", "scope": "global", "oracle": {"kind": "rate", "probe": "count", "N": 5, "scope": "global", "alignment": "per-any", "used_after": 4, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-05-count-locks", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four locks in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nThis editor made four locks: three of them within the last twenty minutes, and one more than two hours ago.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks rate-cap(4; hour). per-any(hour).\nThis editor made four locks: three of them within the last twenty minutes, and one more than two hours ago.", "question": "How much room does this editor have at this point?", "options": ["The full allowance of four is open", "Room for exactly one more", "None — the cap is already full", "The statement does not settle it", "Room for three more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-05-count", "probe": "count", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "count", "N": 4, "scope": "per-identity", "alignment": "per-any", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-05-count-replays.3", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four replays in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nThe analysis bot made four replays: three of them within the last twenty minutes, and one more than two hours ago.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays rate-cap(4; hour). per-any(hour).\nThe analysis bot made four replays: three of them within the last twenty minutes, and one more than two hours ago.", "question": "How much room does the analysis bot have at this point?", "options": ["None — the cap is already full", "Room for three more", "The full allowance of four is open", "The statement does not settle it", "Room for exactly one more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-05-count", "probe": "count", "domain": "replays", "scope": "global", "oracle": {"kind": "rate", "probe": "count", "N": 4, "scope": "global", "alignment": "per-any", "used_after": 3, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-05-count-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five uploads in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts.\nThis uploader made five uploads: four of them within the last twenty minutes, and one more than two hours ago.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads rate-cap(5; hour). per-any(hour).\nThis uploader made five uploads: four of them within the last twenty minutes, and one more than two hours ago.", "question": "How much room does this uploader have at this point?", "options": ["None — the cap is already full", "The full allowance of five is open", "The statement does not settle it", "Room for exactly one more", "Room for four more"], "answer": "Room for exactly one more", "settlement_stratum": "rate", "frame": "rate-05-count", "probe": "count", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "count", "N": 5, "scope": "per-identity", "alignment": "per-any", "used_after": 4, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-06-existence-tickets.1", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four tickets in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe note states this cap and nothing about how many tickets currently exist.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets rate-cap(4; hour).\nThe note states this cap and nothing about how many tickets currently exist.", "question": "How many tickets exist at this moment?", "options": ["No tickets exist right now", "Exactly four tickets exist right now", "More than four tickets exist right now", "The statement does not settle it", "Fewer than four tickets exist right now"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-06-existence", "probe": "existence", "domain": "tickets", "scope": "global", "oracle": {"kind": "rate", "probe": "existence", "N": 4, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-06-existence-probes", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five probes in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe note states this cap and nothing about how many probes currently exist.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes rate-cap(5; hour).\nThe note states this cap and nothing about how many probes currently exist.", "question": "How many probes exist at this moment?", "options": ["No probes exist right now", "The statement does not settle it", "Exactly five probes exist right now", "More than five probes exist right now", "Fewer than five probes exist right now"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-06-existence", "probe": "existence", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "existence", "N": 5, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-06-existence-renders", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four renders in any day; the allowance refills as the day goes by; the note does not say whether the day follows the clock or rolls.\nThe note states this cap and nothing about how many renders currently exist.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders rate-cap(4; day).\nThe note states this cap and nothing about how many renders currently exist.", "question": "How many renders exist at this moment?", "options": ["Fewer than four renders exist right now", "More than four renders exist right now", "The statement does not settle it", "Exactly four renders exist right now", "No renders exist right now"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-06-existence", "probe": "existence", "domain": "renders", "scope": "global", "oracle": {"kind": "rate", "probe": "existence", "N": 4, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-06-existence-backfills.3", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four backfills in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe note states this cap and nothing about how many backfills currently exist.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills rate-cap(4; hour).\nThe note states this cap and nothing about how many backfills currently exist.", "question": "How many backfills exist at this moment?", "options": ["The statement does not settle it", "Exactly four backfills exist right now", "Fewer than four backfills exist right now", "No backfills exist right now", "More than four backfills exist right now"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-06-existence", "probe": "existence", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "existence", "N": 4, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-06-existence-invites.2", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five invites in any day; the allowance refills as the day goes by; the note does not say whether the day follows the clock or rolls.\nThe note states this cap and nothing about how many invites currently exist.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites rate-cap(5; day).\nThe note states this cap and nothing about how many invites currently exist.", "question": "How many invites exist at this moment?", "options": ["No invites exist right now", "Exactly five invites exist right now", "More than five invites exist right now", "The statement does not settle it", "Fewer than five invites exist right now"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-06-existence", "probe": "existence", "domain": "invites", "scope": "global", "oracle": {"kind": "rate", "probe": "existence", "N": 5, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-06-existence-locks.1", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four locks in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe note states this cap and nothing about how many locks currently exist.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks rate-cap(4; hour).\nThe note states this cap and nothing about how many locks currently exist.", "question": "How many locks exist at this moment?", "options": ["The statement does not settle it", "Fewer than four locks exist right now", "More than four locks exist right now", "No locks exist right now", "Exactly four locks exist right now"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-06-existence", "probe": "existence", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "existence", "N": 4, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-06-existence-replays", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four replays in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe note states this cap and nothing about how many replays currently exist.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays rate-cap(4; hour).\nThe note states this cap and nothing about how many replays currently exist.", "question": "How many replays exist at this moment?", "options": ["More than four replays exist right now", "The statement does not settle it", "Exactly four replays exist right now", "Fewer than four replays exist right now", "No replays exist right now"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-06-existence", "probe": "existence", "domain": "replays", "scope": "global", "oracle": {"kind": "rate", "probe": "existence", "N": 4, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-06-existence-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five uploads in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe note states this cap and nothing about how many uploads currently exist.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads rate-cap(5; hour).\nThe note states this cap and nothing about how many uploads currently exist.", "question": "How many uploads exist at this moment?", "options": ["Fewer than five uploads exist right now", "The statement does not settle it", "Exactly five uploads exist right now", "No uploads exist right now", "More than five uploads exist right now"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-06-existence", "probe": "existence", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "existence", "N": 5, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-07-boundary-tickets", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four tickets in any hour; the allowance refills as the hour goes by; a fresh tally begins with each clock hour.\nClock hour boundaries occur on the hour. The intake bot intends four tickets immediately before such a boundary and four more immediately after it, while nothing else happens nearby.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets rate-cap(4; hour). per-clock(hour).\nClock hour boundaries occur on the hour. The intake bot intends four tickets immediately before such a boundary and four more immediately after it, while nothing else happens nearby.", "question": "May both planned batches go ahead under this cap?", "options": ["The statement does not settle it", "No — the pair cannot both be permitted", "Only the batch before the boundary can be permitted", "Only the batch after the boundary can be permitted", "Yes — the two batches can both be permitted"], "answer": "Yes — the two batches can both be permitted", "settlement_stratum": "rate", "frame": "rate-07-boundary", "probe": "boundary", "domain": "tickets", "scope": "global", "oracle": {"kind": "rate", "probe": "boundary", "N": 4, "scope": "global", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-07-boundary-probes", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five probes in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nClock hour boundaries occur on the hour. This monitor intends five probes immediately before such a boundary and five more immediately after it, while nothing else happens nearby.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes rate-cap(5; hour).\nClock hour boundaries occur on the hour. This monitor intends five probes immediately before such a boundary and five more immediately after it, while nothing else happens nearby.", "question": "May both planned batches go ahead under this cap?", "options": ["Only the batch before the boundary can be permitted", "Only the batch after the boundary can be permitted", "The statement does not settle it", "Yes — the two batches can both be permitted", "No — the pair cannot both be permitted"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-07-boundary", "probe": "boundary", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "boundary", "N": 5, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-07-boundary-renders", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four renders in any day; the allowance refills as the day goes by; a fresh tally begins with each clock day.\nClock day boundaries occur at midnight. The night worker intends four renders immediately before such a boundary and four more immediately after it, while nothing else happens nearby.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders rate-cap(4; day). per-clock(day).\nClock day boundaries occur at midnight. The night worker intends four renders immediately before such a boundary and four more immediately after it, while nothing else happens nearby.", "question": "May both planned batches go ahead under this cap?", "options": ["The statement does not settle it", "No — the pair cannot both be permitted", "Yes — the two batches can both be permitted", "Only the batch after the boundary can be permitted", "Only the batch before the boundary can be permitted"], "answer": "Yes — the two batches can both be permitted", "settlement_stratum": "rate", "frame": "rate-07-boundary", "probe": "boundary", "domain": "renders", "scope": "global", "oracle": {"kind": "rate", "probe": "boundary", "N": 4, "scope": "global", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-07-boundary-backfills", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four backfills in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nClock hour boundaries occur on the hour. This migration job intends four backfills immediately before such a boundary and four more immediately after it, while nothing else happens nearby.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills rate-cap(4; hour).\nClock hour boundaries occur on the hour. This migration job intends four backfills immediately before such a boundary and four more immediately after it, while nothing else happens nearby.", "question": "May both planned batches go ahead under this cap?", "options": ["The statement does not settle it", "Yes — the two batches can both be permitted", "Only the batch before the boundary can be permitted", "No — the pair cannot both be permitted", "Only the batch after the boundary can be permitted"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-07-boundary", "probe": "boundary", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "boundary", "N": 4, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-07-boundary-invites.6", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five invites in any day; the allowance refills as the day goes by; a fresh tally begins with each clock day.\nClock day boundaries occur at midnight. The workspace bot intends five invites immediately before such a boundary and five more immediately after it, while nothing else happens nearby.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites rate-cap(5; day). per-clock(day).\nClock day boundaries occur at midnight. The workspace bot intends five invites immediately before such a boundary and five more immediately after it, while nothing else happens nearby.", "question": "May both planned batches go ahead under this cap?", "options": ["Yes — the two batches can both be permitted", "Only the batch after the boundary can be permitted", "Only the batch before the boundary can be permitted", "No — the pair cannot both be permitted", "The statement does not settle it"], "answer": "Yes — the two batches can both be permitted", "settlement_stratum": "rate", "frame": "rate-07-boundary", "probe": "boundary", "domain": "invites", "scope": "global", "oracle": {"kind": "rate", "probe": "boundary", "N": 5, "scope": "global", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-07-boundary-locks.2", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four locks in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nClock hour boundaries occur on the hour. This editor intends four locks immediately before such a boundary and four more immediately after it, while nothing else happens nearby.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks rate-cap(4; hour).\nClock hour boundaries occur on the hour. This editor intends four locks immediately before such a boundary and four more immediately after it, while nothing else happens nearby.", "question": "May both planned batches go ahead under this cap?", "options": ["Yes — the two batches can both be permitted", "The statement does not settle it", "No — the pair cannot both be permitted", "Only the batch before the boundary can be permitted", "Only the batch after the boundary can be permitted"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-07-boundary", "probe": "boundary", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "boundary", "N": 4, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-07-boundary-replays.4", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four replays in any hour; the allowance refills as the hour goes by; a fresh tally begins with each clock hour.\nClock hour boundaries occur on the hour. The analysis bot intends four replays immediately before such a boundary and four more immediately after it, while nothing else happens nearby.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays rate-cap(4; hour). per-clock(hour).\nClock hour boundaries occur on the hour. The analysis bot intends four replays immediately before such a boundary and four more immediately after it, while nothing else happens nearby.", "question": "May both planned batches go ahead under this cap?", "options": ["Only the batch before the boundary can be permitted", "The statement does not settle it", "No — the pair cannot both be permitted", "Yes — the two batches can both be permitted", "Only the batch after the boundary can be permitted"], "answer": "Yes — the two batches can both be permitted", "settlement_stratum": "rate", "frame": "rate-07-boundary", "probe": "boundary", "domain": "replays", "scope": "global", "oracle": {"kind": "rate", "probe": "boundary", "N": 4, "scope": "global", "alignment": "per-clock", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-07-boundary-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five uploads in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nClock hour boundaries occur on the hour. This uploader intends five uploads immediately before such a boundary and five more immediately after it, while nothing else happens nearby.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads rate-cap(5; hour).\nClock hour boundaries occur on the hour. This uploader intends five uploads immediately before such a boundary and five more immediately after it, while nothing else happens nearby.", "question": "May both planned batches go ahead under this cap?", "options": ["The statement does not settle it", "Yes — the two batches can both be permitted", "Only the batch before the boundary can be permitted", "Only the batch after the boundary can be permitted", "No — the pair cannot both be permitted"], "answer": "The statement does not settle it", "settlement_stratum": "rate", "frame": "rate-07-boundary", "probe": "boundary", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "boundary", "N": 5, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-rate-rate-08-mixed-tickets.1", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four tickets in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than four open tickets at the service desk at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nDuring the hour just before now, the intake bot made four tickets, and the set currently holds four open tickets at the service desk; no member is about to leave.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets rate-cap(4; hour). per-any(hour). tickets stock-cap(4; open tickets at the service desk).\nDuring the hour just before now, the intake bot made four tickets, and the set currently holds four open tickets at the service desk; no member is about to leave.", "question": "How much room is left for one more ticket once both caps apply?", "options": ["Room for exactly one more", "Room for three more", "The statement does not settle it", "The full allowance of four is open", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "rate", "frame": "rate-08-mixed", "probe": "mixed", "domain": "tickets", "scope": "global", "oracle": {"kind": "rate", "probe": "mixed", "N": 4, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 4, "stock_held_after": 4}}, {"id": "a86m-rate-rate-08-mixed-probes", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five probes in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than five probes in flight for this monitor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nDuring the hour just before now, this monitor made five probes, and the set currently holds five probes in flight for this monitor; no member is about to leave.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes rate-cap(5; hour). per-any(hour). probes stock-cap(5; probes in flight for this monitor).\nDuring the hour just before now, this monitor made five probes, and the set currently holds five probes in flight for this monitor; no member is about to leave.", "question": "How much room is left for one more probe once both caps apply?", "options": ["The statement does not settle it", "The full allowance of five is open", "Room for four more", "None — the cap is already full", "Room for exactly one more"], "answer": "None — the cap is already full", "settlement_stratum": "rate", "frame": "rate-08-mixed", "probe": "mixed", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "mixed", "N": 5, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 5, "stock_held_after": 5}}, {"id": "a86m-rate-rate-08-mixed-renders.1", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four renders in any day; the allowance refills as the day goes by; the day rolls, so any span of one day counts. The cap allows no more than four renders queued on the farm at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nDuring the day just before now, the night worker made four renders, and the set currently holds four renders queued on the farm; no member is about to leave.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders rate-cap(4; day). per-any(day). renders stock-cap(4; renders queued on the farm).\nDuring the day just before now, the night worker made four renders, and the set currently holds four renders queued on the farm; no member is about to leave.", "question": "How much room is left for one more render once both caps apply?", "options": ["The statement does not settle it", "Room for three more", "Room for exactly one more", "The full allowance of four is open", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "rate", "frame": "rate-08-mixed", "probe": "mixed", "domain": "renders", "scope": "global", "oracle": {"kind": "rate", "probe": "mixed", "N": 4, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 4, "stock_held_after": 4}}, {"id": "a86m-rate-rate-08-mixed-backfills.1", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four backfills in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than four backfills running for this job at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nDuring the hour just before now, this migration job made four backfills, and the set currently holds four backfills running for this job; no member is about to leave.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills rate-cap(4; hour). per-any(hour). backfills stock-cap(4; backfills running for this job).\nDuring the hour just before now, this migration job made four backfills, and the set currently holds four backfills running for this job; no member is about to leave.", "question": "How much room is left for one more backfill once both caps apply?", "options": ["None — the cap is already full", "Room for exactly one more", "The statement does not settle it", "Room for three more", "The full allowance of four is open"], "answer": "None — the cap is already full", "settlement_stratum": "rate", "frame": "rate-08-mixed", "probe": "mixed", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "mixed", "N": 4, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 4, "stock_held_after": 4}}, {"id": "a86m-rate-rate-08-mixed-invites.2", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five invites in any day; the allowance refills as the day goes by; the day rolls, so any span of one day counts. The cap allows no more than five invites outstanding in the workspace at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nDuring the day just before now, the workspace bot made five invites, and the set currently holds five invites outstanding in the workspace; no member is about to leave.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites rate-cap(5; day). per-any(day). invites stock-cap(5; invites outstanding in the workspace).\nDuring the day just before now, the workspace bot made five invites, and the set currently holds five invites outstanding in the workspace; no member is about to leave.", "question": "How much room is left for one more invite once both caps apply?", "options": ["The statement does not settle it", "The full allowance of five is open", "None — the cap is already full", "Room for four more", "Room for exactly one more"], "answer": "None — the cap is already full", "settlement_stratum": "rate", "frame": "rate-08-mixed", "probe": "mixed", "domain": "invites", "scope": "global", "oracle": {"kind": "rate", "probe": "mixed", "N": 5, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 5, "stock_held_after": 5}}, {"id": "a86m-rate-rate-08-mixed-locks.2", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four locks in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than four locks held by this editor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nDuring the hour just before now, this editor made four locks, and the set currently holds four locks held by this editor; no member is about to leave.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks rate-cap(4; hour). per-any(hour). locks stock-cap(4; locks held by this editor).\nDuring the hour just before now, this editor made four locks, and the set currently holds four locks held by this editor; no member is about to leave.", "question": "How much room is left for one more lock once both caps apply?", "options": ["The full allowance of four is open", "The statement does not settle it", "Room for three more", "None — the cap is already full", "Room for exactly one more"], "answer": "None — the cap is already full", "settlement_stratum": "rate", "frame": "rate-08-mixed", "probe": "mixed", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "mixed", "N": 4, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 4, "stock_held_after": 4}}, {"id": "a86m-rate-rate-08-mixed-replays", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most four replays in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than four replays queued on the cluster at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nDuring the hour just before now, the analysis bot made four replays, and the set currently holds four replays queued on the cluster; no member is about to leave.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays rate-cap(4; hour). per-any(hour). replays stock-cap(4; replays queued on the cluster).\nDuring the hour just before now, the analysis bot made four replays, and the set currently holds four replays queued on the cluster; no member is about to leave.", "question": "How much room is left for one more replay once both caps apply?", "options": ["The full allowance of four is open", "Room for three more", "The statement does not settle it", "Room for exactly one more", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "rate", "frame": "rate-08-mixed", "probe": "mixed", "domain": "replays", "scope": "global", "oracle": {"kind": "rate", "probe": "mixed", "N": 4, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 4, "stock_held_after": 4}}, {"id": "a86m-rate-rate-08-mixed-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most five uploads in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than five uploads unfinished for this account at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nDuring the hour just before now, this uploader made five uploads, and the set currently holds five uploads unfinished for this account; no member is about to leave.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads rate-cap(5; hour). per-any(hour). uploads stock-cap(5; uploads unfinished for this account).\nDuring the hour just before now, this uploader made five uploads, and the set currently holds five uploads unfinished for this account; no member is about to leave.", "question": "How much room is left for one more upload once both caps apply?", "options": ["Room for four more", "The full allowance of five is open", "None — the cap is already full", "The statement does not settle it", "Room for exactly one more"], "answer": "None — the cap is already full", "settlement_stratum": "rate", "frame": "rate-08-mixed", "probe": "mixed", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "rate", "probe": "mixed", "N": 5, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 5, "stock_held_after": 5}}, {"id": "a86m-stock-stock-01-wait-tickets", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three open tickets at the service desk at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three open tickets at the service desk. The intake bot idles for twenty minutes without acting; set membership is unchanged.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets stock-cap(3; open tickets at the service desk).\nThe set currently holds three open tickets at the service desk. The intake bot idles for twenty minutes without acting; set membership is unchanged.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["The statement does not settle it", "Room for two more", "Room for exactly one more", "The full allowance of three is open", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-01-wait", "probe": "wait", "domain": "tickets", "scope": "global", "oracle": {"kind": "stock", "probe": "wait", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-01-wait-probes.1", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three probes in flight for this monitor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three probes in flight for this monitor. This monitor idles for twenty minutes without acting; set membership is unchanged.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes stock-cap(3; probes in flight for this monitor).\nThe set currently holds three probes in flight for this monitor. This monitor idles for twenty minutes without acting; set membership is unchanged.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["The statement does not settle it", "None — the cap is already full", "Room for two more", "Room for exactly one more", "The full allowance of three is open"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-01-wait", "probe": "wait", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "wait", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-01-wait-renders.1", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three renders queued on the farm at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three renders queued on the farm. The night worker idles for twenty minutes without acting; set membership is unchanged.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders stock-cap(3; renders queued on the farm).\nThe set currently holds three renders queued on the farm. The night worker idles for twenty minutes without acting; set membership is unchanged.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["The statement does not settle it", "Room for two more", "The full allowance of three is open", "None — the cap is already full", "Room for exactly one more"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-01-wait", "probe": "wait", "domain": "renders", "scope": "global", "oracle": {"kind": "stock", "probe": "wait", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-01-wait-backfills", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three backfills running for this job at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three backfills running for this job. This migration job idles for twenty minutes without acting; set membership is unchanged.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills stock-cap(3; backfills running for this job).\nThe set currently holds three backfills running for this job. This migration job idles for twenty minutes without acting; set membership is unchanged.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["Room for exactly one more", "Room for two more", "The full allowance of three is open", "The statement does not settle it", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-01-wait", "probe": "wait", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "wait", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-01-wait-invites.3", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three invites outstanding in the workspace at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three invites outstanding in the workspace. The workspace bot idles for twenty minutes without acting; set membership is unchanged.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites stock-cap(3; invites outstanding in the workspace).\nThe set currently holds three invites outstanding in the workspace. The workspace bot idles for twenty minutes without acting; set membership is unchanged.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["Room for two more", "The statement does not settle it", "The full allowance of three is open", "Room for exactly one more", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-01-wait", "probe": "wait", "domain": "invites", "scope": "global", "oracle": {"kind": "stock", "probe": "wait", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-01-wait-locks.1", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three locks held by this editor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three locks held by this editor. This editor idles for twenty minutes without acting; set membership is unchanged.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks stock-cap(3; locks held by this editor).\nThe set currently holds three locks held by this editor. This editor idles for twenty minutes without acting; set membership is unchanged.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["The statement does not settle it", "Room for two more", "Room for exactly one more", "None — the cap is already full", "The full allowance of three is open"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-01-wait", "probe": "wait", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "wait", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-01-wait-replays", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three replays queued on the cluster at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three replays queued on the cluster. The analysis bot idles for twenty minutes without acting; set membership is unchanged.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays stock-cap(3; replays queued on the cluster).\nThe set currently holds three replays queued on the cluster. The analysis bot idles for twenty minutes without acting; set membership is unchanged.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["The statement does not settle it", "Room for exactly one more", "The full allowance of three is open", "Room for two more", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-01-wait", "probe": "wait", "domain": "replays", "scope": "global", "oracle": {"kind": "stock", "probe": "wait", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-01-wait-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three uploads unfinished for this account at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three uploads unfinished for this account. This uploader idles for twenty minutes without acting; set membership is unchanged.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads stock-cap(3; uploads unfinished for this account).\nThe set currently holds three uploads unfinished for this account. This uploader idles for twenty minutes without acting; set membership is unchanged.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["None — the cap is already full", "Room for two more", "Room for exactly one more", "The statement does not settle it", "The full allowance of three is open"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-01-wait", "probe": "wait", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "wait", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-02-expiry-tickets", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three open tickets at the service desk at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three open tickets at the service desk; one member will drop out of the set in twenty minutes. The intake bot idles for twenty minutes and takes no action.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets stock-cap(3; open tickets at the service desk).\nThe set currently holds three open tickets at the service desk; one member will drop out of the set in twenty minutes. The intake bot idles for twenty minutes and takes no action.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["Room for exactly one more", "The full allowance of three is open", "The statement does not settle it", "None — the cap is already full", "Room for two more"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-02-expiry", "probe": "expiry", "domain": "tickets", "scope": "global", "oracle": {"kind": "stock", "probe": "expiry", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-02-expiry-probes.3", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three probes in flight for this monitor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three probes in flight for this monitor; one member will drop out of the set in twenty minutes. This monitor idles for twenty minutes and takes no action.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes stock-cap(3; probes in flight for this monitor).\nThe set currently holds three probes in flight for this monitor; one member will drop out of the set in twenty minutes. This monitor idles for twenty minutes and takes no action.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["Room for exactly one more", "The full allowance of three is open", "The statement does not settle it", "None — the cap is already full", "Room for two more"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-02-expiry", "probe": "expiry", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "expiry", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-02-expiry-renders.2", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three renders queued on the farm at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three renders queued on the farm; one member will drop out of the set in twenty minutes. The night worker idles for twenty minutes and takes no action.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders stock-cap(3; renders queued on the farm).\nThe set currently holds three renders queued on the farm; one member will drop out of the set in twenty minutes. The night worker idles for twenty minutes and takes no action.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["Room for two more", "The full allowance of three is open", "None — the cap is already full", "Room for exactly one more", "The statement does not settle it"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-02-expiry", "probe": "expiry", "domain": "renders", "scope": "global", "oracle": {"kind": "stock", "probe": "expiry", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-02-expiry-backfills.5", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three backfills running for this job at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three backfills running for this job; one member will drop out of the set in twenty minutes. This migration job idles for twenty minutes and takes no action.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills stock-cap(3; backfills running for this job).\nThe set currently holds three backfills running for this job; one member will drop out of the set in twenty minutes. This migration job idles for twenty minutes and takes no action.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["None — the cap is already full", "The statement does not settle it", "The full allowance of three is open", "Room for two more", "Room for exactly one more"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-02-expiry", "probe": "expiry", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "expiry", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-02-expiry-invites", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three invites outstanding in the workspace at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three invites outstanding in the workspace; one member will drop out of the set in twenty minutes. The workspace bot idles for twenty minutes and takes no action.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites stock-cap(3; invites outstanding in the workspace).\nThe set currently holds three invites outstanding in the workspace; one member will drop out of the set in twenty minutes. The workspace bot idles for twenty minutes and takes no action.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["None — the cap is already full", "Room for two more", "The statement does not settle it", "Room for exactly one more", "The full allowance of three is open"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-02-expiry", "probe": "expiry", "domain": "invites", "scope": "global", "oracle": {"kind": "stock", "probe": "expiry", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-02-expiry-locks", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three locks held by this editor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three locks held by this editor; one member will drop out of the set in twenty minutes. This editor idles for twenty minutes and takes no action.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks stock-cap(3; locks held by this editor).\nThe set currently holds three locks held by this editor; one member will drop out of the set in twenty minutes. This editor idles for twenty minutes and takes no action.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["The full allowance of three is open", "The statement does not settle it", "None — the cap is already full", "Room for exactly one more", "Room for two more"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-02-expiry", "probe": "expiry", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "expiry", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-02-expiry-replays", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three replays queued on the cluster at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three replays queued on the cluster; one member will drop out of the set in twenty minutes. The analysis bot idles for twenty minutes and takes no action.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays stock-cap(3; replays queued on the cluster).\nThe set currently holds three replays queued on the cluster; one member will drop out of the set in twenty minutes. The analysis bot idles for twenty minutes and takes no action.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["Room for two more", "The full allowance of three is open", "None — the cap is already full", "The statement does not settle it", "Room for exactly one more"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-02-expiry", "probe": "expiry", "domain": "replays", "scope": "global", "oracle": {"kind": "stock", "probe": "expiry", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-02-expiry-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three uploads unfinished for this account at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set currently holds three uploads unfinished for this account; one member will drop out of the set in twenty minutes. This uploader idles for twenty minutes and takes no action.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads stock-cap(3; uploads unfinished for this account).\nThe set currently holds three uploads unfinished for this account; one member will drop out of the set in twenty minutes. This uploader idles for twenty minutes and takes no action.", "question": "When those twenty minutes have elapsed, what room remains under the cap?", "options": ["The statement does not settle it", "Room for exactly one more", "The full allowance of three is open", "Room for two more", "None — the cap is already full"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-02-expiry", "probe": "expiry", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "expiry", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-03-release-tickets", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three open tickets at the service desk at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held two tickets. From T0 to T1 the intake bot let one go; the rest was untouched.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets stock-cap(3; open tickets at the service desk).\nAt T0 the set held two tickets. From T0 to T1 the intake bot let one go; the rest was untouched.", "question": "What room is left at T1, right after that release?", "options": ["The statement does not settle it", "The full allowance of three is open", "Room for exactly one more", "None — the cap is already full", "Room for two more"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-03-release", "probe": "release", "domain": "tickets", "scope": "global", "oracle": {"kind": "stock", "probe": "release", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-03-release-probes.1", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three probes in flight for this monitor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held two probes. From T0 to T1 this monitor let one go; the rest was untouched.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes stock-cap(3; probes in flight for this monitor).\nAt T0 the set held two probes. From T0 to T1 this monitor let one go; the rest was untouched.", "question": "What room is left at T1, right after that release?", "options": ["Room for exactly one more", "The full allowance of three is open", "Room for two more", "None — the cap is already full", "The statement does not settle it"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-03-release", "probe": "release", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "release", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-03-release-renders.1", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three renders queued on the farm at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held two renders. From T0 to T1 the night worker let one go; the rest was untouched.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders stock-cap(3; renders queued on the farm).\nAt T0 the set held two renders. From T0 to T1 the night worker let one go; the rest was untouched.", "question": "What room is left at T1, right after that release?", "options": ["None — the cap is already full", "Room for exactly one more", "The full allowance of three is open", "Room for two more", "The statement does not settle it"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-03-release", "probe": "release", "domain": "renders", "scope": "global", "oracle": {"kind": "stock", "probe": "release", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-03-release-backfills", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three backfills running for this job at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held two backfills. From T0 to T1 this migration job let one go; the rest was untouched.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills stock-cap(3; backfills running for this job).\nAt T0 the set held two backfills. From T0 to T1 this migration job let one go; the rest was untouched.", "question": "What room is left at T1, right after that release?", "options": ["The statement does not settle it", "None — the cap is already full", "The full allowance of three is open", "Room for two more", "Room for exactly one more"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-03-release", "probe": "release", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "release", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-03-release-invites.2", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three invites outstanding in the workspace at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held two invites. From T0 to T1 the workspace bot let one go; the rest was untouched.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites stock-cap(3; invites outstanding in the workspace).\nAt T0 the set held two invites. From T0 to T1 the workspace bot let one go; the rest was untouched.", "question": "What room is left at T1, right after that release?", "options": ["None — the cap is already full", "Room for two more", "Room for exactly one more", "The full allowance of three is open", "The statement does not settle it"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-03-release", "probe": "release", "domain": "invites", "scope": "global", "oracle": {"kind": "stock", "probe": "release", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-03-release-locks.1", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three locks held by this editor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held two locks. From T0 to T1 this editor let one go; the rest was untouched.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks stock-cap(3; locks held by this editor).\nAt T0 the set held two locks. From T0 to T1 this editor let one go; the rest was untouched.", "question": "What room is left at T1, right after that release?", "options": ["Room for exactly one more", "Room for two more", "The statement does not settle it", "The full allowance of three is open", "None — the cap is already full"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-03-release", "probe": "release", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "release", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-03-release-replays.6", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three replays queued on the cluster at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held two replays. From T0 to T1 the analysis bot let one go; the rest was untouched.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays stock-cap(3; replays queued on the cluster).\nAt T0 the set held two replays. From T0 to T1 the analysis bot let one go; the rest was untouched.", "question": "What room is left at T1, right after that release?", "options": ["Room for exactly one more", "The statement does not settle it", "None — the cap is already full", "The full allowance of three is open", "Room for two more"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-03-release", "probe": "release", "domain": "replays", "scope": "global", "oracle": {"kind": "stock", "probe": "release", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-03-release-uploads.1", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three uploads unfinished for this account at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held two uploads. From T0 to T1 this uploader let one go; the rest was untouched.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads stock-cap(3; uploads unfinished for this account).\nAt T0 the set held two uploads. From T0 to T1 this uploader let one go; the rest was untouched.", "question": "What room is left at T1, right after that release?", "options": ["The statement does not settle it", "None — the cap is already full", "The full allowance of three is open", "Room for two more", "Room for exactly one more"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-03-release", "probe": "release", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "release", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-04-delete-member-tickets", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three open tickets at the service desk at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three tickets, and six archived tickets sat outside it. From T0 to T1 the intake bot removed one member of the set; the rest was untouched.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets stock-cap(3; open tickets at the service desk).\nAt T0 the set held three tickets, and six archived tickets sat outside it. From T0 to T1 the intake bot removed one member of the set; the rest was untouched.", "question": "What room is left at T1, right after that deletion?", "options": ["Room for exactly one more", "None — the cap is already full", "Room for two more", "The full allowance of three is open", "The statement does not settle it"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-04-delete-member", "probe": "delete-member", "domain": "tickets", "scope": "global", "oracle": {"kind": "stock", "probe": "delete-member", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-04-delete-member-probes", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three probes in flight for this monitor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three probes, and six archived probes sat outside it. From T0 to T1 this monitor removed one member of the set; the rest was untouched.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes stock-cap(3; probes in flight for this monitor).\nAt T0 the set held three probes, and six archived probes sat outside it. From T0 to T1 this monitor removed one member of the set; the rest was untouched.", "question": "What room is left at T1, right after that deletion?", "options": ["The statement does not settle it", "Room for two more", "None — the cap is already full", "The full allowance of three is open", "Room for exactly one more"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-04-delete-member", "probe": "delete-member", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "delete-member", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-04-delete-member-renders", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three renders queued on the farm at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three renders, and six archived renders sat outside it. From T0 to T1 the night worker removed one member of the set; the rest was untouched.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders stock-cap(3; renders queued on the farm).\nAt T0 the set held three renders, and six archived renders sat outside it. From T0 to T1 the night worker removed one member of the set; the rest was untouched.", "question": "What room is left at T1, right after that deletion?", "options": ["Room for two more", "The statement does not settle it", "The full allowance of three is open", "Room for exactly one more", "None — the cap is already full"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-04-delete-member", "probe": "delete-member", "domain": "renders", "scope": "global", "oracle": {"kind": "stock", "probe": "delete-member", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-04-delete-member-backfills.1", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three backfills running for this job at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three backfills, and six archived backfills sat outside it. From T0 to T1 this migration job removed one member of the set; the rest was untouched.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills stock-cap(3; backfills running for this job).\nAt T0 the set held three backfills, and six archived backfills sat outside it. From T0 to T1 this migration job removed one member of the set; the rest was untouched.", "question": "What room is left at T1, right after that deletion?", "options": ["None — the cap is already full", "The full allowance of three is open", "The statement does not settle it", "Room for exactly one more", "Room for two more"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-04-delete-member", "probe": "delete-member", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "delete-member", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-04-delete-member-invites", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three invites outstanding in the workspace at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three invites, and six archived invites sat outside it. From T0 to T1 the workspace bot removed one member of the set; the rest was untouched.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites stock-cap(3; invites outstanding in the workspace).\nAt T0 the set held three invites, and six archived invites sat outside it. From T0 to T1 the workspace bot removed one member of the set; the rest was untouched.", "question": "What room is left at T1, right after that deletion?", "options": ["None — the cap is already full", "Room for two more", "The statement does not settle it", "The full allowance of three is open", "Room for exactly one more"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-04-delete-member", "probe": "delete-member", "domain": "invites", "scope": "global", "oracle": {"kind": "stock", "probe": "delete-member", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-04-delete-member-locks", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three locks held by this editor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three locks, and six archived locks sat outside it. From T0 to T1 this editor removed one member of the set; the rest was untouched.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks stock-cap(3; locks held by this editor).\nAt T0 the set held three locks, and six archived locks sat outside it. From T0 to T1 this editor removed one member of the set; the rest was untouched.", "question": "What room is left at T1, right after that deletion?", "options": ["None — the cap is already full", "Room for exactly one more", "The statement does not settle it", "The full allowance of three is open", "Room for two more"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-04-delete-member", "probe": "delete-member", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "delete-member", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-04-delete-member-replays", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three replays queued on the cluster at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three replays, and six archived replays sat outside it. From T0 to T1 the analysis bot removed one member of the set; the rest was untouched.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays stock-cap(3; replays queued on the cluster).\nAt T0 the set held three replays, and six archived replays sat outside it. From T0 to T1 the analysis bot removed one member of the set; the rest was untouched.", "question": "What room is left at T1, right after that deletion?", "options": ["None — the cap is already full", "Room for exactly one more", "The statement does not settle it", "The full allowance of three is open", "Room for two more"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-04-delete-member", "probe": "delete-member", "domain": "replays", "scope": "global", "oracle": {"kind": "stock", "probe": "delete-member", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-04-delete-member-uploads.5", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three uploads unfinished for this account at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three uploads, and six archived uploads sat outside it. From T0 to T1 this uploader removed one member of the set; the rest was untouched.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads stock-cap(3; uploads unfinished for this account).\nAt T0 the set held three uploads, and six archived uploads sat outside it. From T0 to T1 this uploader removed one member of the set; the rest was untouched.", "question": "What room is left at T1, right after that deletion?", "options": ["The full allowance of three is open", "None — the cap is already full", "Room for exactly one more", "Room for two more", "The statement does not settle it"], "answer": "Room for exactly one more", "settlement_stratum": "stock", "frame": "stock-04-delete-member", "probe": "delete-member", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "delete-member", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 2, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-05-delete-other-tickets.3", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three open tickets at the service desk at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three tickets, and six archived tickets sat outside it. From T0 to T1 the intake bot removed one of the archived tickets, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets stock-cap(3; open tickets at the service desk).\nAt T0 the set held three tickets, and six archived tickets sat outside it. From T0 to T1 the intake bot removed one of the archived tickets, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "question": "What room is left at T1, right after that deletion?", "options": ["The statement does not settle it", "Room for two more", "Room for exactly one more", "The full allowance of three is open", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-05-delete-other", "probe": "delete-other", "domain": "tickets", "scope": "global", "oracle": {"kind": "stock", "probe": "delete-other", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-05-delete-other-probes", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three probes in flight for this monitor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three probes, and six archived probes sat outside it. From T0 to T1 this monitor removed one of the archived probes, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes stock-cap(3; probes in flight for this monitor).\nAt T0 the set held three probes, and six archived probes sat outside it. From T0 to T1 this monitor removed one of the archived probes, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "question": "What room is left at T1, right after that deletion?", "options": ["The statement does not settle it", "Room for exactly one more", "Room for two more", "None — the cap is already full", "The full allowance of three is open"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-05-delete-other", "probe": "delete-other", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "delete-other", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-05-delete-other-renders", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three renders queued on the farm at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three renders, and six archived renders sat outside it. From T0 to T1 the night worker removed one of the archived renders, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders stock-cap(3; renders queued on the farm).\nAt T0 the set held three renders, and six archived renders sat outside it. From T0 to T1 the night worker removed one of the archived renders, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "question": "What room is left at T1, right after that deletion?", "options": ["Room for exactly one more", "The full allowance of three is open", "Room for two more", "The statement does not settle it", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-05-delete-other", "probe": "delete-other", "domain": "renders", "scope": "global", "oracle": {"kind": "stock", "probe": "delete-other", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-05-delete-other-backfills", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three backfills running for this job at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three backfills, and six archived backfills sat outside it. From T0 to T1 this migration job removed one of the archived backfills, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills stock-cap(3; backfills running for this job).\nAt T0 the set held three backfills, and six archived backfills sat outside it. From T0 to T1 this migration job removed one of the archived backfills, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "question": "What room is left at T1, right after that deletion?", "options": ["Room for two more", "Room for exactly one more", "The statement does not settle it", "None — the cap is already full", "The full allowance of three is open"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-05-delete-other", "probe": "delete-other", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "delete-other", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-05-delete-other-invites", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three invites outstanding in the workspace at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three invites, and six archived invites sat outside it. From T0 to T1 the workspace bot removed one of the archived invites, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites stock-cap(3; invites outstanding in the workspace).\nAt T0 the set held three invites, and six archived invites sat outside it. From T0 to T1 the workspace bot removed one of the archived invites, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "question": "What room is left at T1, right after that deletion?", "options": ["The statement does not settle it", "None — the cap is already full", "The full allowance of three is open", "Room for exactly one more", "Room for two more"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-05-delete-other", "probe": "delete-other", "domain": "invites", "scope": "global", "oracle": {"kind": "stock", "probe": "delete-other", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-05-delete-other-locks", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three locks held by this editor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three locks, and six archived locks sat outside it. From T0 to T1 this editor removed one of the archived locks, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks stock-cap(3; locks held by this editor).\nAt T0 the set held three locks, and six archived locks sat outside it. From T0 to T1 this editor removed one of the archived locks, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "question": "What room is left at T1, right after that deletion?", "options": ["The statement does not settle it", "The full allowance of three is open", "Room for exactly one more", "None — the cap is already full", "Room for two more"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-05-delete-other", "probe": "delete-other", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "delete-other", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-05-delete-other-replays", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three replays queued on the cluster at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three replays, and six archived replays sat outside it. From T0 to T1 the analysis bot removed one of the archived replays, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays stock-cap(3; replays queued on the cluster).\nAt T0 the set held three replays, and six archived replays sat outside it. From T0 to T1 the analysis bot removed one of the archived replays, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "question": "What room is left at T1, right after that deletion?", "options": ["The statement does not settle it", "Room for two more", "The full allowance of three is open", "Room for exactly one more", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-05-delete-other", "probe": "delete-other", "domain": "replays", "scope": "global", "oracle": {"kind": "stock", "probe": "delete-other", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-05-delete-other-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three uploads unfinished for this account at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nAt T0 the set held three uploads, and six archived uploads sat outside it. From T0 to T1 this uploader removed one of the archived uploads, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads stock-cap(3; uploads unfinished for this account).\nAt T0 the set held three uploads, and six archived uploads sat outside it. From T0 to T1 this uploader removed one of the archived uploads, never a set member. The clearance to proceed was cancelled earlier today and not reinstated.", "question": "What room is left at T1, right after that deletion?", "options": ["The statement does not settle it", "Room for two more", "Room for exactly one more", "The full allowance of three is open", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-05-delete-other", "probe": "delete-other", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "delete-other", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-06-scope-tickets.4", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three open tickets at the service desk at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set holds one ticket for the intake bot and two more for another actor; all three are inside the shared set. Nothing changes.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets stock-cap(3; open tickets at the service desk).\nThe set holds one ticket for the intake bot and two more for another actor; all three are inside the shared set. Nothing changes.", "question": "How much room does the intake bot have now?", "options": ["The full allowance of three is open", "The statement does not settle it", "Room for exactly one more", "Room for two more", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-06-scope", "probe": "scope", "domain": "tickets", "scope": "global", "oracle": {"kind": "stock", "probe": "scope", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-06-scope-probes", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three probes in flight for this monitor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set holds one probe for this monitor; another actor keeps two more of the same kind outside this monitor's set. Nothing changes.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes stock-cap(3; probes in flight for this monitor).\nThe set holds one probe for this monitor; another actor keeps two more of the same kind outside this monitor's set. Nothing changes.", "question": "How much room does this monitor have now?", "options": ["None — the cap is already full", "Room for two more", "The full allowance of three is open", "The statement does not settle it", "Room for exactly one more"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-06-scope", "probe": "scope", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "scope", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-06-scope-renders", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three renders queued on the farm at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set holds one render for the night worker and two more for another actor; all three are inside the shared set. Nothing changes.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders stock-cap(3; renders queued on the farm).\nThe set holds one render for the night worker and two more for another actor; all three are inside the shared set. Nothing changes.", "question": "How much room does the night worker have now?", "options": ["The full allowance of three is open", "None — the cap is already full", "Room for two more", "Room for exactly one more", "The statement does not settle it"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-06-scope", "probe": "scope", "domain": "renders", "scope": "global", "oracle": {"kind": "stock", "probe": "scope", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-06-scope-backfills.1", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three backfills running for this job at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set holds one backfill for this migration job; another actor keeps two more of the same kind outside this migration job's set. Nothing changes.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills stock-cap(3; backfills running for this job).\nThe set holds one backfill for this migration job; another actor keeps two more of the same kind outside this migration job's set. Nothing changes.", "question": "How much room does this migration job have now?", "options": ["None — the cap is already full", "Room for exactly one more", "The statement does not settle it", "Room for two more", "The full allowance of three is open"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-06-scope", "probe": "scope", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "scope", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-06-scope-invites", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three invites outstanding in the workspace at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set holds one invite for the workspace bot and two more for another actor; all three are inside the shared set. Nothing changes.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites stock-cap(3; invites outstanding in the workspace).\nThe set holds one invite for the workspace bot and two more for another actor; all three are inside the shared set. Nothing changes.", "question": "How much room does the workspace bot have now?", "options": ["Room for exactly one more", "The statement does not settle it", "None — the cap is already full", "Room for two more", "The full allowance of three is open"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-06-scope", "probe": "scope", "domain": "invites", "scope": "global", "oracle": {"kind": "stock", "probe": "scope", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-06-scope-locks.1", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three locks held by this editor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set holds one lock for this editor; another actor keeps two more of the same kind outside this editor's set. Nothing changes.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks stock-cap(3; locks held by this editor).\nThe set holds one lock for this editor; another actor keeps two more of the same kind outside this editor's set. Nothing changes.", "question": "How much room does this editor have now?", "options": ["Room for two more", "None — the cap is already full", "Room for exactly one more", "The statement does not settle it", "The full allowance of three is open"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-06-scope", "probe": "scope", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "scope", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-06-scope-replays", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three replays queued on the cluster at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set holds one replay for the analysis bot and two more for another actor; all three are inside the shared set. Nothing changes.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays stock-cap(3; replays queued on the cluster).\nThe set holds one replay for the analysis bot and two more for another actor; all three are inside the shared set. Nothing changes.", "question": "How much room does the analysis bot have now?", "options": ["Room for exactly one more", "The statement does not settle it", "None — the cap is already full", "The full allowance of three is open", "Room for two more"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-06-scope", "probe": "scope", "domain": "replays", "scope": "global", "oracle": {"kind": "stock", "probe": "scope", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 3, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-06-scope-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three uploads unfinished for this account at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe set holds one upload for this uploader; another actor keeps two more of the same kind outside this uploader's set. Nothing changes.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads stock-cap(3; uploads unfinished for this account).\nThe set holds one upload for this uploader; another actor keeps two more of the same kind outside this uploader's set. Nothing changes.", "question": "How much room does this uploader have now?", "options": ["The full allowance of three is open", "Room for two more", "None — the cap is already full", "Room for exactly one more", "The statement does not settle it"], "answer": "Room for two more", "settlement_stratum": "stock", "frame": "stock-06-scope", "probe": "scope", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "scope", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 1, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-07-existence-tickets.2", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three open tickets at the service desk at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe note states this cap and nothing about how many tickets the set currently holds.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets stock-cap(3; open tickets at the service desk).\nThe note states this cap and nothing about how many tickets the set currently holds.", "question": "How many tickets are in the set at this moment?", "options": ["No tickets are in the set right now", "More than three tickets are in the set right now", "Fewer than three tickets are in the set right now", "The statement does not settle it", "Exactly three tickets are in the set right now"], "answer": "The statement does not settle it", "settlement_stratum": "stock", "frame": "stock-07-existence", "probe": "existence", "domain": "tickets", "scope": "global", "oracle": {"kind": "stock", "probe": "existence", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-07-existence-probes.1", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three probes in flight for this monitor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe note states this cap and nothing about how many probes the set currently holds.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes stock-cap(3; probes in flight for this monitor).\nThe note states this cap and nothing about how many probes the set currently holds.", "question": "How many probes are in the set at this moment?", "options": ["The statement does not settle it", "No probes are in the set right now", "Fewer than three probes are in the set right now", "Exactly three probes are in the set right now", "More than three probes are in the set right now"], "answer": "The statement does not settle it", "settlement_stratum": "stock", "frame": "stock-07-existence", "probe": "existence", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "existence", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-07-existence-renders.1", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three renders queued on the farm at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe note states this cap and nothing about how many renders the set currently holds.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders stock-cap(3; renders queued on the farm).\nThe note states this cap and nothing about how many renders the set currently holds.", "question": "How many renders are in the set at this moment?", "options": ["Exactly three renders are in the set right now", "The statement does not settle it", "More than three renders are in the set right now", "No renders are in the set right now", "Fewer than three renders are in the set right now"], "answer": "The statement does not settle it", "settlement_stratum": "stock", "frame": "stock-07-existence", "probe": "existence", "domain": "renders", "scope": "global", "oracle": {"kind": "stock", "probe": "existence", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-07-existence-backfills.2", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three backfills running for this job at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe note states this cap and nothing about how many backfills the set currently holds.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills stock-cap(3; backfills running for this job).\nThe note states this cap and nothing about how many backfills the set currently holds.", "question": "How many backfills are in the set at this moment?", "options": ["No backfills are in the set right now", "Exactly three backfills are in the set right now", "Fewer than three backfills are in the set right now", "The statement does not settle it", "More than three backfills are in the set right now"], "answer": "The statement does not settle it", "settlement_stratum": "stock", "frame": "stock-07-existence", "probe": "existence", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "existence", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-07-existence-invites.1", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three invites outstanding in the workspace at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe note states this cap and nothing about how many invites the set currently holds.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites stock-cap(3; invites outstanding in the workspace).\nThe note states this cap and nothing about how many invites the set currently holds.", "question": "How many invites are in the set at this moment?", "options": ["Fewer than three invites are in the set right now", "The statement does not settle it", "No invites are in the set right now", "Exactly three invites are in the set right now", "More than three invites are in the set right now"], "answer": "The statement does not settle it", "settlement_stratum": "stock", "frame": "stock-07-existence", "probe": "existence", "domain": "invites", "scope": "global", "oracle": {"kind": "stock", "probe": "existence", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-07-existence-locks", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three locks held by this editor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe note states this cap and nothing about how many locks the set currently holds.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks stock-cap(3; locks held by this editor).\nThe note states this cap and nothing about how many locks the set currently holds.", "question": "How many locks are in the set at this moment?", "options": ["The statement does not settle it", "Fewer than three locks are in the set right now", "Exactly three locks are in the set right now", "More than three locks are in the set right now", "No locks are in the set right now"], "answer": "The statement does not settle it", "settlement_stratum": "stock", "frame": "stock-07-existence", "probe": "existence", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "existence", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-07-existence-replays.1", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three replays queued on the cluster at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe note states this cap and nothing about how many replays the set currently holds.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays stock-cap(3; replays queued on the cluster).\nThe note states this cap and nothing about how many replays the set currently holds.", "question": "How many replays are in the set at this moment?", "options": ["The statement does not settle it", "More than three replays are in the set right now", "Exactly three replays are in the set right now", "No replays are in the set right now", "Fewer than three replays are in the set right now"], "answer": "The statement does not settle it", "settlement_stratum": "stock", "frame": "stock-07-existence", "probe": "existence", "domain": "replays", "scope": "global", "oracle": {"kind": "stock", "probe": "existence", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-07-existence-uploads.1", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than three uploads unfinished for this account at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe note states this cap and nothing about how many uploads the set currently holds.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads stock-cap(3; uploads unfinished for this account).\nThe note states this cap and nothing about how many uploads the set currently holds.", "question": "How many uploads are in the set at this moment?", "options": ["More than three uploads are in the set right now", "Fewer than three uploads are in the set right now", "No uploads are in the set right now", "Exactly three uploads are in the set right now", "The statement does not settle it"], "answer": "The statement does not settle it", "settlement_stratum": "stock", "frame": "stock-07-existence", "probe": "existence", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "existence", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 0, "stock_held_after": 0}}, {"id": "a86m-stock-stock-08-mixed-tickets", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three tickets in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than three open tickets at the service desk at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nBetween two hours back and one hour back, the intake bot made three tickets; nothing since. The set currently holds three tickets, none of them about to leave.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets rate-cap(3; hour). per-any(hour). tickets stock-cap(3; open tickets at the service desk).\nBetween two hours back and one hour back, the intake bot made three tickets; nothing since. The set currently holds three tickets, none of them about to leave.", "question": "How much room is left for one more ticket once both caps apply?", "options": ["Room for two more", "The full allowance of three is open", "None — the cap is already full", "The statement does not settle it", "Room for exactly one more"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-08-mixed", "probe": "mixed", "domain": "tickets", "scope": "global", "oracle": {"kind": "stock", "probe": "mixed", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 3, "stock_held_after": 3}}, {"id": "a86m-stock-stock-08-mixed-probes", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three probes in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than three probes in flight for this monitor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nBetween two hours back and one hour back, this monitor made three probes; nothing since. The set currently holds three probes, none of them about to leave.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes rate-cap(3; hour). per-any(hour). probes stock-cap(3; probes in flight for this monitor).\nBetween two hours back and one hour back, this monitor made three probes; nothing since. The set currently holds three probes, none of them about to leave.", "question": "How much room is left for one more probe once both caps apply?", "options": ["The full allowance of three is open", "Room for exactly one more", "The statement does not settle it", "Room for two more", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-08-mixed", "probe": "mixed", "domain": "probes", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "mixed", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 3, "stock_held_after": 3}}, {"id": "a86m-stock-stock-08-mixed-renders.1", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three renders in any day; the allowance refills as the day goes by; the day rolls, so any span of one day counts. The cap allows no more than three renders queued on the farm at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nBetween two days back and one day back, the night worker made three renders; nothing since. The set currently holds three renders, none of them about to leave.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders rate-cap(3; day). per-any(day). renders stock-cap(3; renders queued on the farm).\nBetween two days back and one day back, the night worker made three renders; nothing since. The set currently holds three renders, none of them about to leave.", "question": "How much room is left for one more render once both caps apply?", "options": ["None — the cap is already full", "The full allowance of three is open", "Room for exactly one more", "Room for two more", "The statement does not settle it"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-08-mixed", "probe": "mixed", "domain": "renders", "scope": "global", "oracle": {"kind": "stock", "probe": "mixed", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 3, "stock_held_after": 3}}, {"id": "a86m-stock-stock-08-mixed-backfills", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three backfills in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than three backfills running for this job at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nBetween two hours back and one hour back, this migration job made three backfills; nothing since. The set currently holds three backfills, none of them about to leave.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills rate-cap(3; hour). per-any(hour). backfills stock-cap(3; backfills running for this job).\nBetween two hours back and one hour back, this migration job made three backfills; nothing since. The set currently holds three backfills, none of them about to leave.", "question": "How much room is left for one more backfill once both caps apply?", "options": ["Room for exactly one more", "The statement does not settle it", "The full allowance of three is open", "Room for two more", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-08-mixed", "probe": "mixed", "domain": "backfills", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "mixed", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 3, "stock_held_after": 3}}, {"id": "a86m-stock-stock-08-mixed-invites", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three invites in any day; the allowance refills as the day goes by; the day rolls, so any span of one day counts. The cap allows no more than three invites outstanding in the workspace at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nBetween two days back and one day back, the workspace bot made three invites; nothing since. The set currently holds three invites, none of them about to leave.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites rate-cap(3; day). per-any(day). invites stock-cap(3; invites outstanding in the workspace).\nBetween two days back and one day back, the workspace bot made three invites; nothing since. The set currently holds three invites, none of them about to leave.", "question": "How much room is left for one more invite once both caps apply?", "options": ["Room for exactly one more", "None — the cap is already full", "Room for two more", "The statement does not settle it", "The full allowance of three is open"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-08-mixed", "probe": "mixed", "domain": "invites", "scope": "global", "oracle": {"kind": "stock", "probe": "mixed", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 3, "stock_held_after": 3}}, {"id": "a86m-stock-stock-08-mixed-locks.2", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three locks in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than three locks held by this editor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nBetween two hours back and one hour back, this editor made three locks; nothing since. The set currently holds three locks, none of them about to leave.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks rate-cap(3; hour). per-any(hour). locks stock-cap(3; locks held by this editor).\nBetween two hours back and one hour back, this editor made three locks; nothing since. The set currently holds three locks, none of them about to leave.", "question": "How much room is left for one more lock once both caps apply?", "options": ["Room for exactly one more", "Room for two more", "The statement does not settle it", "The full allowance of three is open", "None — the cap is already full"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-08-mixed", "probe": "mixed", "domain": "locks", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "mixed", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 3, "stock_held_after": 3}}, {"id": "a86m-stock-stock-08-mixed-replays", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three replays in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than three replays queued on the cluster at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nBetween two hours back and one hour back, the analysis bot made three replays; nothing since. The set currently holds three replays, none of them about to leave.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays rate-cap(3; hour). per-any(hour). replays stock-cap(3; replays queued on the cluster).\nBetween two hours back and one hour back, the analysis bot made three replays; nothing since. The set currently holds three replays, none of them about to leave.", "question": "How much room is left for one more replay once both caps apply?", "options": ["None — the cap is already full", "Room for two more", "Room for exactly one more", "The statement does not settle it", "The full allowance of three is open"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-08-mixed", "probe": "mixed", "domain": "replays", "scope": "global", "oracle": {"kind": "stock", "probe": "mixed", "N": 3, "scope": "global", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 3, "stock_held_after": 3}}, {"id": "a86m-stock-stock-08-mixed-uploads", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three uploads in any hour; the allowance refills as the hour goes by; the hour rolls, so any span of one hour counts. The cap allows no more than three uploads unfinished for this account at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nBetween two hours back and one hour back, this uploader made three uploads; nothing since. The set currently holds three uploads, none of them about to leave.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads rate-cap(3; hour). per-any(hour). uploads stock-cap(3; uploads unfinished for this account).\nBetween two hours back and one hour back, this uploader made three uploads; nothing since. The set currently holds three uploads, none of them about to leave.", "question": "How much room is left for one more upload once both caps apply?", "options": ["Room for exactly one more", "Room for two more", "The full allowance of three is open", "None — the cap is already full", "The statement does not settle it"], "answer": "None — the cap is already full", "settlement_stratum": "stock", "frame": "stock-08-mixed", "probe": "mixed", "domain": "uploads", "scope": "per-identity", "oracle": {"kind": "stock", "probe": "mixed", "N": 3, "scope": "per-identity", "alignment": "bare", "used_after": 0, "held_after": 0, "rate_used_after": 3, "stock_held_after": 3}}, {"id": "a86m-cal-instr-rate-tickets", "calibration": true, "planted_stratum": "rate", "control_kind": "instrument", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than four open tickets at the service desk at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe cap records four tickets during the hour just before now, and the set currently holds four open tickets at the service desk. the intake bot idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets rate-cap(4; hour).\nThe cap records four tickets during the hour just before now, and the set currently holds four open tickets at the service desk. the intake bot idles for one full hour without acting; set membership is unchanged.", "question": "After the intake bot has idled, what room is left under the cap?", "options": ["None — the cap is already full", "Room for exactly one more", "Room for three more", "The statement does not settle it", "The full allowance of four is open"], "answer": "The full allowance of four is open", "oracle": {"kind": "rate", "N": 4, "probe": "wait", "key_room": 4, "unplanted_form": "stock", "unplanted_room": 0}}, {"id": "a86m-cal-instr-rate-probes", "calibration": true, "planted_stratum": "rate", "control_kind": "instrument", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than four probes in flight for this monitor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe cap records four probes during the hour just before now, and the set currently holds four probes in flight for this monitor. this monitor idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes rate-cap(4; hour).\nThe cap records four probes during the hour just before now, and the set currently holds four probes in flight for this monitor. this monitor idles for one full hour without acting; set membership is unchanged.", "question": "After this monitor has idled, what room is left under the cap?", "options": ["The full allowance of four is open", "Room for three more", "Room for exactly one more", "None — the cap is already full", "The statement does not settle it"], "answer": "The full allowance of four is open", "oracle": {"kind": "rate", "N": 4, "probe": "wait", "key_room": 4, "unplanted_form": "stock", "unplanted_room": 0}}, {"id": "a86m-cal-instr-rate-renders", "calibration": true, "planted_stratum": "rate", "control_kind": "instrument", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than four renders queued on the farm at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe cap records four renders during the day just before now, and the set currently holds four renders queued on the farm. the night worker idles for one full day without acting; set membership is unchanged.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders rate-cap(4; day).\nThe cap records four renders during the day just before now, and the set currently holds four renders queued on the farm. the night worker idles for one full day without acting; set membership is unchanged.", "question": "After the night worker has idled, what room is left under the cap?", "options": ["Room for exactly one more", "The statement does not settle it", "None — the cap is already full", "The full allowance of four is open", "Room for three more"], "answer": "The full allowance of four is open", "oracle": {"kind": "rate", "N": 4, "probe": "wait", "key_room": 4, "unplanted_form": "stock", "unplanted_room": 0}}, {"id": "a86m-cal-instr-rate-backfills", "calibration": true, "planted_stratum": "rate", "control_kind": "instrument", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than four backfills running for this job at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe cap records four backfills during the hour just before now, and the set currently holds four backfills running for this job. this migration job idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills rate-cap(4; hour).\nThe cap records four backfills during the hour just before now, and the set currently holds four backfills running for this job. this migration job idles for one full hour without acting; set membership is unchanged.", "question": "After this migration job has idled, what room is left under the cap?", "options": ["The statement does not settle it", "The full allowance of four is open", "Room for exactly one more", "Room for three more", "None — the cap is already full"], "answer": "The full allowance of four is open", "oracle": {"kind": "rate", "N": 4, "probe": "wait", "key_room": 4, "unplanted_form": "stock", "unplanted_room": 0}}, {"id": "a86m-cal-instr-rate-invites", "calibration": true, "planted_stratum": "rate", "control_kind": "instrument", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than four invites outstanding in the workspace at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe cap records four invites during the day just before now, and the set currently holds four invites outstanding in the workspace. the workspace bot idles for one full day without acting; set membership is unchanged.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites rate-cap(4; day).\nThe cap records four invites during the day just before now, and the set currently holds four invites outstanding in the workspace. the workspace bot idles for one full day without acting; set membership is unchanged.", "question": "After the workspace bot has idled, what room is left under the cap?", "options": ["Room for exactly one more", "Room for three more", "None — the cap is already full", "The full allowance of four is open", "The statement does not settle it"], "answer": "The full allowance of four is open", "oracle": {"kind": "rate", "N": 4, "probe": "wait", "key_room": 4, "unplanted_form": "stock", "unplanted_room": 0}}, {"id": "a86m-cal-instr-rate-locks", "calibration": true, "planted_stratum": "rate", "control_kind": "instrument", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than four locks held by this editor at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe cap records four locks during the hour just before now, and the set currently holds four locks held by this editor. this editor idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks rate-cap(4; hour).\nThe cap records four locks during the hour just before now, and the set currently holds four locks held by this editor. this editor idles for one full hour without acting; set membership is unchanged.", "question": "After this editor has idled, what room is left under the cap?", "options": ["The full allowance of four is open", "Room for exactly one more", "None — the cap is already full", "Room for three more", "The statement does not settle it"], "answer": "The full allowance of four is open", "oracle": {"kind": "rate", "N": 4, "probe": "wait", "key_room": 4, "unplanted_form": "stock", "unplanted_room": 0}}, {"id": "a86m-cal-instr-rate-replays", "calibration": true, "planted_stratum": "rate", "control_kind": "instrument", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than four replays queued on the cluster at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe cap records four replays during the hour just before now, and the set currently holds four replays queued on the cluster. the analysis bot idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays rate-cap(4; hour).\nThe cap records four replays during the hour just before now, and the set currently holds four replays queued on the cluster. the analysis bot idles for one full hour without acting; set membership is unchanged.", "question": "After the analysis bot has idled, what room is left under the cap?", "options": ["Room for three more", "The full allowance of four is open", "The statement does not settle it", "Room for exactly one more", "None — the cap is already full"], "answer": "The full allowance of four is open", "oracle": {"kind": "rate", "N": 4, "probe": "wait", "key_room": 4, "unplanted_form": "stock", "unplanted_room": 0}}, {"id": "a86m-cal-instr-rate-uploads", "calibration": true, "planted_stratum": "rate", "control_kind": "instrument", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows no more than four uploads unfinished for this account at once; a place frees only when a member quits the set — closed, released, deleted or consumed — regardless of how much time passes.\nThe cap records four uploads during the hour just before now, and the set currently holds four uploads unfinished for this account. this uploader idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads rate-cap(4; hour).\nThe cap records four uploads during the hour just before now, and the set currently holds four uploads unfinished for this account. this uploader idles for one full hour without acting; set membership is unchanged.", "question": "After this uploader has idled, what room is left under the cap?", "options": ["Room for exactly one more", "Room for three more", "The statement does not settle it", "The full allowance of four is open", "None — the cap is already full"], "answer": "The full allowance of four is open", "oracle": {"kind": "rate", "N": 4, "probe": "wait", "key_room": 4, "unplanted_form": "stock", "unplanted_room": 0}}, {"id": "a86m-cal-cust-rate-tickets", "calibration": true, "planted_stratum": "rate", "control_kind": "custodian", "english": "Manifest line CN-4100: no custodian is recorded.", "ainglish": "Manifest line CN-4100: the custodian recorded is Mirela.", "question": "Which party is recorded as custodian on line CN-4100?", "options": ["Mirela", "No party is recorded", "A party is named but withheld", "The field is blank", "Bram"], "answer": "Mirela", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-rate-probes", "calibration": true, "planted_stratum": "rate", "control_kind": "custodian", "english": "Manifest line CN-4101: no custodian is recorded.", "ainglish": "Manifest line CN-4101: the custodian recorded is Tobiah.", "question": "Which party is recorded as custodian on line CN-4101?", "options": ["A party is named but withheld", "No party is recorded", "Tobiah", "The field is blank", "Yuki"], "answer": "Tobiah", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-rate-renders", "calibration": true, "planted_stratum": "rate", "control_kind": "custodian", "english": "Manifest line CN-4102: no custodian is recorded.", "ainglish": "Manifest line CN-4102: the custodian recorded is Sunil.", "question": "Which party is recorded as custodian on line CN-4102?", "options": ["Sunil", "A party is named but withheld", "No party is recorded", "Halvard", "The field is blank"], "answer": "Sunil", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-rate-backfills", "calibration": true, "planted_stratum": "rate", "control_kind": "custodian", "english": "Manifest line CN-4103: no custodian is recorded.", "ainglish": "Manifest line CN-4103: the custodian recorded is Ottoline.", "question": "Which party is recorded as custodian on line CN-4103?", "options": ["The field is blank", "A party is named but withheld", "Esen", "Ottoline", "No party is recorded"], "answer": "Ottoline", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-rate-invites", "calibration": true, "planted_stratum": "rate", "control_kind": "custodian", "english": "Manifest line CN-4104: no custodian is recorded.", "ainglish": "Manifest line CN-4104: the custodian recorded is Bram.", "question": "Which party is recorded as custodian on line CN-4104?", "options": ["No party is recorded", "The field is blank", "A party is named but withheld", "Perrin", "Bram"], "answer": "Bram", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-rate-locks", "calibration": true, "planted_stratum": "rate", "control_kind": "custodian", "english": "Manifest line CN-4105: no custodian is recorded.", "ainglish": "Manifest line CN-4105: the custodian recorded is Yuki.", "question": "Which party is recorded as custodian on line CN-4105?", "options": ["The field is blank", "A party is named but withheld", "Yuki", "No party is recorded", "Nadia"], "answer": "Yuki", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-rate-replays", "calibration": true, "planted_stratum": "rate", "control_kind": "custodian", "english": "Manifest line CN-4106: no custodian is recorded.", "ainglish": "Manifest line CN-4106: the custodian recorded is Halvard.", "question": "Which party is recorded as custodian on line CN-4106?", "options": ["No party is recorded", "Corin", "Halvard", "A party is named but withheld", "The field is blank"], "answer": "Halvard", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-rate-uploads", "calibration": true, "planted_stratum": "rate", "control_kind": "custodian", "english": "Manifest line CN-4107: no custodian is recorded.", "ainglish": "Manifest line CN-4107: the custodian recorded is Esen.", "question": "Which party is recorded as custodian on line CN-4107?", "options": ["The field is blank", "A party is named but withheld", "Esen", "No party is recorded", "Aster"], "answer": "Esen", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-instr-stock-tickets", "calibration": true, "planted_stratum": "stock", "control_kind": "instrument", "english": "Operations note — tickets. The allowance described below is shared across the service desk.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three tickets in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe cap records three tickets during the hour just before now, and the set currently holds three open tickets at the service desk. the intake bot idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — tickets. The allowance described below is shared across the service desk.\ntickets stock-cap(3; open tickets at the service desk).\nThe cap records three tickets during the hour just before now, and the set currently holds three open tickets at the service desk. the intake bot idles for one full hour without acting; set membership is unchanged.", "question": "After the intake bot has idled, what room is left under the cap?", "options": ["Room for two more", "None — the cap is already full", "The statement does not settle it", "Room for exactly one more", "The full allowance of three is open"], "answer": "None — the cap is already full", "oracle": {"kind": "stock", "N": 3, "probe": "wait", "key_room": 0, "unplanted_form": "rate", "unplanted_room": 3}}, {"id": "a86m-cal-instr-stock-probes", "calibration": true, "planted_stratum": "stock", "control_kind": "instrument", "english": "Operations note — probes. The allowance described below covers this monitor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three probes in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe cap records three probes during the hour just before now, and the set currently holds three probes in flight for this monitor. this monitor idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — probes. The allowance described below covers this monitor alone.\nprobes stock-cap(3; probes in flight for this monitor).\nThe cap records three probes during the hour just before now, and the set currently holds three probes in flight for this monitor. this monitor idles for one full hour without acting; set membership is unchanged.", "question": "After this monitor has idled, what room is left under the cap?", "options": ["The statement does not settle it", "The full allowance of three is open", "Room for two more", "None — the cap is already full", "Room for exactly one more"], "answer": "None — the cap is already full", "oracle": {"kind": "stock", "N": 3, "probe": "wait", "key_room": 0, "unplanted_form": "rate", "unplanted_room": 3}}, {"id": "a86m-cal-instr-stock-renders", "calibration": true, "planted_stratum": "stock", "control_kind": "instrument", "english": "Operations note — renders. The allowance described below is shared across the render farm.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three renders in any day; the allowance refills as the day goes by; the note does not say whether the day follows the clock or rolls.\nThe cap records three renders during the day just before now, and the set currently holds three renders queued on the farm. the night worker idles for one full day without acting; set membership is unchanged.", "ainglish": "Operations note — renders. The allowance described below is shared across the render farm.\nrenders stock-cap(3; renders queued on the farm).\nThe cap records three renders during the day just before now, and the set currently holds three renders queued on the farm. the night worker idles for one full day without acting; set membership is unchanged.", "question": "After the night worker has idled, what room is left under the cap?", "options": ["Room for two more", "The statement does not settle it", "The full allowance of three is open", "None — the cap is already full", "Room for exactly one more"], "answer": "None — the cap is already full", "oracle": {"kind": "stock", "N": 3, "probe": "wait", "key_room": 0, "unplanted_form": "rate", "unplanted_room": 3}}, {"id": "a86m-cal-instr-stock-backfills", "calibration": true, "planted_stratum": "stock", "control_kind": "instrument", "english": "Operations note — backfills. The allowance described below covers this migration job alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three backfills in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe cap records three backfills during the hour just before now, and the set currently holds three backfills running for this job. this migration job idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — backfills. The allowance described below covers this migration job alone.\nbackfills stock-cap(3; backfills running for this job).\nThe cap records three backfills during the hour just before now, and the set currently holds three backfills running for this job. this migration job idles for one full hour without acting; set membership is unchanged.", "question": "After this migration job has idled, what room is left under the cap?", "options": ["The statement does not settle it", "The full allowance of three is open", "Room for exactly one more", "Room for two more", "None — the cap is already full"], "answer": "None — the cap is already full", "oracle": {"kind": "stock", "N": 3, "probe": "wait", "key_room": 0, "unplanted_form": "rate", "unplanted_room": 3}}, {"id": "a86m-cal-instr-stock-invites", "calibration": true, "planted_stratum": "stock", "control_kind": "instrument", "english": "Operations note — invites. The allowance described below is shared across the workspace.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three invites in any day; the allowance refills as the day goes by; the note does not say whether the day follows the clock or rolls.\nThe cap records three invites during the day just before now, and the set currently holds three invites outstanding in the workspace. the workspace bot idles for one full day without acting; set membership is unchanged.", "ainglish": "Operations note — invites. The allowance described below is shared across the workspace.\ninvites stock-cap(3; invites outstanding in the workspace).\nThe cap records three invites during the day just before now, and the set currently holds three invites outstanding in the workspace. the workspace bot idles for one full day without acting; set membership is unchanged.", "question": "After the workspace bot has idled, what room is left under the cap?", "options": ["The full allowance of three is open", "The statement does not settle it", "None — the cap is already full", "Room for two more", "Room for exactly one more"], "answer": "None — the cap is already full", "oracle": {"kind": "stock", "N": 3, "probe": "wait", "key_room": 0, "unplanted_form": "rate", "unplanted_room": 3}}, {"id": "a86m-cal-instr-stock-locks", "calibration": true, "planted_stratum": "stock", "control_kind": "instrument", "english": "Operations note — locks. The allowance described below covers this editor alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three locks in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe cap records three locks during the hour just before now, and the set currently holds three locks held by this editor. this editor idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — locks. The allowance described below covers this editor alone.\nlocks stock-cap(3; locks held by this editor).\nThe cap records three locks during the hour just before now, and the set currently holds three locks held by this editor. this editor idles for one full hour without acting; set membership is unchanged.", "question": "After this editor has idled, what room is left under the cap?", "options": ["The full allowance of three is open", "Room for exactly one more", "The statement does not settle it", "None — the cap is already full", "Room for two more"], "answer": "None — the cap is already full", "oracle": {"kind": "stock", "N": 3, "probe": "wait", "key_room": 0, "unplanted_form": "rate", "unplanted_room": 3}}, {"id": "a86m-cal-instr-stock-replays", "calibration": true, "planted_stratum": "stock", "control_kind": "instrument", "english": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three replays in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe cap records three replays during the hour just before now, and the set currently holds three replays queued on the cluster. the analysis bot idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — replays. The allowance described below is shared across the analysis cluster.\nreplays stock-cap(3; replays queued on the cluster).\nThe cap records three replays during the hour just before now, and the set currently holds three replays queued on the cluster. the analysis bot idles for one full hour without acting; set membership is unchanged.", "question": "After the analysis bot has idled, what room is left under the cap?", "options": ["The full allowance of three is open", "None — the cap is already full", "The statement does not settle it", "Room for exactly one more", "Room for two more"], "answer": "None — the cap is already full", "oracle": {"kind": "stock", "N": 3, "probe": "wait", "key_room": 0, "unplanted_form": "rate", "unplanted_room": 3}}, {"id": "a86m-cal-instr-stock-uploads", "calibration": true, "planted_stratum": "stock", "control_kind": "instrument", "english": "Operations note — uploads. The allowance described below covers this uploader alone.\nRegister definition: Attach exactly one cap operator to a countable noun in a statement of a limit, quota, budget or allowance. `X rate-cap(N; W)` means at most N X may be created, performed or spent within the window W, and capacity returns as W passes, independent of what later happens to any earlier X; W is a bare period unit such as hour, day or 60m. A bare unit says how long the window is and nothing about how it is aligned: whether the count restarts at a clock boundary or slides is stated as a separate per-clock or per-any statement when it is load-bearing, and is never written inside the argument. Where no alignment statement accompanies a rate-cap, a reader treats boundary questions, such as whether two maximal bursts either side of an hour mark are both legal, as unknown rather than inferring an alignment from the unit. rate-cap says nothing about how many X may exist at once. `X stock-cap(N; S)` means at most N X belonging to the set S may exist or be held at one time, and capacity returns only when a member of S leaves it by being closed, released, deleted or consumed; the passage of time alone returns nothing, and stock-cap says nothing about how fast X may be created. S names the scope of the holding, for example `open proposals by this sub` or `pages of this artifact`, so per-identity versus global is carried by S, not by the marker. Both forms state a ceiling, not an entitlement, and neither says who enforces the limit, what happens on breach, or whether the cap can change. The discriminating question is one a reader can put to any limit: if the actor does nothing, does capacity come back? Yes is rate-cap; no is stock-cap. If a writer cannot answer that question, ask rather than guess. Bare `limit`, `quota` or `cap` remains legal where only one reading is possible or the distinction cannot affect an inference or action.\nThe cap allows at most three uploads in any hour; the allowance refills as the hour goes by; the note does not say whether the hour follows the clock or rolls.\nThe cap records three uploads during the hour just before now, and the set currently holds three uploads unfinished for this account. this uploader idles for one full hour without acting; set membership is unchanged.", "ainglish": "Operations note — uploads. The allowance described below covers this uploader alone.\nuploads stock-cap(3; uploads unfinished for this account).\nThe cap records three uploads during the hour just before now, and the set currently holds three uploads unfinished for this account. this uploader idles for one full hour without acting; set membership is unchanged.", "question": "After this uploader has idled, what room is left under the cap?", "options": ["None — the cap is already full", "Room for exactly one more", "The full allowance of three is open", "The statement does not settle it", "Room for two more"], "answer": "None — the cap is already full", "oracle": {"kind": "stock", "N": 3, "probe": "wait", "key_room": 0, "unplanted_form": "rate", "unplanted_room": 3}}, {"id": "a86m-cal-cust-stock-tickets", "calibration": true, "planted_stratum": "stock", "control_kind": "custodian", "english": "Manifest line CN-4150: no custodian is recorded.", "ainglish": "Manifest line CN-4150: the custodian recorded is Perrin.", "question": "Which party is recorded as custodian on line CN-4150?", "options": ["A party is named but withheld", "No party is recorded", "The field is blank", "Jumoke", "Perrin"], "answer": "Perrin", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-stock-probes", "calibration": true, "planted_stratum": "stock", "control_kind": "custodian", "english": "Manifest line CN-4151: no custodian is recorded.", "ainglish": "Manifest line CN-4151: the custodian recorded is Nadia.", "question": "Which party is recorded as custodian on line CN-4151?", "options": ["The field is blank", "No party is recorded", "Nadia", "Tarek", "A party is named but withheld"], "answer": "Nadia", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-stock-renders", "calibration": true, "planted_stratum": "stock", "control_kind": "custodian", "english": "Manifest line CN-4152: no custodian is recorded.", "ainglish": "Manifest line CN-4152: the custodian recorded is Corin.", "question": "Which party is recorded as custodian on line CN-4152?", "options": ["A party is named but withheld", "Corin", "No party is recorded", "The field is blank", "Willa"], "answer": "Corin", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-stock-backfills", "calibration": true, "planted_stratum": "stock", "control_kind": "custodian", "english": "Manifest line CN-4153: no custodian is recorded.", "ainglish": "Manifest line CN-4153: the custodian recorded is Aster.", "question": "Which party is recorded as custodian on line CN-4153?", "options": ["Aster", "Ondrej", "A party is named but withheld", "No party is recorded", "The field is blank"], "answer": "Aster", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-stock-invites", "calibration": true, "planted_stratum": "stock", "control_kind": "custodian", "english": "Manifest line CN-4154: no custodian is recorded.", "ainglish": "Manifest line CN-4154: the custodian recorded is Jumoke.", "question": "Which party is recorded as custodian on line CN-4154?", "options": ["Jumoke", "A party is named but withheld", "No party is recorded", "The field is blank", "Mirela"], "answer": "Jumoke", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-stock-locks", "calibration": true, "planted_stratum": "stock", "control_kind": "custodian", "english": "Manifest line CN-4155: no custodian is recorded.", "ainglish": "Manifest line CN-4155: the custodian recorded is Tarek.", "question": "Which party is recorded as custodian on line CN-4155?", "options": ["Tobiah", "The field is blank", "Tarek", "No party is recorded", "A party is named but withheld"], "answer": "Tarek", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-stock-replays", "calibration": true, "planted_stratum": "stock", "control_kind": "custodian", "english": "Manifest line CN-4156: no custodian is recorded.", "ainglish": "Manifest line CN-4156: the custodian recorded is Willa.", "question": "Which party is recorded as custodian on line CN-4156?", "options": ["Willa", "Sunil", "The field is blank", "A party is named but withheld", "No party is recorded"], "answer": "Willa", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}, {"id": "a86m-cal-cust-stock-uploads", "calibration": true, "planted_stratum": "stock", "control_kind": "custodian", "english": "Manifest line CN-4157: no custodian is recorded.", "ainglish": "Manifest line CN-4157: the custodian recorded is Ondrej.", "question": "Which party is recorded as custodian on line CN-4157?", "options": ["Ottoline", "No party is recorded", "The field is blank", "A party is named but withheld", "Ondrej"], "answer": "Ondrej", "oracle": {"unplanted_licensed_answer": "No party is recorded"}}], "sha256": "63a03a70a0c3f91264523ba0eb567709b8b3ec117603af96d975ff2bb95261f4"}