[
  {
    "id": "rc-api-rate-01-wait-dxalloc-0",
    "english": "Service note, API budget. Budget for this client only.\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.\nAt most 4 requests in each hour; capacity returns as the hour passes; whether the hour is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding hour, this client made four requests.\nThis client holds an authorisation to make a request that runs until the end of today.",
    "ainglish": "Service note, API budget. Budget for this client only.\nrequests rate-cap(4; hour).\nCounts below are as of now, before any further action.\nIn the preceding hour, this client made four requests.\nThis client holds an authorisation to make a request that runs until the end of today.",
    "question": "If this client waits one full hour from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "No room for another",
      "Room for three more",
      "Room for one more",
      "Room for the full allowance of four",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of four",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "api",
    "semantic_frame": "rate-01-wait",
    "source_item_id": "rc-api-rate-01-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-rate-02-wait-dxalloc-3",
    "english": "Service note, API budget. Budget for this client only.\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.\nAt most 4 requests in each hour; capacity returns as the hour passes; the count restarts at each clock hour boundary.\nCounts below are as of now, before any further action.\nIn the current clock hour, this client made four requests.",
    "ainglish": "Service note, API budget. Budget for this client only.\nrequests rate-cap(4; hour). per-clock(hour).\nCounts below are as of now, before any further action.\nIn the current clock hour, this client made four requests.",
    "question": "If this client waits one full hour from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for one more",
      "Room for the full allowance of four",
      "Room for two more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of four",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "api",
    "semantic_frame": "rate-02-wait",
    "source_item_id": "rc-api-rate-02-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-rate-03-release-dxalloc-1",
    "english": "Service note, API budget. Budget for this client only.\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.\nAt most 4 requests in each hour; capacity returns as the hour passes; the window slides, so any span of one hour counts.\nCounts below are as of now, before any further action.\nIn the preceding hour, this client made two requests, aged 10 minutes and 15 minutes.\nJust now, this client closed one of those requests; nothing else changed.",
    "ainglish": "Service note, API budget. Budget for this client only.\nrequests rate-cap(4; hour). per-any(hour).\nCounts below are as of now, before any further action.\nIn the preceding hour, this client made two requests, aged 10 minutes and 15 minutes.\nJust now, this client closed one of those requests; nothing else changed.",
    "question": "How much room is there under this cap now, immediately after that closure?",
    "options": [
      "Room for two more",
      "No room for another",
      "Room for three more",
      "Room for the full allowance of four",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "rate",
    "probe": "release",
    "domain": "api",
    "semantic_frame": "rate-03-release",
    "source_item_id": "rc-api-rate-03-release",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-rate-04-delete-dxalloc-2",
    "english": "Service note, API budget. Budget for this client only.\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.\nAt most 4 requests in each hour; capacity returns as the hour passes; whether the hour is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding hour, this client made two requests, aged 6 minutes and 10 minutes.\nThe current time is 10:40.\nJust now, this client deleted an older request that it made last week; nothing else changed.\nThis client's authorisation to make a request was revoked this morning and has not been restored.",
    "ainglish": "Service note, API budget. Budget for this client only.\nrequests rate-cap(4; hour).\nCounts below are as of now, before any further action.\nIn the preceding hour, this client made two requests, aged 6 minutes and 10 minutes.\nThe current time is 10:40.\nJust now, this client deleted an older request that it made last week; nothing else changed.\nThis client's authorisation to make a request was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap now, immediately after that deletion?",
    "options": [
      "Room for three more",
      "Room for the full allowance of four",
      "Room for one more",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "rate",
    "probe": "delete",
    "domain": "api",
    "semantic_frame": "rate-04-delete",
    "source_item_id": "rc-api-rate-04-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-rate-05-count-dxalloc-9",
    "english": "Service note, API budget. Budget for this client only.\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.\nAt most 4 requests in each hour; capacity returns as the hour passes; the window slides, so any span of one hour counts.\nCounts below are as of now, before any further action.\nThis client made four requests: two of them 6 minutes and 12 minutes ago, and two of them 90 minutes and 120 minutes ago.\nAnother client made three requests in the preceding hour.",
    "ainglish": "Service note, API budget. Budget for this client only.\nrequests rate-cap(4; hour). per-any(hour).\nCounts below are as of now, before any further action.\nThis client made four requests: two of them 6 minutes and 12 minutes ago, and two of them 90 minutes and 120 minutes ago.\nAnother client made three requests in the preceding hour.",
    "question": "How much room is there under this cap for this client now?",
    "options": [
      "Room for the full allowance of four",
      "Room for three more",
      "Room for one more",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "api",
    "semantic_frame": "rate-05-count",
    "source_item_id": "rc-api-rate-05-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-rate-06-count-dxalloc-2",
    "english": "Service note, API budget. Budget for this client only.\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.\nAt most 4 requests in each hour; capacity returns as the hour passes; whether the hour is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of requests is given.",
    "ainglish": "Service note, API budget. Budget for this client only.\nrequests rate-cap(4; hour).\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of requests is given.",
    "question": "How many requests exist now?",
    "options": [
      "Exactly four exist now",
      "Fewer than four exist now",
      "More than four exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "api",
    "semantic_frame": "rate-06-count",
    "source_item_id": "rc-api-rate-06-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-rate-07-boundary-dxalloc-0",
    "english": "Service note, API budget. Budget for this client only.\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.\nAt most 4 requests in each hour; capacity returns as the hour passes; the count restarts at each clock hour boundary.\nCounts below are as of now, before any further action.\nThe hour boundary falls at the top of the hour. This client plans four requests just before the boundary and four more just after it, with nothing else made in the surrounding span.",
    "ainglish": "Service note, API budget. Budget for this client only.\nrequests rate-cap(4; hour). per-clock(hour).\nCounts below are as of now, before any further action.\nThe hour boundary falls at the top of the hour. This client plans four requests just before the boundary and four more just after it, with nothing else made in the surrounding span.",
    "question": "Can both planned bursts be legal under this cap?",
    "options": [
      "Yes, both bursts can be legal",
      "No, at most one of the two bursts can be legal",
      "Only the burst before the boundary can be legal",
      "Only the burst after the boundary can be legal",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Yes, both bursts can be legal",
    "settlement_stratum": "rate",
    "probe": "boundary",
    "domain": "api",
    "semantic_frame": "rate-07-boundary",
    "source_item_id": "rc-api-rate-07-boundary",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-rate-08-count-dxalloc-2",
    "english": "Service note, API budget. Budget for this client only.\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.\nAt most 4 requests in each hour; capacity returns as the hour passes; the window slides, so any span of one hour counts. At most 5 in-flight requests by this client may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the preceding hour, this client made four requests, aged 10 minutes, 13 minutes, 16 minutes and 19 minutes.\nThree in-flight requests exist now.",
    "ainglish": "Service note, API budget. Budget for this client only.\nrequests rate-cap(4; hour). per-any(hour). requests stock-cap(5; in-flight requests by this client).\nCounts below are as of now, before any further action.\nIn the preceding hour, this client made four requests, aged 10 minutes, 13 minutes, 16 minutes and 19 minutes.\nThree in-flight requests exist now.",
    "question": "How much room is there now for one additional request under both constraints together?",
    "options": [
      "No room for another",
      "Room for the full allowance of four",
      "Room for one more",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "api",
    "semantic_frame": "rate-08-count",
    "source_item_id": "rc-api-rate-08-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-stock-01-wait-dxalloc-0",
    "english": "Service note, API budget.\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.\nAt most 3 in-flight requests by this client may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nThree in-flight requests exist now.\nThis client waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "ainglish": "Service note, API budget.\nrequests stock-cap(3; in-flight requests by this client).\nCounts below are as of now, before any further action.\nThree in-flight requests exist now.\nThis client waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "No room for another",
      "Room for two more",
      "Room for one more",
      "Room for the full allowance of three",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "api",
    "semantic_frame": "stock-01-wait",
    "source_item_id": "rc-api-stock-01-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-stock-02-wait-dxalloc-0",
    "english": "Service note, API budget.\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.\nAt most 3 in-flight requests by this client may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nThree in-flight requests exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. This client waits twenty minutes and does nothing else; nothing else changes.",
    "ainglish": "Service note, API budget.\nrequests stock-cap(3; in-flight requests by this client).\nCounts below are as of now, before any further action.\nThree in-flight requests exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. This client waits twenty minutes and does nothing else; nothing else changes.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for one more",
      "Room for the full allowance of three",
      "Room for two more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "api",
    "semantic_frame": "stock-02-wait",
    "source_item_id": "rc-api-stock-02-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-stock-03-release-dxalloc-5",
    "english": "Service note, API budget.\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.\nAt most 3 in-flight requests by this client may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, two in-flight requests existed.\nBetween T0 and T1, this client released one of them; nothing else changed.\nThis client holds an authorisation to start a request that runs until the end of today.",
    "ainglish": "Service note, API budget.\nrequests stock-cap(3; in-flight requests by this client).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, two in-flight requests existed.\nBetween T0 and T1, this client released one of them; nothing else changed.\nThis client holds an authorisation to start a request that runs until the end of today.",
    "question": "How much room is there under this cap at T1, immediately after that release?",
    "options": [
      "Room for one more",
      "Room for two more",
      "Room for the full allowance of three",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "stock",
    "probe": "release",
    "domain": "api",
    "semantic_frame": "stock-03-release",
    "source_item_id": "rc-api-stock-03-release",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-stock-04-delete-dxalloc-3",
    "english": "Service note, API budget.\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.\nAt most 3 in-flight requests by this client may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three in-flight requests existed, and six archived requests existed that were not in the named set.\nBetween T0 and T1, this client deleted one of the in-flight requests; nothing else changed.",
    "ainglish": "Service note, API budget.\nrequests stock-cap(3; in-flight requests by this client).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three in-flight requests existed, and six archived requests existed that were not in the named set.\nBetween T0 and T1, this client deleted one of the in-flight requests; nothing else changed.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "No room for another",
      "Room for one more",
      "Room for two more",
      "Room for the full allowance of three",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "api",
    "semantic_frame": "stock-04-delete",
    "source_item_id": "rc-api-stock-04-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-stock-05-delete-dxalloc-2",
    "english": "Service note, API budget.\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.\nAt most 3 in-flight requests by this client may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three in-flight requests existed, and six archived requests existed that were not in the named set.\nBetween T0 and T1, this client deleted one of the archived requests; no member of the named set changed.\nThis client's authorisation to start a request was revoked this morning and has not been restored.",
    "ainglish": "Service note, API budget.\nrequests stock-cap(3; in-flight requests by this client).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three in-flight requests existed, and six archived requests existed that were not in the named set.\nBetween T0 and T1, this client deleted one of the archived requests; no member of the named set changed.\nThis client's authorisation to start a request was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for one more",
      "Room for two more",
      "Room for the full allowance of three",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "api",
    "semantic_frame": "stock-05-delete",
    "source_item_id": "rc-api-stock-05-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-stock-06-count-dxalloc-7",
    "english": "Service note, API budget.\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.\nAt most 3 in-flight requests by this client may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nThis client has one request in the named set now; another client has two requests of the same kind, which belong to another client and not to this client. No membership changes.",
    "ainglish": "Service note, API budget.\nrequests stock-cap(3; in-flight requests by this client).\nCounts below are as of now, before any further action.\nThis client has one request in the named set now; another client has two requests of the same kind, which belong to another client and not to this client. No membership changes.",
    "question": "How much room is there under this cap for this client now?",
    "options": [
      "Room for one more",
      "Room for two more",
      "No room for another",
      "Room for the full allowance of three",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "api",
    "semantic_frame": "stock-06-count",
    "source_item_id": "rc-api-stock-06-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-stock-07-count-dxalloc-0",
    "english": "Service note, API budget.\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.\nAt most 3 in-flight requests by this client may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of in-flight requests is not given.",
    "ainglish": "Service note, API budget.\nrequests stock-cap(3; in-flight requests by this client).\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of in-flight requests is not given.",
    "question": "Exactly how many in-flight requests exist now?",
    "options": [
      "Exactly three exist now",
      "Fewer than three exist now",
      "More than three exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "api",
    "semantic_frame": "stock-07-count",
    "source_item_id": "rc-api-stock-07-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-api-stock-08-count-dxalloc-1",
    "english": "Service note, API budget.\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.\nAt most 4 requests in each hour; capacity returns as the hour passes; the window slides, so any span of one hour counts. At most 3 in-flight requests by this client may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the span from two hours ago to one hour ago, this client made four requests; none since.\nThree in-flight requests exist now and none is scheduled to leave.",
    "ainglish": "Service note, API budget.\nrequests rate-cap(4; hour). per-any(hour). requests stock-cap(3; in-flight requests by this client).\nCounts below are as of now, before any further action.\nIn the span from two hours ago to one hour ago, this client made four requests; none since.\nThree in-flight requests exist now and none is scheduled to leave.",
    "question": "How much room is there now for one additional request under both constraints together?",
    "options": [
      "Room for two more",
      "No room for another",
      "Room for the full allowance of three",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "api",
    "semantic_frame": "stock-08-count",
    "source_item_id": "rc-api-stock-08-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-storage-rate-01-wait-dxalloc-3",
    "english": "Storage policy note. Budget shared by every actor on this service.\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.\nAt most 5 snapshots in each day; capacity returns as the day passes; whether the day is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding day, the backup agent took five snapshots.\nNo other actor takes a snapshot during the coming day.\nThe backup agent holds an authorisation to take a snapshot that runs until the end of today.",
    "ainglish": "Storage policy note. Budget shared by every actor on this service.\nsnapshots rate-cap(5; day).\nCounts below are as of now, before any further action.\nIn the preceding day, the backup agent took five snapshots.\nNo other actor takes a snapshot during the coming day.\nThe backup agent holds an authorisation to take a snapshot that runs until the end of today.",
    "question": "If the backup agent waits one full day from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for two more",
      "No room for another",
      "Room for four more",
      "Room for the full allowance of five",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of five",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "storage",
    "semantic_frame": "rate-01-wait",
    "source_item_id": "rc-storage-rate-01-wait",
    "scope": "global"
  },
  {
    "id": "rc-storage-rate-02-wait-dxalloc-13",
    "english": "Storage policy note. Budget shared by every actor on this service.\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.\nAt most 5 snapshots in each day; capacity returns as the day passes; the count restarts at each clock day boundary.\nCounts below are as of now, before any further action.\nIn the current clock day, the backup agent took five snapshots.\nNo other actor takes a snapshot during the coming day.",
    "ainglish": "Storage policy note. Budget shared by every actor on this service.\nsnapshots rate-cap(5; day). per-clock(day).\nCounts below are as of now, before any further action.\nIn the current clock day, the backup agent took five snapshots.\nNo other actor takes a snapshot during the coming day.",
    "question": "If the backup agent waits one full day from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "No room for another",
      "Room for one more",
      "Room for the full allowance of five",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of five",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "storage",
    "semantic_frame": "rate-02-wait",
    "source_item_id": "rc-storage-rate-02-wait",
    "scope": "global"
  },
  {
    "id": "rc-storage-rate-03-release-dxalloc-1",
    "english": "Storage policy note. Budget shared by every actor on this service.\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.\nAt most 5 snapshots in each day; capacity returns as the day passes; the window slides, so any span of one day counts.\nCounts below are as of now, before any further action.\nIn the preceding day, the backup agent took three snapshots, aged 4 hours, 6 hours and 8 hours.\nNo other actor took any snapshots in the preceding day.\nJust now, the backup agent closed one of those snapshots; nothing else changed.",
    "ainglish": "Storage policy note. Budget shared by every actor on this service.\nsnapshots rate-cap(5; day). per-any(day).\nCounts below are as of now, before any further action.\nIn the preceding day, the backup agent took three snapshots, aged 4 hours, 6 hours and 8 hours.\nNo other actor took any snapshots in the preceding day.\nJust now, the backup agent closed one of those snapshots; nothing else changed.",
    "question": "How much room is there under this cap now, immediately after that closure?",
    "options": [
      "Room for four more",
      "Room for two more",
      "No room for another",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "rate",
    "probe": "release",
    "domain": "storage",
    "semantic_frame": "rate-03-release",
    "source_item_id": "rc-storage-rate-03-release",
    "scope": "global"
  },
  {
    "id": "rc-storage-rate-04-delete-dxalloc-11",
    "english": "Storage policy note. Budget shared by every actor on this service.\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.\nAt most 5 snapshots in each day; capacity returns as the day passes; whether the day is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding day, the backup agent took two snapshots, aged 2 hours and 4 hours.\nNo other actor took any snapshots in the preceding day.\nThe current time is 14:00 on Wednesday.\nJust now, the backup agent deleted an older snapshot that it took last week; nothing else changed.\nThe backup agent's authorisation to take a snapshot was revoked this morning and has not been restored.",
    "ainglish": "Storage policy note. Budget shared by every actor on this service.\nsnapshots rate-cap(5; day).\nCounts below are as of now, before any further action.\nIn the preceding day, the backup agent took two snapshots, aged 2 hours and 4 hours.\nNo other actor took any snapshots in the preceding day.\nThe current time is 14:00 on Wednesday.\nJust now, the backup agent deleted an older snapshot that it took last week; nothing else changed.\nThe backup agent's authorisation to take a snapshot was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap now, immediately after that deletion?",
    "options": [
      "Room for one more",
      "Room for three more",
      "No room for another",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for three more",
    "settlement_stratum": "rate",
    "probe": "delete",
    "domain": "storage",
    "semantic_frame": "rate-04-delete",
    "source_item_id": "rc-storage-rate-04-delete",
    "scope": "global"
  },
  {
    "id": "rc-storage-rate-05-count-dxalloc-0",
    "english": "Storage policy note. Budget shared by every actor on this service.\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.\nAt most 5 snapshots in each day; capacity returns as the day passes; the window slides, so any span of one day counts.\nCounts below are as of now, before any further action.\nThe backup agent took four snapshots: two of them 2 hours and 4 hours ago, and two of them 36 hours and 48 hours ago.\nThe archive agent took three snapshots in the preceding day.\nNo actor other than the backup agent and the archive agent took any snapshots in the preceding day.",
    "ainglish": "Storage policy note. Budget shared by every actor on this service.\nsnapshots rate-cap(5; day). per-any(day).\nCounts below are as of now, before any further action.\nThe backup agent took four snapshots: two of them 2 hours and 4 hours ago, and two of them 36 hours and 48 hours ago.\nThe archive agent took three snapshots in the preceding day.\nNo actor other than the backup agent and the archive agent took any snapshots in the preceding day.",
    "question": "How much room is there under this cap for the backup agent now?",
    "options": [
      "Room for two more",
      "Room for three more",
      "Room for the full allowance of five",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "storage",
    "semantic_frame": "rate-05-count",
    "source_item_id": "rc-storage-rate-05-count",
    "scope": "global"
  },
  {
    "id": "rc-storage-rate-06-count-dxalloc-2",
    "english": "Storage policy note. Budget shared by every actor on this service.\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.\nAt most 5 snapshots in each day; capacity returns as the day passes; whether the day is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of snapshots is given.",
    "ainglish": "Storage policy note. Budget shared by every actor on this service.\nsnapshots rate-cap(5; day).\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of snapshots is given.",
    "question": "How many snapshots exist now?",
    "options": [
      "Exactly five exist now",
      "Fewer than five exist now",
      "More than five exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "storage",
    "semantic_frame": "rate-06-count",
    "source_item_id": "rc-storage-rate-06-count",
    "scope": "global"
  },
  {
    "id": "rc-storage-rate-07-boundary-dxalloc-1",
    "english": "Storage policy note. Budget shared by every actor on this service.\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.\nAt most 5 snapshots in each day; capacity returns as the day passes; the window slides, so any span of one day counts.\nCounts below are as of now, before any further action.\nThe day boundary falls at midnight. The backup agent plans five snapshots just before the boundary and five more just after it, with nothing else took in the surrounding span.",
    "ainglish": "Storage policy note. Budget shared by every actor on this service.\nsnapshots rate-cap(5; day). per-any(day).\nCounts below are as of now, before any further action.\nThe day boundary falls at midnight. The backup agent plans five snapshots just before the boundary and five more just after it, with nothing else took in the surrounding span.",
    "question": "Can both planned bursts be legal under this cap?",
    "options": [
      "Yes, both bursts can be legal",
      "No, at most one of the two bursts can be legal",
      "Only the burst before the boundary can be legal",
      "Only the burst after the boundary can be legal",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No, at most one of the two bursts can be legal",
    "settlement_stratum": "rate",
    "probe": "boundary",
    "domain": "storage",
    "semantic_frame": "rate-07-boundary",
    "source_item_id": "rc-storage-rate-07-boundary",
    "scope": "global"
  },
  {
    "id": "rc-storage-rate-08-count-dxalloc-8",
    "english": "Storage policy note. Budget shared by every actor on this service.\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.\nAt most 5 snapshots in each day; capacity returns as the day passes; the window slides, so any span of one day counts. At most 5 retained snapshots of volume V may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the preceding day, the backup agent took five snapshots, aged 4 hours, 5 hours, 6 hours, 7 hours and 8 hours.\nNo other actor took any snapshots in the preceding day.\nThree retained snapshots of volume V exist now.",
    "ainglish": "Storage policy note. Budget shared by every actor on this service.\nsnapshots rate-cap(5; day). per-any(day). snapshots stock-cap(5; retained snapshots of volume V).\nCounts below are as of now, before any further action.\nIn the preceding day, the backup agent took five snapshots, aged 4 hours, 5 hours, 6 hours, 7 hours and 8 hours.\nNo other actor took any snapshots in the preceding day.\nThree retained snapshots of volume V exist now.",
    "question": "How much room is there now for one additional snapshot under both constraints together?",
    "options": [
      "Room for four more",
      "Room for the full allowance of five",
      "No room for another",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "storage",
    "semantic_frame": "rate-08-count",
    "source_item_id": "rc-storage-rate-08-count",
    "scope": "global"
  },
  {
    "id": "rc-storage-stock-01-wait-dxalloc-10",
    "english": "Storage policy note.\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.\nAt most 4 retained snapshots of volume V may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nFour retained snapshots of volume V exist now.\nThe backup agent waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "ainglish": "Storage policy note.\nsnapshots stock-cap(4; retained snapshots of volume V).\nCounts below are as of now, before any further action.\nFour retained snapshots of volume V exist now.\nThe backup agent waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for three more",
      "Room for one more",
      "Room for two more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "storage",
    "semantic_frame": "stock-01-wait",
    "source_item_id": "rc-storage-stock-01-wait",
    "scope": "global"
  },
  {
    "id": "rc-storage-stock-02-wait-dxalloc-9",
    "english": "Storage policy note.\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.\nAt most 4 retained snapshots of volume V may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nFour retained snapshots of volume V exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. The backup agent waits twenty minutes and does nothing else; nothing else changes.",
    "ainglish": "Storage policy note.\nsnapshots stock-cap(4; retained snapshots of volume V).\nCounts below are as of now, before any further action.\nFour retained snapshots of volume V exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. The backup agent waits twenty minutes and does nothing else; nothing else changes.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for the full allowance of four",
      "Room for three more",
      "No room for another",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "storage",
    "semantic_frame": "stock-02-wait",
    "source_item_id": "rc-storage-stock-02-wait",
    "scope": "global"
  },
  {
    "id": "rc-storage-stock-03-release-dxalloc-0",
    "english": "Storage policy note.\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.\nAt most 4 retained snapshots of volume V may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three retained snapshots of volume V existed.\nBetween T0 and T1, the backup agent released one of them; nothing else changed.\nThe backup agent holds an authorisation to retain a snapshot that runs until the end of today.",
    "ainglish": "Storage policy note.\nsnapshots stock-cap(4; retained snapshots of volume V).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three retained snapshots of volume V existed.\nBetween T0 and T1, the backup agent released one of them; nothing else changed.\nThe backup agent holds an authorisation to retain a snapshot that runs until the end of today.",
    "question": "How much room is there under this cap at T1, immediately after that release?",
    "options": [
      "Room for the full allowance of four",
      "No room for another",
      "Room for one more",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "stock",
    "probe": "release",
    "domain": "storage",
    "semantic_frame": "stock-03-release",
    "source_item_id": "rc-storage-stock-03-release",
    "scope": "global"
  },
  {
    "id": "rc-storage-stock-04-delete-dxalloc-10",
    "english": "Storage policy note.\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.\nAt most 4 retained snapshots of volume V may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four retained snapshots of volume V existed, and six archived snapshots existed that were not in the named set.\nBetween T0 and T1, the backup agent deleted one of the retained snapshots of volume V; nothing else changed.",
    "ainglish": "Storage policy note.\nsnapshots stock-cap(4; retained snapshots of volume V).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four retained snapshots of volume V existed, and six archived snapshots existed that were not in the named set.\nBetween T0 and T1, the backup agent deleted one of the retained snapshots of volume V; nothing else changed.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for two more",
      "Room for one more",
      "No room for another",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "storage",
    "semantic_frame": "stock-04-delete",
    "source_item_id": "rc-storage-stock-04-delete",
    "scope": "global"
  },
  {
    "id": "rc-storage-stock-05-delete-dxalloc-7",
    "english": "Storage policy note.\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.\nAt most 4 retained snapshots of volume V may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four retained snapshots of volume V existed, and six archived snapshots existed that were not in the named set.\nBetween T0 and T1, the backup agent deleted one of the archived snapshots; no member of the named set changed.\nThe backup agent's authorisation to retain a snapshot was revoked this morning and has not been restored.",
    "ainglish": "Storage policy note.\nsnapshots stock-cap(4; retained snapshots of volume V).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four retained snapshots of volume V existed, and six archived snapshots existed that were not in the named set.\nBetween T0 and T1, the backup agent deleted one of the archived snapshots; no member of the named set changed.\nThe backup agent's authorisation to retain a snapshot was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for three more",
      "Room for two more",
      "No room for another",
      "Room for the full allowance of four",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "storage",
    "semantic_frame": "stock-05-delete",
    "source_item_id": "rc-storage-stock-05-delete",
    "scope": "global"
  },
  {
    "id": "rc-storage-stock-06-count-dxalloc-7",
    "english": "Storage policy note.\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.\nAt most 4 retained snapshots of volume V may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nThe backup agent has one snapshot in the named set now; the archive agent has two snapshots in the same named set; no other owner has any snapshot in that set. No membership changes.",
    "ainglish": "Storage policy note.\nsnapshots stock-cap(4; retained snapshots of volume V).\nCounts below are as of now, before any further action.\nThe backup agent has one snapshot in the named set now; the archive agent has two snapshots in the same named set; no other owner has any snapshot in that set. No membership changes.",
    "question": "How much room is there under this cap for the backup agent now?",
    "options": [
      "Room for the full allowance of four",
      "Room for three more",
      "Room for two more",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "storage",
    "semantic_frame": "stock-06-count",
    "source_item_id": "rc-storage-stock-06-count",
    "scope": "global"
  },
  {
    "id": "rc-storage-stock-07-count-dxalloc-1",
    "english": "Storage policy note.\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.\nAt most 4 retained snapshots of volume V may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of retained snapshots of volume V is not given.",
    "ainglish": "Storage policy note.\nsnapshots stock-cap(4; retained snapshots of volume V).\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of retained snapshots of volume V is not given.",
    "question": "Exactly how many retained snapshots of volume V exist now?",
    "options": [
      "Exactly four exist now",
      "Fewer than four exist now",
      "More than four exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "storage",
    "semantic_frame": "stock-07-count",
    "source_item_id": "rc-storage-stock-07-count",
    "scope": "global"
  },
  {
    "id": "rc-storage-stock-08-count-dxalloc-2",
    "english": "Storage policy note.\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.\nAt most 4 snapshots in each day; capacity returns as the day passes; the window slides, so any span of one day counts. At most 4 retained snapshots of volume V may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the span from two days ago to one day ago, the backup agent took four snapshots; none since.\nFour retained snapshots of volume V exist now and none is scheduled to leave.",
    "ainglish": "Storage policy note.\nsnapshots rate-cap(4; day). per-any(day). snapshots stock-cap(4; retained snapshots of volume V).\nCounts below are as of now, before any further action.\nIn the span from two days ago to one day ago, the backup agent took four snapshots; none since.\nFour retained snapshots of volume V exist now and none is scheduled to leave.",
    "question": "How much room is there now for one additional snapshot under both constraints together?",
    "options": [
      "Room for two more",
      "Room for the full allowance of four",
      "No room for another",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "storage",
    "semantic_frame": "stock-08-count",
    "source_item_id": "rc-storage-stock-08-count",
    "scope": "global"
  },
  {
    "id": "rc-seats-rate-01-wait-dxalloc-6",
    "english": "Licensing note. Budget for team T only.\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.\nAt most 6 activations in each day; capacity returns as the day passes; whether the day is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding day, team T performed six activations.\nTeam T holds an authorisation to activate a licence that runs until the end of today.",
    "ainglish": "Licensing note. Budget for team T only.\nactivations rate-cap(6; day).\nCounts below are as of now, before any further action.\nIn the preceding day, team T performed six activations.\nTeam T holds an authorisation to activate a licence that runs until the end of today.",
    "question": "If team T waits one full day from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for the full allowance of six",
      "No room for another",
      "Room for two more",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of six",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "seats",
    "semantic_frame": "rate-01-wait",
    "source_item_id": "rc-seats-rate-01-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-rate-02-wait-dxalloc-2",
    "english": "Licensing note. Budget for team T only.\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.\nAt most 6 activations in each day; capacity returns as the day passes; the count restarts at each clock day boundary.\nCounts below are as of now, before any further action.\nIn the current clock day, team T performed six activations.",
    "ainglish": "Licensing note. Budget for team T only.\nactivations rate-cap(6; day). per-clock(day).\nCounts below are as of now, before any further action.\nIn the current clock day, team T performed six activations.",
    "question": "If team T waits one full day from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for five more",
      "Room for three more",
      "No room for another",
      "Room for the full allowance of six",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of six",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "seats",
    "semantic_frame": "rate-02-wait",
    "source_item_id": "rc-seats-rate-02-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-rate-03-release-dxalloc-6",
    "english": "Licensing note. Budget for team T only.\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.\nAt most 6 activations in each day; capacity returns as the day passes; the window slides, so any span of one day counts.\nCounts below are as of now, before any further action.\nIn the preceding day, team T performed four activations, aged 4 hours, 6 hours, 8 hours and 10 hours.\nJust now, team T closed one of those activations; nothing else changed.",
    "ainglish": "Licensing note. Budget for team T only.\nactivations rate-cap(6; day). per-any(day).\nCounts below are as of now, before any further action.\nIn the preceding day, team T performed four activations, aged 4 hours, 6 hours, 8 hours and 10 hours.\nJust now, team T closed one of those activations; nothing else changed.",
    "question": "How much room is there under this cap now, immediately after that closure?",
    "options": [
      "Room for three more",
      "Room for five more",
      "No room for another",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "rate",
    "probe": "release",
    "domain": "seats",
    "semantic_frame": "rate-03-release",
    "source_item_id": "rc-seats-rate-03-release",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-rate-04-delete-dxalloc-3",
    "english": "Licensing note. Budget for team T only.\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.\nAt most 6 activations in each day; capacity returns as the day passes; whether the day is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding day, team T performed two activations, aged 2 hours and 4 hours.\nThe current time is 14:00 on Wednesday.\nJust now, team T deleted an older activation that it performed last week; nothing else changed.\nTeam T's authorisation to activate a licence was revoked this morning and has not been restored.",
    "ainglish": "Licensing note. Budget for team T only.\nactivations rate-cap(6; day).\nCounts below are as of now, before any further action.\nIn the preceding day, team T performed two activations, aged 2 hours and 4 hours.\nThe current time is 14:00 on Wednesday.\nJust now, team T deleted an older activation that it performed last week; nothing else changed.\nTeam T's authorisation to activate a licence was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap now, immediately after that deletion?",
    "options": [
      "Room for one more",
      "Room for four more",
      "Room for two more",
      "Room for five more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for four more",
    "settlement_stratum": "rate",
    "probe": "delete",
    "domain": "seats",
    "semantic_frame": "rate-04-delete",
    "source_item_id": "rc-seats-rate-04-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-rate-05-count-dxalloc-4",
    "english": "Licensing note. Budget for team T only.\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.\nAt most 6 activations in each day; capacity returns as the day passes; the window slides, so any span of one day counts.\nCounts below are as of now, before any further action.\nTeam T performed four activations: two of them 2 hours and 4 hours ago, and two of them 36 hours and 48 hours ago.\nTeam U performed three activations in the preceding day.",
    "ainglish": "Licensing note. Budget for team T only.\nactivations rate-cap(6; day). per-any(day).\nCounts below are as of now, before any further action.\nTeam T performed four activations: two of them 2 hours and 4 hours ago, and two of them 36 hours and 48 hours ago.\nTeam U performed three activations in the preceding day.",
    "question": "How much room is there under this cap for team T now?",
    "options": [
      "Room for one more",
      "Room for five more",
      "Room for two more",
      "Room for four more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for four more",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "seats",
    "semantic_frame": "rate-05-count",
    "source_item_id": "rc-seats-rate-05-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-rate-06-count-dxalloc-0",
    "english": "Licensing note. Budget for team T only.\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.\nAt most 6 activations in each day; capacity returns as the day passes; whether the day is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of activations is given.",
    "ainglish": "Licensing note. Budget for team T only.\nactivations rate-cap(6; day).\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of activations is given.",
    "question": "How many activations exist now?",
    "options": [
      "Exactly six exist now",
      "Fewer than six exist now",
      "More than six exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "seats",
    "semantic_frame": "rate-06-count",
    "source_item_id": "rc-seats-rate-06-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-rate-07-boundary-dxalloc-1",
    "english": "Licensing note. Budget for team T only.\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.\nAt most 6 activations in each day; capacity returns as the day passes; whether the day is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nThe day boundary falls at midnight. Team T plans six activations just before the boundary and six more just after it, with nothing else performed in the surrounding span.",
    "ainglish": "Licensing note. Budget for team T only.\nactivations rate-cap(6; day).\nCounts below are as of now, before any further action.\nThe day boundary falls at midnight. Team T plans six activations just before the boundary and six more just after it, with nothing else performed in the surrounding span.",
    "question": "Can both planned bursts be legal under this cap?",
    "options": [
      "Yes, both bursts can be legal",
      "No, at most one of the two bursts can be legal",
      "Only the burst before the boundary can be legal",
      "Only the burst after the boundary can be legal",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "rate",
    "probe": "boundary",
    "domain": "seats",
    "semantic_frame": "rate-07-boundary",
    "source_item_id": "rc-seats-rate-07-boundary",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-rate-08-count-dxalloc-5",
    "english": "Licensing note. Budget for team T only.\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.\nAt most 6 activations in each day; capacity returns as the day passes; the window slides, so any span of one day counts. At most 5 active seats held by team T may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the preceding day, team T performed six activations, aged 4 hours, 5 hours, 6 hours, 7 hours, 8 hours and 9 hours.\nThree active seats held by team T exist now.",
    "ainglish": "Licensing note. Budget for team T only.\nactivations rate-cap(6; day). per-any(day). seats stock-cap(5; active seats held by team T).\nCounts below are as of now, before any further action.\nIn the preceding day, team T performed six activations, aged 4 hours, 5 hours, 6 hours, 7 hours, 8 hours and 9 hours.\nThree active seats held by team T exist now.",
    "question": "How much room is there now for one additional activation under both constraints together?",
    "options": [
      "Room for five more",
      "Room for the full allowance of six",
      "Room for one more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "seats",
    "semantic_frame": "rate-08-count",
    "source_item_id": "rc-seats-rate-08-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-stock-01-wait-dxalloc-0",
    "english": "Licensing note.\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.\nAt most 5 active seats held by team T may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nFive active seats held by team T exist now.\nTeam T waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "ainglish": "Licensing note.\nseats stock-cap(5; active seats held by team T).\nCounts below are as of now, before any further action.\nFive active seats held by team T exist now.\nTeam T waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for the full allowance of five",
      "Room for four more",
      "No room for another",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "seats",
    "semantic_frame": "stock-01-wait",
    "source_item_id": "rc-seats-stock-01-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-stock-02-wait-dxalloc-2",
    "english": "Licensing note.\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.\nAt most 5 active seats held by team T may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nFive active seats held by team T exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. Team T waits twenty minutes and does nothing else; nothing else changes.",
    "ainglish": "Licensing note.\nseats stock-cap(5; active seats held by team T).\nCounts below are as of now, before any further action.\nFive active seats held by team T exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. Team T waits twenty minutes and does nothing else; nothing else changes.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for one more",
      "Room for the full allowance of five",
      "Room for two more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "seats",
    "semantic_frame": "stock-02-wait",
    "source_item_id": "rc-seats-stock-02-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-stock-03-release-dxalloc-8",
    "english": "Licensing note.\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.\nAt most 5 active seats held by team T may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four active seats held by team T existed.\nBetween T0 and T1, team T released one of them; nothing else changed.\nTeam T holds an authorisation to claim a seat that runs until the end of today.",
    "ainglish": "Licensing note.\nseats stock-cap(5; active seats held by team T).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four active seats held by team T existed.\nBetween T0 and T1, team T released one of them; nothing else changed.\nTeam T holds an authorisation to claim a seat that runs until the end of today.",
    "question": "How much room is there under this cap at T1, immediately after that release?",
    "options": [
      "Room for the full allowance of five",
      "Room for one more",
      "Room for two more",
      "Room for four more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "stock",
    "probe": "release",
    "domain": "seats",
    "semantic_frame": "stock-03-release",
    "source_item_id": "rc-seats-stock-03-release",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-stock-04-delete-dxalloc-1",
    "english": "Licensing note.\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.\nAt most 5 active seats held by team T may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, five active seats held by team T existed, and six archived seats existed that were not in the named set.\nBetween T0 and T1, team T deleted one of the active seats held by team T; nothing else changed.",
    "ainglish": "Licensing note.\nseats stock-cap(5; active seats held by team T).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, five active seats held by team T existed, and six archived seats existed that were not in the named set.\nBetween T0 and T1, team T deleted one of the active seats held by team T; nothing else changed.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for three more",
      "Room for one more",
      "Room for four more",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "seats",
    "semantic_frame": "stock-04-delete",
    "source_item_id": "rc-seats-stock-04-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-stock-05-delete-dxalloc-2",
    "english": "Licensing note.\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.\nAt most 5 active seats held by team T may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, five active seats held by team T existed, and six archived seats existed that were not in the named set.\nBetween T0 and T1, team T deleted one of the archived seats; no member of the named set changed.\nTeam T's authorisation to claim a seat was revoked this morning and has not been restored.",
    "ainglish": "Licensing note.\nseats stock-cap(5; active seats held by team T).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, five active seats held by team T existed, and six archived seats existed that were not in the named set.\nBetween T0 and T1, team T deleted one of the archived seats; no member of the named set changed.\nTeam T's authorisation to claim a seat was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "No room for another",
      "Room for the full allowance of five",
      "Room for four more",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "seats",
    "semantic_frame": "stock-05-delete",
    "source_item_id": "rc-seats-stock-05-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-stock-06-count-dxalloc-4",
    "english": "Licensing note.\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.\nAt most 5 active seats held by team T may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nTeam T has one seat in the named set now; team U has two seats of the same kind, which belong to team U and not to team T. No membership changes.",
    "ainglish": "Licensing note.\nseats stock-cap(5; active seats held by team T).\nCounts below are as of now, before any further action.\nTeam T has one seat in the named set now; team U has two seats of the same kind, which belong to team U and not to team T. No membership changes.",
    "question": "How much room is there under this cap for team T now?",
    "options": [
      "Room for four more",
      "Room for three more",
      "Room for two more",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for four more",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "seats",
    "semantic_frame": "stock-06-count",
    "source_item_id": "rc-seats-stock-06-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-stock-07-count-dxalloc-9",
    "english": "Licensing note.\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.\nAt most 5 active seats held by team T may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of active seats held by team T is not given.",
    "ainglish": "Licensing note.\nseats stock-cap(5; active seats held by team T).\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of active seats held by team T is not given.",
    "question": "Exactly how many active seats held by team T exist now?",
    "options": [
      "Exactly five exist now",
      "Fewer than five exist now",
      "More than five exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "seats",
    "semantic_frame": "stock-07-count",
    "source_item_id": "rc-seats-stock-07-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-seats-stock-08-count-dxalloc-3",
    "english": "Licensing note.\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.\nAt most 4 activations in each day; capacity returns as the day passes; the window slides, so any span of one day counts. At most 5 active seats held by team T may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the span from two days ago to one day ago, team T performed four activations; none since.\nFive active seats held by team T exist now and none is scheduled to leave.",
    "ainglish": "Licensing note.\nactivations rate-cap(4; day). per-any(day). seats stock-cap(5; active seats held by team T).\nCounts below are as of now, before any further action.\nIn the span from two days ago to one day ago, team T performed four activations; none since.\nFive active seats held by team T exist now and none is scheduled to leave.",
    "question": "How much room is there now for one additional seat under both constraints together?",
    "options": [
      "Room for the full allowance of five",
      "No room for another",
      "Room for one more",
      "Room for four more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "seats",
    "semantic_frame": "stock-08-count",
    "source_item_id": "rc-seats-stock-08-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-connections-rate-01-wait-dxalloc-2",
    "english": "Connection pool note. Budget shared by every actor on this service.\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.\nAt most 8 connections in each minute; capacity returns as the minute passes; whether the minute is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding minute, worker A opened eight connections.\nNo other actor opens a connection during the coming minute.\nWorker A holds an authorisation to open a connection that runs until the end of today.",
    "ainglish": "Connection pool note. Budget shared by every actor on this service.\nconnections rate-cap(8; minute).\nCounts below are as of now, before any further action.\nIn the preceding minute, worker A opened eight connections.\nNo other actor opens a connection during the coming minute.\nWorker A holds an authorisation to open a connection that runs until the end of today.",
    "question": "If worker A waits one full minute from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "No room for another",
      "Room for seven more",
      "Room for the full allowance of eight",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of eight",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "connections",
    "semantic_frame": "rate-01-wait",
    "source_item_id": "rc-connections-rate-01-wait",
    "scope": "global"
  },
  {
    "id": "rc-connections-rate-02-wait-dxalloc-10",
    "english": "Connection pool note. Budget shared by every actor on this service.\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.\nAt most 8 connections in each minute; capacity returns as the minute passes; the count restarts at each clock minute boundary.\nCounts below are as of now, before any further action.\nIn the current clock minute, worker A opened eight connections.\nNo other actor opens a connection during the coming minute.",
    "ainglish": "Connection pool note. Budget shared by every actor on this service.\nconnections rate-cap(8; minute). per-clock(minute).\nCounts below are as of now, before any further action.\nIn the current clock minute, worker A opened eight connections.\nNo other actor opens a connection during the coming minute.",
    "question": "If worker A waits one full minute from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for seven more",
      "Room for one more",
      "No room for another",
      "Room for the full allowance of eight",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of eight",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "connections",
    "semantic_frame": "rate-02-wait",
    "source_item_id": "rc-connections-rate-02-wait",
    "scope": "global"
  },
  {
    "id": "rc-connections-rate-03-release-dxalloc-2",
    "english": "Connection pool note. Budget shared by every actor on this service.\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.\nAt most 8 connections in each minute; capacity returns as the minute passes; the window slides, so any span of one minute counts.\nCounts below are as of now, before any further action.\nIn the preceding minute, worker A opened six connections, aged 10 seconds, 15 seconds, 20 seconds, 25 seconds, 30 seconds and 35 seconds.\nNo other actor opened any connections in the preceding minute.\nJust now, worker A closed one of those connections; nothing else changed.",
    "ainglish": "Connection pool note. Budget shared by every actor on this service.\nconnections rate-cap(8; minute). per-any(minute).\nCounts below are as of now, before any further action.\nIn the preceding minute, worker A opened six connections, aged 10 seconds, 15 seconds, 20 seconds, 25 seconds, 30 seconds and 35 seconds.\nNo other actor opened any connections in the preceding minute.\nJust now, worker A closed one of those connections; nothing else changed.",
    "question": "How much room is there under this cap now, immediately after that closure?",
    "options": [
      "No room for another",
      "Room for two more",
      "Room for one more",
      "Room for seven more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "rate",
    "probe": "release",
    "domain": "connections",
    "semantic_frame": "rate-03-release",
    "source_item_id": "rc-connections-rate-03-release",
    "scope": "global"
  },
  {
    "id": "rc-connections-rate-04-delete-dxalloc-1",
    "english": "Connection pool note. Budget shared by every actor on this service.\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.\nAt most 8 connections in each minute; capacity returns as the minute passes; whether the minute is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding minute, worker A opened two connections, aged 6 seconds and 10 seconds.\nNo other actor opened any connections in the preceding minute.\nThe current time is 10:40:30.\nJust now, worker A deleted an older connection that it opened last week; nothing else changed.\nWorker A's authorisation to open a connection was revoked this morning and has not been restored.",
    "ainglish": "Connection pool note. Budget shared by every actor on this service.\nconnections rate-cap(8; minute).\nCounts below are as of now, before any further action.\nIn the preceding minute, worker A opened two connections, aged 6 seconds and 10 seconds.\nNo other actor opened any connections in the preceding minute.\nThe current time is 10:40:30.\nJust now, worker A deleted an older connection that it opened last week; nothing else changed.\nWorker A's authorisation to open a connection was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap now, immediately after that deletion?",
    "options": [
      "Room for one more",
      "Room for three more",
      "Room for six more",
      "Room for seven more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for six more",
    "settlement_stratum": "rate",
    "probe": "delete",
    "domain": "connections",
    "semantic_frame": "rate-04-delete",
    "source_item_id": "rc-connections-rate-04-delete",
    "scope": "global"
  },
  {
    "id": "rc-connections-rate-05-count-dxalloc-0",
    "english": "Connection pool note. Budget shared by every actor on this service.\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.\nAt most 8 connections in each minute; capacity returns as the minute passes; the window slides, so any span of one minute counts.\nCounts below are as of now, before any further action.\nWorker A opened four connections: two of them 6 seconds and 12 seconds ago, and two of them 90 seconds and 120 seconds ago.\nWorker B opened three connections in the preceding minute.\nNo actor other than worker A and worker B opened any connections in the preceding minute.",
    "ainglish": "Connection pool note. Budget shared by every actor on this service.\nconnections rate-cap(8; minute). per-any(minute).\nCounts below are as of now, before any further action.\nWorker A opened four connections: two of them 6 seconds and 12 seconds ago, and two of them 90 seconds and 120 seconds ago.\nWorker B opened three connections in the preceding minute.\nNo actor other than worker A and worker B opened any connections in the preceding minute.",
    "question": "How much room is there under this cap for worker A now?",
    "options": [
      "Room for three more",
      "Room for seven more",
      "Room for two more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for three more",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "connections",
    "semantic_frame": "rate-05-count",
    "source_item_id": "rc-connections-rate-05-count",
    "scope": "global"
  },
  {
    "id": "rc-connections-rate-06-count-dxalloc-4",
    "english": "Connection pool note. Budget shared by every actor on this service.\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.\nAt most 8 connections in each minute; capacity returns as the minute passes; whether the minute is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of connections is given.",
    "ainglish": "Connection pool note. Budget shared by every actor on this service.\nconnections rate-cap(8; minute).\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of connections is given.",
    "question": "How many connections exist now?",
    "options": [
      "Exactly eight exist now",
      "Fewer than eight exist now",
      "More than eight exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "connections",
    "semantic_frame": "rate-06-count",
    "source_item_id": "rc-connections-rate-06-count",
    "scope": "global"
  },
  {
    "id": "rc-connections-rate-07-boundary-dxalloc-0",
    "english": "Connection pool note. Budget shared by every actor on this service.\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.\nAt most 8 connections in each minute; capacity returns as the minute passes; the count restarts at each clock minute boundary.\nCounts below are as of now, before any further action.\nThe minute boundary falls at the top of the minute. Worker A plans eight connections just before the boundary and eight more just after it, with nothing else opened in the surrounding span.",
    "ainglish": "Connection pool note. Budget shared by every actor on this service.\nconnections rate-cap(8; minute). per-clock(minute).\nCounts below are as of now, before any further action.\nThe minute boundary falls at the top of the minute. Worker A plans eight connections just before the boundary and eight more just after it, with nothing else opened in the surrounding span.",
    "question": "Can both planned bursts be legal under this cap?",
    "options": [
      "Yes, both bursts can be legal",
      "No, at most one of the two bursts can be legal",
      "Only the burst before the boundary can be legal",
      "Only the burst after the boundary can be legal",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Yes, both bursts can be legal",
    "settlement_stratum": "rate",
    "probe": "boundary",
    "domain": "connections",
    "semantic_frame": "rate-07-boundary",
    "source_item_id": "rc-connections-rate-07-boundary",
    "scope": "global"
  },
  {
    "id": "rc-connections-rate-08-count-dxalloc-4",
    "english": "Connection pool note. Budget shared by every actor on this service.\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.\nAt most 8 connections in each minute; capacity returns as the minute passes; the window slides, so any span of one minute counts. At most 5 open connections owned by worker A may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the preceding minute, worker A opened eight connections, aged 10 seconds, 13 seconds, 16 seconds, 19 seconds, 22 seconds, 25 seconds, 28 seconds and 31 seconds.\nNo other actor opened any connections in the preceding minute.\nThree open connections owned by worker A exist now.",
    "ainglish": "Connection pool note. Budget shared by every actor on this service.\nconnections rate-cap(8; minute). per-any(minute). connections stock-cap(5; open connections owned by worker A).\nCounts below are as of now, before any further action.\nIn the preceding minute, worker A opened eight connections, aged 10 seconds, 13 seconds, 16 seconds, 19 seconds, 22 seconds, 25 seconds, 28 seconds and 31 seconds.\nNo other actor opened any connections in the preceding minute.\nThree open connections owned by worker A exist now.",
    "question": "How much room is there now for one additional connection under both constraints together?",
    "options": [
      "Room for three more",
      "Room for one more",
      "No room for another",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "connections",
    "semantic_frame": "rate-08-count",
    "source_item_id": "rc-connections-rate-08-count",
    "scope": "global"
  },
  {
    "id": "rc-connections-stock-01-wait-dxalloc-2",
    "english": "Connection pool note.\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.\nAt most 3 open connections owned by worker A may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nThree open connections owned by worker A exist now.\nWorker A waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "ainglish": "Connection pool note.\nconnections stock-cap(3; open connections owned by worker A).\nCounts below are as of now, before any further action.\nThree open connections owned by worker A exist now.\nWorker A waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for two more",
      "Room for one more",
      "Room for the full allowance of three",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "connections",
    "semantic_frame": "stock-01-wait",
    "source_item_id": "rc-connections-stock-01-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-connections-stock-02-wait-dxalloc-1",
    "english": "Connection pool note.\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.\nAt most 3 open connections owned by worker A may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nThree open connections owned by worker A exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. Worker A waits twenty minutes and does nothing else; nothing else changes.",
    "ainglish": "Connection pool note.\nconnections stock-cap(3; open connections owned by worker A).\nCounts below are as of now, before any further action.\nThree open connections owned by worker A exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. Worker A waits twenty minutes and does nothing else; nothing else changes.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for the full allowance of three",
      "Room for two more",
      "No room for another",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "connections",
    "semantic_frame": "stock-02-wait",
    "source_item_id": "rc-connections-stock-02-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-connections-stock-03-release-dxalloc-0",
    "english": "Connection pool note.\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.\nAt most 3 open connections owned by worker A may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, two open connections owned by worker A existed.\nBetween T0 and T1, worker A released one of them; nothing else changed.\nWorker A holds an authorisation to open a connection that runs until the end of today.",
    "ainglish": "Connection pool note.\nconnections stock-cap(3; open connections owned by worker A).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, two open connections owned by worker A existed.\nBetween T0 and T1, worker A released one of them; nothing else changed.\nWorker A holds an authorisation to open a connection that runs until the end of today.",
    "question": "How much room is there under this cap at T1, immediately after that release?",
    "options": [
      "No room for another",
      "Room for one more",
      "Room for the full allowance of three",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "stock",
    "probe": "release",
    "domain": "connections",
    "semantic_frame": "stock-03-release",
    "source_item_id": "rc-connections-stock-03-release",
    "scope": "per-identity"
  },
  {
    "id": "rc-connections-stock-04-delete-dxalloc-5",
    "english": "Connection pool note.\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.\nAt most 3 open connections owned by worker A may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three open connections owned by worker A existed, and six archived connections existed that were not in the named set.\nBetween T0 and T1, worker A deleted one of the open connections owned by worker A; nothing else changed.",
    "ainglish": "Connection pool note.\nconnections stock-cap(3; open connections owned by worker A).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three open connections owned by worker A existed, and six archived connections existed that were not in the named set.\nBetween T0 and T1, worker A deleted one of the open connections owned by worker A; nothing else changed.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for two more",
      "No room for another",
      "Room for the full allowance of three",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "connections",
    "semantic_frame": "stock-04-delete",
    "source_item_id": "rc-connections-stock-04-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-connections-stock-05-delete-dxalloc-0",
    "english": "Connection pool note.\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.\nAt most 3 open connections owned by worker A may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three open connections owned by worker A existed, and six archived connections existed that were not in the named set.\nBetween T0 and T1, worker A deleted one of the archived connections; no member of the named set changed.\nWorker A's authorisation to open a connection was revoked this morning and has not been restored.",
    "ainglish": "Connection pool note.\nconnections stock-cap(3; open connections owned by worker A).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three open connections owned by worker A existed, and six archived connections existed that were not in the named set.\nBetween T0 and T1, worker A deleted one of the archived connections; no member of the named set changed.\nWorker A's authorisation to open a connection was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for the full allowance of three",
      "Room for one more",
      "No room for another",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "connections",
    "semantic_frame": "stock-05-delete",
    "source_item_id": "rc-connections-stock-05-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-connections-stock-06-count-dxalloc-8",
    "english": "Connection pool note.\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.\nAt most 3 open connections owned by worker A may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nWorker A has one connection in the named set now; worker B has two connections of the same kind, which belong to worker B and not to worker A. No membership changes.",
    "ainglish": "Connection pool note.\nconnections stock-cap(3; open connections owned by worker A).\nCounts below are as of now, before any further action.\nWorker A has one connection in the named set now; worker B has two connections of the same kind, which belong to worker B and not to worker A. No membership changes.",
    "question": "How much room is there under this cap for worker A now?",
    "options": [
      "No room for another",
      "Room for the full allowance of three",
      "Room for two more",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "connections",
    "semantic_frame": "stock-06-count",
    "source_item_id": "rc-connections-stock-06-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-connections-stock-07-count-dxalloc-4",
    "english": "Connection pool note.\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.\nAt most 3 open connections owned by worker A may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of open connections owned by worker A is not given.",
    "ainglish": "Connection pool note.\nconnections stock-cap(3; open connections owned by worker A).\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of open connections owned by worker A is not given.",
    "question": "Exactly how many open connections owned by worker A exist now?",
    "options": [
      "Exactly three exist now",
      "Fewer than three exist now",
      "More than three exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "connections",
    "semantic_frame": "stock-07-count",
    "source_item_id": "rc-connections-stock-07-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-connections-stock-08-count-dxalloc-4",
    "english": "Connection pool note.\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.\nAt most 4 connections in each minute; capacity returns as the minute passes; the window slides, so any span of one minute counts. At most 3 open connections owned by worker A may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the span from two minutes ago to one minute ago, worker A opened four connections; none since.\nThree open connections owned by worker A exist now and none is scheduled to leave.",
    "ainglish": "Connection pool note.\nconnections rate-cap(4; minute). per-any(minute). connections stock-cap(3; open connections owned by worker A).\nCounts below are as of now, before any further action.\nIn the span from two minutes ago to one minute ago, worker A opened four connections; none since.\nThree open connections owned by worker A exist now and none is scheduled to leave.",
    "question": "How much room is there now for one additional connection under both constraints together?",
    "options": [
      "Room for two more",
      "No room for another",
      "Room for one more",
      "Room for the full allowance of three",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "connections",
    "semantic_frame": "stock-08-count",
    "source_item_id": "rc-connections-stock-08-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-messages-rate-01-wait-dxalloc-0",
    "english": "Messaging note. Budget for this sender only.\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.\nAt most 3 messages in each day; capacity returns as the day passes; whether the day is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding day, this sender sent three messages.\nThis sender holds an authorisation to send a message that runs until the end of today.",
    "ainglish": "Messaging note. Budget for this sender only.\nmessages rate-cap(3; day).\nCounts below are as of now, before any further action.\nIn the preceding day, this sender sent three messages.\nThis sender holds an authorisation to send a message that runs until the end of today.",
    "question": "If this sender waits one full day from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for the full allowance of three",
      "Room for one more",
      "No room for another",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of three",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "messages",
    "semantic_frame": "rate-01-wait",
    "source_item_id": "rc-messages-rate-01-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-messages-rate-02-wait-dxalloc-0",
    "english": "Messaging note. Budget for this sender only.\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.\nAt most 3 messages in each day; capacity returns as the day passes; the count restarts at each clock day boundary.\nCounts below are as of now, before any further action.\nIn the current clock day, this sender sent three messages.",
    "ainglish": "Messaging note. Budget for this sender only.\nmessages rate-cap(3; day). per-clock(day).\nCounts below are as of now, before any further action.\nIn the current clock day, this sender sent three messages.",
    "question": "If this sender waits one full day from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for two more",
      "Room for the full allowance of three",
      "No room for another",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of three",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "messages",
    "semantic_frame": "rate-02-wait",
    "source_item_id": "rc-messages-rate-02-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-messages-rate-03-release-dxalloc-9",
    "english": "Messaging note. Budget for this sender only.\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.\nAt most 3 messages in each day; capacity returns as the day passes; the window slides, so any span of one day counts.\nCounts below are as of now, before any further action.\nIn the preceding day, this sender sent one messages, aged 4 hours.\nJust now, this sender closed one of those messages; nothing else changed.",
    "ainglish": "Messaging note. Budget for this sender only.\nmessages rate-cap(3; day). per-any(day).\nCounts below are as of now, before any further action.\nIn the preceding day, this sender sent one messages, aged 4 hours.\nJust now, this sender closed one of those messages; nothing else changed.",
    "question": "How much room is there under this cap now, immediately after that closure?",
    "options": [
      "No room for another",
      "Room for the full allowance of three",
      "Room for two more",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "rate",
    "probe": "release",
    "domain": "messages",
    "semantic_frame": "rate-03-release",
    "source_item_id": "rc-messages-rate-03-release",
    "scope": "per-identity"
  },
  {
    "id": "rc-messages-rate-04-delete-dxalloc-3",
    "english": "Messaging note. Budget for this sender only.\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.\nAt most 3 messages in each day; capacity returns as the day passes; whether the day is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding day, this sender sent two messages, aged 2 hours and 4 hours.\nThe current time is 14:00 on Wednesday.\nJust now, this sender deleted an older message that it sent last week; nothing else changed.\nThis sender's authorisation to send a message was revoked this morning and has not been restored.",
    "ainglish": "Messaging note. Budget for this sender only.\nmessages rate-cap(3; day).\nCounts below are as of now, before any further action.\nIn the preceding day, this sender sent two messages, aged 2 hours and 4 hours.\nThe current time is 14:00 on Wednesday.\nJust now, this sender deleted an older message that it sent last week; nothing else changed.\nThis sender's authorisation to send a message was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap now, immediately after that deletion?",
    "options": [
      "No room for another",
      "Room for two more",
      "Room for the full allowance of three",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "rate",
    "probe": "delete",
    "domain": "messages",
    "semantic_frame": "rate-04-delete",
    "source_item_id": "rc-messages-rate-04-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-messages-rate-05-count-dxalloc-1",
    "english": "Messaging note. Budget for this sender only.\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.\nAt most 3 messages in each day; capacity returns as the day passes; the window slides, so any span of one day counts.\nCounts below are as of now, before any further action.\nThis sender sent four messages: two of them 2 hours and 4 hours ago, and two of them 36 hours and 48 hours ago.\nAnother sender sent three messages in the preceding day.",
    "ainglish": "Messaging note. Budget for this sender only.\nmessages rate-cap(3; day). per-any(day).\nCounts below are as of now, before any further action.\nThis sender sent four messages: two of them 2 hours and 4 hours ago, and two of them 36 hours and 48 hours ago.\nAnother sender sent three messages in the preceding day.",
    "question": "How much room is there under this cap for this sender now?",
    "options": [
      "Room for one more",
      "Room for two more",
      "Room for the full allowance of three",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "messages",
    "semantic_frame": "rate-05-count",
    "source_item_id": "rc-messages-rate-05-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-messages-rate-06-count-dxalloc-4",
    "english": "Messaging note. Budget for this sender only.\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.\nAt most 3 messages in each day; capacity returns as the day passes; whether the day is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of messages is given.",
    "ainglish": "Messaging note. Budget for this sender only.\nmessages rate-cap(3; day).\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of messages is given.",
    "question": "How many messages exist now?",
    "options": [
      "Exactly three exist now",
      "Fewer than three exist now",
      "More than three exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "messages",
    "semantic_frame": "rate-06-count",
    "source_item_id": "rc-messages-rate-06-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-messages-rate-07-boundary-dxalloc-2",
    "english": "Messaging note. Budget for this sender only.\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.\nAt most 3 messages in each day; capacity returns as the day passes; the window slides, so any span of one day counts.\nCounts below are as of now, before any further action.\nThe day boundary falls at midnight. This sender plans three messages just before the boundary and three more just after it, with nothing else sent in the surrounding span.",
    "ainglish": "Messaging note. Budget for this sender only.\nmessages rate-cap(3; day). per-any(day).\nCounts below are as of now, before any further action.\nThe day boundary falls at midnight. This sender plans three messages just before the boundary and three more just after it, with nothing else sent in the surrounding span.",
    "question": "Can both planned bursts be legal under this cap?",
    "options": [
      "Yes, both bursts can be legal",
      "No, at most one of the two bursts can be legal",
      "Only the burst before the boundary can be legal",
      "Only the burst after the boundary can be legal",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No, at most one of the two bursts can be legal",
    "settlement_stratum": "rate",
    "probe": "boundary",
    "domain": "messages",
    "semantic_frame": "rate-07-boundary",
    "source_item_id": "rc-messages-rate-07-boundary",
    "scope": "per-identity"
  },
  {
    "id": "rc-messages-rate-08-count-dxalloc-4",
    "english": "Messaging note. Budget for this sender only.\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.\nAt most 3 messages in each day; capacity returns as the day passes; the window slides, so any span of one day counts. At most 5 queued messages in mailbox M may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the preceding day, this sender sent three messages, aged 4 hours, 5 hours and 6 hours.\nThree queued messages in mailbox M exist now.",
    "ainglish": "Messaging note. Budget for this sender only.\nmessages rate-cap(3; day). per-any(day). messages stock-cap(5; queued messages in mailbox M).\nCounts below are as of now, before any further action.\nIn the preceding day, this sender sent three messages, aged 4 hours, 5 hours and 6 hours.\nThree queued messages in mailbox M exist now.",
    "question": "How much room is there now for one additional message under both constraints together?",
    "options": [
      "Room for one more",
      "Room for the full allowance of three",
      "No room for another",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "messages",
    "semantic_frame": "rate-08-count",
    "source_item_id": "rc-messages-rate-08-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-messages-stock-01-wait-dxalloc-0",
    "english": "Messaging note.\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.\nAt most 6 queued messages in mailbox M may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nSix queued messages in mailbox M exist now.\nThis sender waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "ainglish": "Messaging note.\nmessages stock-cap(6; queued messages in mailbox M).\nCounts below are as of now, before any further action.\nSix queued messages in mailbox M exist now.\nThis sender waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for the full allowance of six",
      "Room for two more",
      "No room for another",
      "Room for five more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "messages",
    "semantic_frame": "stock-01-wait",
    "source_item_id": "rc-messages-stock-01-wait",
    "scope": "global"
  },
  {
    "id": "rc-messages-stock-02-wait-dxalloc-3",
    "english": "Messaging note.\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.\nAt most 6 queued messages in mailbox M may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nSix queued messages in mailbox M exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. This sender waits twenty minutes and does nothing else; nothing else changes.",
    "ainglish": "Messaging note.\nmessages stock-cap(6; queued messages in mailbox M).\nCounts below are as of now, before any further action.\nSix queued messages in mailbox M exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. This sender waits twenty minutes and does nothing else; nothing else changes.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for the full allowance of six",
      "Room for one more",
      "Room for three more",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "messages",
    "semantic_frame": "stock-02-wait",
    "source_item_id": "rc-messages-stock-02-wait",
    "scope": "global"
  },
  {
    "id": "rc-messages-stock-03-release-dxalloc-4",
    "english": "Messaging note.\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.\nAt most 6 queued messages in mailbox M may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, five queued messages in mailbox M existed.\nBetween T0 and T1, this sender released one of them; nothing else changed.\nThis sender holds an authorisation to queue a message that runs until the end of today.",
    "ainglish": "Messaging note.\nmessages stock-cap(6; queued messages in mailbox M).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, five queued messages in mailbox M existed.\nBetween T0 and T1, this sender released one of them; nothing else changed.\nThis sender holds an authorisation to queue a message that runs until the end of today.",
    "question": "How much room is there under this cap at T1, immediately after that release?",
    "options": [
      "No room for another",
      "Room for one more",
      "Room for two more",
      "Room for five more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "stock",
    "probe": "release",
    "domain": "messages",
    "semantic_frame": "stock-03-release",
    "source_item_id": "rc-messages-stock-03-release",
    "scope": "global"
  },
  {
    "id": "rc-messages-stock-04-delete-dxalloc-0",
    "english": "Messaging note.\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.\nAt most 6 queued messages in mailbox M may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, six queued messages in mailbox M existed, and six archived messages existed that were not in the named set.\nBetween T0 and T1, this sender deleted one of the queued messages in mailbox M; nothing else changed.",
    "ainglish": "Messaging note.\nmessages stock-cap(6; queued messages in mailbox M).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, six queued messages in mailbox M existed, and six archived messages existed that were not in the named set.\nBetween T0 and T1, this sender deleted one of the queued messages in mailbox M; nothing else changed.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for the full allowance of six",
      "Room for three more",
      "No room for another",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "messages",
    "semantic_frame": "stock-04-delete",
    "source_item_id": "rc-messages-stock-04-delete",
    "scope": "global"
  },
  {
    "id": "rc-messages-stock-05-delete-dxalloc-8",
    "english": "Messaging note.\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.\nAt most 6 queued messages in mailbox M may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, six queued messages in mailbox M existed, and six archived messages existed that were not in the named set.\nBetween T0 and T1, this sender deleted one of the archived messages; no member of the named set changed.\nThis sender's authorisation to queue a message was revoked this morning and has not been restored.",
    "ainglish": "Messaging note.\nmessages stock-cap(6; queued messages in mailbox M).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, six queued messages in mailbox M existed, and six archived messages existed that were not in the named set.\nBetween T0 and T1, this sender deleted one of the archived messages; no member of the named set changed.\nThis sender's authorisation to queue a message was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for three more",
      "Room for the full allowance of six",
      "No room for another",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "messages",
    "semantic_frame": "stock-05-delete",
    "source_item_id": "rc-messages-stock-05-delete",
    "scope": "global"
  },
  {
    "id": "rc-messages-stock-06-count-dxalloc-0",
    "english": "Messaging note.\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.\nAt most 6 queued messages in mailbox M may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nThis sender has one message in the named set now; another sender has two messages in the same named set; no other owner has any message in that set. No membership changes.",
    "ainglish": "Messaging note.\nmessages stock-cap(6; queued messages in mailbox M).\nCounts below are as of now, before any further action.\nThis sender has one message in the named set now; another sender has two messages in the same named set; no other owner has any message in that set. No membership changes.",
    "question": "How much room is there under this cap for this sender now?",
    "options": [
      "Room for five more",
      "Room for two more",
      "Room for three more",
      "Room for the full allowance of six",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for three more",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "messages",
    "semantic_frame": "stock-06-count",
    "source_item_id": "rc-messages-stock-06-count",
    "scope": "global"
  },
  {
    "id": "rc-messages-stock-07-count-dxalloc-2",
    "english": "Messaging note.\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.\nAt most 6 queued messages in mailbox M may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of queued messages in mailbox M is not given.",
    "ainglish": "Messaging note.\nmessages stock-cap(6; queued messages in mailbox M).\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of queued messages in mailbox M is not given.",
    "question": "Exactly how many queued messages in mailbox M exist now?",
    "options": [
      "Exactly six exist now",
      "Fewer than six exist now",
      "More than six exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "messages",
    "semantic_frame": "stock-07-count",
    "source_item_id": "rc-messages-stock-07-count",
    "scope": "global"
  },
  {
    "id": "rc-messages-stock-08-count-dxalloc-0",
    "english": "Messaging note.\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.\nAt most 4 messages in each day; capacity returns as the day passes; the window slides, so any span of one day counts. At most 6 queued messages in mailbox M may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the span from two days ago to one day ago, this sender sent four messages; none since.\nSix queued messages in mailbox M exist now and none is scheduled to leave.",
    "ainglish": "Messaging note.\nmessages rate-cap(4; day). per-any(day). messages stock-cap(6; queued messages in mailbox M).\nCounts below are as of now, before any further action.\nIn the span from two days ago to one day ago, this sender sent four messages; none since.\nSix queued messages in mailbox M exist now and none is scheduled to leave.",
    "question": "How much room is there now for one additional message under both constraints together?",
    "options": [
      "Room for one more",
      "Room for the full allowance of six",
      "No room for another",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "messages",
    "semantic_frame": "stock-08-count",
    "source_item_id": "rc-messages-stock-08-count",
    "scope": "global"
  },
  {
    "id": "rc-permits-rate-01-wait-dxalloc-1",
    "english": "Parking office note. Budget shared by every actor on this service.\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.\nAt most 10 permits in each week; capacity returns as the week passes; whether the week is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding week, this permit holder issued ten permits.\nNo other actor issues a permit during the coming week.\nThis permit holder holds an authorisation to issue a permit that runs until the end of today.",
    "ainglish": "Parking office note. Budget shared by every actor on this service.\npermits rate-cap(10; week).\nCounts below are as of now, before any further action.\nIn the preceding week, this permit holder issued ten permits.\nNo other actor issues a permit during the coming week.\nThis permit holder holds an authorisation to issue a permit that runs until the end of today.",
    "question": "If this permit holder waits one full week from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for two more",
      "Room for one more",
      "Room for the full allowance of ten",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of ten",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "permits",
    "semantic_frame": "rate-01-wait",
    "source_item_id": "rc-permits-rate-01-wait",
    "scope": "global"
  },
  {
    "id": "rc-permits-rate-02-wait-dxalloc-0",
    "english": "Parking office note. Budget shared by every actor on this service.\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.\nAt most 10 permits in each week; capacity returns as the week passes; the count restarts at each clock week boundary.\nCounts below are as of now, before any further action.\nIn the current clock week, this permit holder issued ten permits.\nNo other actor issues a permit during the coming week.",
    "ainglish": "Parking office note. Budget shared by every actor on this service.\npermits rate-cap(10; week). per-clock(week).\nCounts below are as of now, before any further action.\nIn the current clock week, this permit holder issued ten permits.\nNo other actor issues a permit during the coming week.",
    "question": "If this permit holder waits one full week from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for two more",
      "Room for the full allowance of ten",
      "Room for one more",
      "Room for nine more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of ten",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "permits",
    "semantic_frame": "rate-02-wait",
    "source_item_id": "rc-permits-rate-02-wait",
    "scope": "global"
  },
  {
    "id": "rc-permits-rate-03-release-dxalloc-9",
    "english": "Parking office note. Budget shared by every actor on this service.\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.\nAt most 10 permits in each week; capacity returns as the week passes; the window slides, so any span of one week counts.\nCounts below are as of now, before any further action.\nIn the preceding week, this permit holder issued eight permits, aged 28 hours, 42 hours, 56 hours, 70 hours, 84 hours, 98 hours, 112 hours and 126 hours.\nNo other actor issued any permits in the preceding week.\nJust now, this permit holder closed one of those permits; nothing else changed.",
    "ainglish": "Parking office note. Budget shared by every actor on this service.\npermits rate-cap(10; week). per-any(week).\nCounts below are as of now, before any further action.\nIn the preceding week, this permit holder issued eight permits, aged 28 hours, 42 hours, 56 hours, 70 hours, 84 hours, 98 hours, 112 hours and 126 hours.\nNo other actor issued any permits in the preceding week.\nJust now, this permit holder closed one of those permits; nothing else changed.",
    "question": "How much room is there under this cap now, immediately after that closure?",
    "options": [
      "Room for nine more",
      "Room for two more",
      "Room for three more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "rate",
    "probe": "release",
    "domain": "permits",
    "semantic_frame": "rate-03-release",
    "source_item_id": "rc-permits-rate-03-release",
    "scope": "global"
  },
  {
    "id": "rc-permits-rate-04-delete-dxalloc-0",
    "english": "Parking office note. Budget shared by every actor on this service.\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.\nAt most 10 permits in each week; capacity returns as the week passes; whether the week is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding week, this permit holder issued two permits, aged 16 hours and 28 hours.\nNo other actor issued any permits in the preceding week.\nToday is Wednesday.\nJust now, this permit holder deleted an older permit that it issued last month; nothing else changed.\nThis permit holder's authorisation to issue a permit was revoked this morning and has not been restored.",
    "ainglish": "Parking office note. Budget shared by every actor on this service.\npermits rate-cap(10; week).\nCounts below are as of now, before any further action.\nIn the preceding week, this permit holder issued two permits, aged 16 hours and 28 hours.\nNo other actor issued any permits in the preceding week.\nToday is Wednesday.\nJust now, this permit holder deleted an older permit that it issued last month; nothing else changed.\nThis permit holder's authorisation to issue a permit was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap now, immediately after that deletion?",
    "options": [
      "Room for one more",
      "Room for eight more",
      "Room for the full allowance of ten",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for eight more",
    "settlement_stratum": "rate",
    "probe": "delete",
    "domain": "permits",
    "semantic_frame": "rate-04-delete",
    "source_item_id": "rc-permits-rate-04-delete",
    "scope": "global"
  },
  {
    "id": "rc-permits-rate-05-count-dxalloc-0",
    "english": "Parking office note. Budget shared by every actor on this service.\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.\nAt most 10 permits in each week; capacity returns as the week passes; the window slides, so any span of one week counts.\nCounts below are as of now, before any further action.\nThis permit holder issued four permits: two of them 16 hours and 33 hours ago, and two of them 252 hours and 336 hours ago.\nAnother permit holder issued three permits in the preceding week.\nNo actor other than this permit holder and another permit holder issued any permits in the preceding week.",
    "ainglish": "Parking office note. Budget shared by every actor on this service.\npermits rate-cap(10; week). per-any(week).\nCounts below are as of now, before any further action.\nThis permit holder issued four permits: two of them 16 hours and 33 hours ago, and two of them 252 hours and 336 hours ago.\nAnother permit holder issued three permits in the preceding week.\nNo actor other than this permit holder and another permit holder issued any permits in the preceding week.",
    "question": "How much room is there under this cap for this permit holder now?",
    "options": [
      "Room for three more",
      "Room for two more",
      "Room for five more",
      "Room for nine more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for five more",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "permits",
    "semantic_frame": "rate-05-count",
    "source_item_id": "rc-permits-rate-05-count",
    "scope": "global"
  },
  {
    "id": "rc-permits-rate-06-count-dxalloc-1",
    "english": "Parking office note. Budget shared by every actor on this service.\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.\nAt most 10 permits in each week; capacity returns as the week passes; whether the week is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of permits is given.",
    "ainglish": "Parking office note. Budget shared by every actor on this service.\npermits rate-cap(10; week).\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of permits is given.",
    "question": "How many permits exist now?",
    "options": [
      "Exactly ten exist now",
      "Fewer than ten exist now",
      "More than ten exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "permits",
    "semantic_frame": "rate-06-count",
    "source_item_id": "rc-permits-rate-06-count",
    "scope": "global"
  },
  {
    "id": "rc-permits-rate-07-boundary-dxalloc-2",
    "english": "Parking office note. Budget shared by every actor on this service.\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.\nAt most 10 permits in each week; capacity returns as the week passes; whether the week is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nThe week boundary falls at the start of Monday. This permit holder plans ten permits just before the boundary and ten more just after it, with nothing else issued in the surrounding span.",
    "ainglish": "Parking office note. Budget shared by every actor on this service.\npermits rate-cap(10; week).\nCounts below are as of now, before any further action.\nThe week boundary falls at the start of Monday. This permit holder plans ten permits just before the boundary and ten more just after it, with nothing else issued in the surrounding span.",
    "question": "Can both planned bursts be legal under this cap?",
    "options": [
      "Yes, both bursts can be legal",
      "No, at most one of the two bursts can be legal",
      "Only the burst before the boundary can be legal",
      "Only the burst after the boundary can be legal",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "rate",
    "probe": "boundary",
    "domain": "permits",
    "semantic_frame": "rate-07-boundary",
    "source_item_id": "rc-permits-rate-07-boundary",
    "scope": "global"
  },
  {
    "id": "rc-permits-rate-08-count-dxalloc-2",
    "english": "Parking office note. Budget shared by every actor on this service.\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.\nAt most 10 permits in each week; capacity returns as the week passes; the window slides, so any span of one week counts. At most 5 vehicles parked in bay set B may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the preceding week, this permit holder issued ten permits, aged 28 hours, 36 hours, 44 hours, 52 hours, 60 hours, 68 hours, 76 hours, 84 hours, 92 hours and 100 hours.\nNo other actor issued any permits in the preceding week.\nThree vehicles parked in bay set B exist now.",
    "ainglish": "Parking office note. Budget shared by every actor on this service.\npermits rate-cap(10; week). per-any(week). vehicles stock-cap(5; vehicles parked in bay set B).\nCounts below are as of now, before any further action.\nIn the preceding week, this permit holder issued ten permits, aged 28 hours, 36 hours, 44 hours, 52 hours, 60 hours, 68 hours, 76 hours, 84 hours, 92 hours and 100 hours.\nNo other actor issued any permits in the preceding week.\nThree vehicles parked in bay set B exist now.",
    "question": "How much room is there now for one additional permit under both constraints together?",
    "options": [
      "Room for two more",
      "Room for the full allowance of ten",
      "Room for nine more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "permits",
    "semantic_frame": "rate-08-count",
    "source_item_id": "rc-permits-rate-08-count",
    "scope": "global"
  },
  {
    "id": "rc-permits-stock-01-wait-dxalloc-4",
    "english": "Parking office note.\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.\nAt most 4 vehicles parked in bay set B may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nFour vehicles parked in bay set B exist now.\nThis permit holder waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "ainglish": "Parking office note.\nvehicles stock-cap(4; vehicles parked in bay set B).\nCounts below are as of now, before any further action.\nFour vehicles parked in bay set B exist now.\nThis permit holder waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for one more",
      "No room for another",
      "Room for two more",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "permits",
    "semantic_frame": "stock-01-wait",
    "source_item_id": "rc-permits-stock-01-wait",
    "scope": "global"
  },
  {
    "id": "rc-permits-stock-02-wait-dxalloc-9",
    "english": "Parking office note.\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.\nAt most 4 vehicles parked in bay set B may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nFour vehicles parked in bay set B exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. This permit holder waits twenty minutes and does nothing else; nothing else changes.",
    "ainglish": "Parking office note.\nvehicles stock-cap(4; vehicles parked in bay set B).\nCounts below are as of now, before any further action.\nFour vehicles parked in bay set B exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. This permit holder waits twenty minutes and does nothing else; nothing else changes.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for one more",
      "No room for another",
      "Room for two more",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "permits",
    "semantic_frame": "stock-02-wait",
    "source_item_id": "rc-permits-stock-02-wait",
    "scope": "global"
  },
  {
    "id": "rc-permits-stock-03-release-dxalloc-5",
    "english": "Parking office note.\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.\nAt most 4 vehicles parked in bay set B may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three vehicles parked in bay set B existed.\nBetween T0 and T1, this permit holder released one of them; nothing else changed.\nThis permit holder holds an authorisation to park a vehicle that runs until the end of today.",
    "ainglish": "Parking office note.\nvehicles stock-cap(4; vehicles parked in bay set B).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, three vehicles parked in bay set B existed.\nBetween T0 and T1, this permit holder released one of them; nothing else changed.\nThis permit holder holds an authorisation to park a vehicle that runs until the end of today.",
    "question": "How much room is there under this cap at T1, immediately after that release?",
    "options": [
      "No room for another",
      "Room for two more",
      "Room for one more",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "stock",
    "probe": "release",
    "domain": "permits",
    "semantic_frame": "stock-03-release",
    "source_item_id": "rc-permits-stock-03-release",
    "scope": "global"
  },
  {
    "id": "rc-permits-stock-04-delete-dxalloc-0",
    "english": "Parking office note.\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.\nAt most 4 vehicles parked in bay set B may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four vehicles parked in bay set B existed, and six archived vehicles existed that were not in the named set.\nBetween T0 and T1, this permit holder deleted one of the vehicles parked in bay set B; nothing else changed.",
    "ainglish": "Parking office note.\nvehicles stock-cap(4; vehicles parked in bay set B).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four vehicles parked in bay set B existed, and six archived vehicles existed that were not in the named set.\nBetween T0 and T1, this permit holder deleted one of the vehicles parked in bay set B; nothing else changed.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "No room for another",
      "Room for the full allowance of four",
      "Room for two more",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "permits",
    "semantic_frame": "stock-04-delete",
    "source_item_id": "rc-permits-stock-04-delete",
    "scope": "global"
  },
  {
    "id": "rc-permits-stock-05-delete-dxalloc-0",
    "english": "Parking office note.\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.\nAt most 4 vehicles parked in bay set B may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four vehicles parked in bay set B existed, and six archived vehicles existed that were not in the named set.\nBetween T0 and T1, this permit holder deleted one of the archived vehicles; no member of the named set changed.\nThis permit holder's authorisation to park a vehicle was revoked this morning and has not been restored.",
    "ainglish": "Parking office note.\nvehicles stock-cap(4; vehicles parked in bay set B).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four vehicles parked in bay set B existed, and six archived vehicles existed that were not in the named set.\nBetween T0 and T1, this permit holder deleted one of the archived vehicles; no member of the named set changed.\nThis permit holder's authorisation to park a vehicle was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for the full allowance of four",
      "Room for two more",
      "Room for one more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "permits",
    "semantic_frame": "stock-05-delete",
    "source_item_id": "rc-permits-stock-05-delete",
    "scope": "global"
  },
  {
    "id": "rc-permits-stock-06-count-dxalloc-1",
    "english": "Parking office note.\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.\nAt most 4 vehicles parked in bay set B may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nThis permit holder has one vehicle in the named set now; another permit holder has two vehicles in the same named set; no other owner has any vehicle in that set. No membership changes.",
    "ainglish": "Parking office note.\nvehicles stock-cap(4; vehicles parked in bay set B).\nCounts below are as of now, before any further action.\nThis permit holder has one vehicle in the named set now; another permit holder has two vehicles in the same named set; no other owner has any vehicle in that set. No membership changes.",
    "question": "How much room is there under this cap for this permit holder now?",
    "options": [
      "Room for two more",
      "Room for one more",
      "No room for another",
      "Room for the full allowance of four",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "permits",
    "semantic_frame": "stock-06-count",
    "source_item_id": "rc-permits-stock-06-count",
    "scope": "global"
  },
  {
    "id": "rc-permits-stock-07-count-dxalloc-0",
    "english": "Parking office note.\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.\nAt most 4 vehicles parked in bay set B may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of vehicles parked in bay set B is not given.",
    "ainglish": "Parking office note.\nvehicles stock-cap(4; vehicles parked in bay set B).\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of vehicles parked in bay set B is not given.",
    "question": "Exactly how many vehicles parked in bay set B exist now?",
    "options": [
      "Exactly four exist now",
      "Fewer than four exist now",
      "More than four exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "permits",
    "semantic_frame": "stock-07-count",
    "source_item_id": "rc-permits-stock-07-count",
    "scope": "global"
  },
  {
    "id": "rc-permits-stock-08-count-dxalloc-0",
    "english": "Parking office note.\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.\nAt most 4 permits in each week; capacity returns as the week passes; the window slides, so any span of one week counts. At most 4 vehicles parked in bay set B may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the span from two weeks ago to one week ago, this permit holder issued four permits; none since.\nFour vehicles parked in bay set B exist now and none is scheduled to leave.",
    "ainglish": "Parking office note.\npermits rate-cap(4; week). per-any(week). vehicles stock-cap(4; vehicles parked in bay set B).\nCounts below are as of now, before any further action.\nIn the span from two weeks ago to one week ago, this permit holder issued four permits; none since.\nFour vehicles parked in bay set B exist now and none is scheduled to leave.",
    "question": "How much room is there now for one additional vehicle under both constraints together?",
    "options": [
      "Room for the full allowance of four",
      "Room for two more",
      "Room for one more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "permits",
    "semantic_frame": "stock-08-count",
    "source_item_id": "rc-permits-stock-08-count",
    "scope": "global"
  },
  {
    "id": "rc-retries-rate-01-wait-dxalloc-0",
    "english": "Retry policy note. Budget for job J only.\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.\nAt most 5 retries in each hour; capacity returns as the hour passes; whether the hour is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding hour, job J scheduled five retries.\nJob J holds an authorisation to schedule a retry that runs until the end of today.",
    "ainglish": "Retry policy note. Budget for job J only.\nretries rate-cap(5; hour).\nCounts below are as of now, before any further action.\nIn the preceding hour, job J scheduled five retries.\nJob J holds an authorisation to schedule a retry that runs until the end of today.",
    "question": "If job J waits one full hour from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for the full allowance of five",
      "Room for one more",
      "Room for four more",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of five",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "retries",
    "semantic_frame": "rate-01-wait",
    "source_item_id": "rc-retries-rate-01-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-rate-02-wait-dxalloc-2",
    "english": "Retry policy note. Budget for job J only.\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.\nAt most 5 retries in each hour; capacity returns as the hour passes; the count restarts at each clock hour boundary.\nCounts below are as of now, before any further action.\nIn the current clock hour, job J scheduled five retries.",
    "ainglish": "Retry policy note. Budget for job J only.\nretries rate-cap(5; hour). per-clock(hour).\nCounts below are as of now, before any further action.\nIn the current clock hour, job J scheduled five retries.",
    "question": "If job J waits one full hour from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for the full allowance of five",
      "Room for four more",
      "Room for two more",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of five",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "retries",
    "semantic_frame": "rate-02-wait",
    "source_item_id": "rc-retries-rate-02-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-rate-03-release-dxalloc-3",
    "english": "Retry policy note. Budget for job J only.\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.\nAt most 5 retries in each hour; capacity returns as the hour passes; the window slides, so any span of one hour counts.\nCounts below are as of now, before any further action.\nIn the preceding hour, job J scheduled three retries, aged 10 minutes, 15 minutes and 20 minutes.\nJust now, job J closed one of those retries; nothing else changed.",
    "ainglish": "Retry policy note. Budget for job J only.\nretries rate-cap(5; hour). per-any(hour).\nCounts below are as of now, before any further action.\nIn the preceding hour, job J scheduled three retries, aged 10 minutes, 15 minutes and 20 minutes.\nJust now, job J closed one of those retries; nothing else changed.",
    "question": "How much room is there under this cap now, immediately after that closure?",
    "options": [
      "No room for another",
      "Room for the full allowance of five",
      "Room for one more",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "rate",
    "probe": "release",
    "domain": "retries",
    "semantic_frame": "rate-03-release",
    "source_item_id": "rc-retries-rate-03-release",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-rate-04-delete-dxalloc-0",
    "english": "Retry policy note. Budget for job J only.\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.\nAt most 5 retries in each hour; capacity returns as the hour passes; whether the hour is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding hour, job J scheduled two retries, aged 6 minutes and 10 minutes.\nThe current time is 10:40.\nJust now, job J deleted an older retry that it scheduled last week; nothing else changed.\nJob J's authorisation to schedule a retry was revoked this morning and has not been restored.",
    "ainglish": "Retry policy note. Budget for job J only.\nretries rate-cap(5; hour).\nCounts below are as of now, before any further action.\nIn the preceding hour, job J scheduled two retries, aged 6 minutes and 10 minutes.\nThe current time is 10:40.\nJust now, job J deleted an older retry that it scheduled last week; nothing else changed.\nJob J's authorisation to schedule a retry was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap now, immediately after that deletion?",
    "options": [
      "Room for three more",
      "Room for one more",
      "No room for another",
      "Room for the full allowance of five",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for three more",
    "settlement_stratum": "rate",
    "probe": "delete",
    "domain": "retries",
    "semantic_frame": "rate-04-delete",
    "source_item_id": "rc-retries-rate-04-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-rate-05-count-dxalloc-3",
    "english": "Retry policy note. Budget for job J only.\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.\nAt most 5 retries in each hour; capacity returns as the hour passes; the window slides, so any span of one hour counts.\nCounts below are as of now, before any further action.\nJob J scheduled four retries: two of them 6 minutes and 12 minutes ago, and two of them 90 minutes and 120 minutes ago.\nJob K scheduled three retries in the preceding hour.",
    "ainglish": "Retry policy note. Budget for job J only.\nretries rate-cap(5; hour). per-any(hour).\nCounts below are as of now, before any further action.\nJob J scheduled four retries: two of them 6 minutes and 12 minutes ago, and two of them 90 minutes and 120 minutes ago.\nJob K scheduled three retries in the preceding hour.",
    "question": "How much room is there under this cap for job J now?",
    "options": [
      "Room for the full allowance of five",
      "Room for one more",
      "Room for three more",
      "Room for four more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for three more",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "retries",
    "semantic_frame": "rate-05-count",
    "source_item_id": "rc-retries-rate-05-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-rate-06-count-dxalloc-0",
    "english": "Retry policy note. Budget for job J only.\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.\nAt most 5 retries in each hour; capacity returns as the hour passes; whether the hour is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of retries is given.",
    "ainglish": "Retry policy note. Budget for job J only.\nretries rate-cap(5; hour).\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of retries is given.",
    "question": "How many retries exist now?",
    "options": [
      "Exactly five exist now",
      "Fewer than five exist now",
      "More than five exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "retries",
    "semantic_frame": "rate-06-count",
    "source_item_id": "rc-retries-rate-06-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-rate-07-boundary-dxalloc-0",
    "english": "Retry policy note. Budget for job J only.\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.\nAt most 5 retries in each hour; capacity returns as the hour passes; the count restarts at each clock hour boundary.\nCounts below are as of now, before any further action.\nThe hour boundary falls at the top of the hour. Job J plans five retries just before the boundary and five more just after it, with nothing else scheduled in the surrounding span.",
    "ainglish": "Retry policy note. Budget for job J only.\nretries rate-cap(5; hour). per-clock(hour).\nCounts below are as of now, before any further action.\nThe hour boundary falls at the top of the hour. Job J plans five retries just before the boundary and five more just after it, with nothing else scheduled in the surrounding span.",
    "question": "Can both planned bursts be legal under this cap?",
    "options": [
      "Yes, both bursts can be legal",
      "No, at most one of the two bursts can be legal",
      "Only the burst before the boundary can be legal",
      "Only the burst after the boundary can be legal",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Yes, both bursts can be legal",
    "settlement_stratum": "rate",
    "probe": "boundary",
    "domain": "retries",
    "semantic_frame": "rate-07-boundary",
    "source_item_id": "rc-retries-rate-07-boundary",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-rate-08-count-dxalloc-0",
    "english": "Retry policy note. Budget for job J only.\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.\nAt most 5 retries in each hour; capacity returns as the hour passes; the window slides, so any span of one hour counts. At most 5 pending retries for job J may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the preceding hour, job J scheduled five retries, aged 10 minutes, 13 minutes, 16 minutes, 19 minutes and 22 minutes.\nThree pending retries for job J exist now.",
    "ainglish": "Retry policy note. Budget for job J only.\nretries rate-cap(5; hour). per-any(hour). retries stock-cap(5; pending retries for job J).\nCounts below are as of now, before any further action.\nIn the preceding hour, job J scheduled five retries, aged 10 minutes, 13 minutes, 16 minutes, 19 minutes and 22 minutes.\nThree pending retries for job J exist now.",
    "question": "How much room is there now for one additional retry under both constraints together?",
    "options": [
      "Room for the full allowance of five",
      "Room for four more",
      "Room for three more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "retries",
    "semantic_frame": "rate-08-count",
    "source_item_id": "rc-retries-rate-08-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-stock-01-wait-dxalloc-4",
    "english": "Retry policy note.\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.\nAt most 5 pending retries for job J may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nFive pending retries for job J exist now.\nJob J waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "ainglish": "Retry policy note.\nretries stock-cap(5; pending retries for job J).\nCounts below are as of now, before any further action.\nFive pending retries for job J exist now.\nJob J waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for one more",
      "Room for four more",
      "Room for three more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "retries",
    "semantic_frame": "stock-01-wait",
    "source_item_id": "rc-retries-stock-01-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-stock-02-wait-dxalloc-0",
    "english": "Retry policy note.\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.\nAt most 5 pending retries for job J may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nFive pending retries for job J exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. Job J waits twenty minutes and does nothing else; nothing else changes.",
    "ainglish": "Retry policy note.\nretries stock-cap(5; pending retries for job J).\nCounts below are as of now, before any further action.\nFive pending retries for job J exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. Job J waits twenty minutes and does nothing else; nothing else changes.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for four more",
      "Room for two more",
      "Room for three more",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "retries",
    "semantic_frame": "stock-02-wait",
    "source_item_id": "rc-retries-stock-02-wait",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-stock-03-release-dxalloc-3",
    "english": "Retry policy note.\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.\nAt most 5 pending retries for job J may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four pending retries for job J existed.\nBetween T0 and T1, job J released one of them; nothing else changed.\nJob J holds an authorisation to schedule a retry that runs until the end of today.",
    "ainglish": "Retry policy note.\nretries stock-cap(5; pending retries for job J).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, four pending retries for job J existed.\nBetween T0 and T1, job J released one of them; nothing else changed.\nJob J holds an authorisation to schedule a retry that runs until the end of today.",
    "question": "How much room is there under this cap at T1, immediately after that release?",
    "options": [
      "Room for four more",
      "Room for one more",
      "Room for two more",
      "Room for the full allowance of five",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "stock",
    "probe": "release",
    "domain": "retries",
    "semantic_frame": "stock-03-release",
    "source_item_id": "rc-retries-stock-03-release",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-stock-04-delete-dxalloc-8",
    "english": "Retry policy note.\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.\nAt most 5 pending retries for job J may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, five pending retries for job J existed, and six archived retries existed that were not in the named set.\nBetween T0 and T1, job J deleted one of the pending retries for job J; nothing else changed.",
    "ainglish": "Retry policy note.\nretries stock-cap(5; pending retries for job J).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, five pending retries for job J existed, and six archived retries existed that were not in the named set.\nBetween T0 and T1, job J deleted one of the pending retries for job J; nothing else changed.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for four more",
      "Room for two more",
      "Room for one more",
      "Room for the full allowance of five",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "retries",
    "semantic_frame": "stock-04-delete",
    "source_item_id": "rc-retries-stock-04-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-stock-05-delete-dxalloc-0",
    "english": "Retry policy note.\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.\nAt most 5 pending retries for job J may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, five pending retries for job J existed, and six archived retries existed that were not in the named set.\nBetween T0 and T1, job J deleted one of the archived retries; no member of the named set changed.\nJob J's authorisation to schedule a retry was revoked this morning and has not been restored.",
    "ainglish": "Retry policy note.\nretries stock-cap(5; pending retries for job J).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, five pending retries for job J existed, and six archived retries existed that were not in the named set.\nBetween T0 and T1, job J deleted one of the archived retries; no member of the named set changed.\nJob J's authorisation to schedule a retry was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for the full allowance of five",
      "No room for another",
      "Room for three more",
      "Room for four more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "retries",
    "semantic_frame": "stock-05-delete",
    "source_item_id": "rc-retries-stock-05-delete",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-stock-06-count-dxalloc-2",
    "english": "Retry policy note.\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.\nAt most 5 pending retries for job J may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nJob J has one retry in the named set now; job K has two retries of the same kind, which belong to job K and not to job J. No membership changes.",
    "ainglish": "Retry policy note.\nretries stock-cap(5; pending retries for job J).\nCounts below are as of now, before any further action.\nJob J has one retry in the named set now; job K has two retries of the same kind, which belong to job K and not to job J. No membership changes.",
    "question": "How much room is there under this cap for job J now?",
    "options": [
      "Room for four more",
      "Room for the full allowance of five",
      "No room for another",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for four more",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "retries",
    "semantic_frame": "stock-06-count",
    "source_item_id": "rc-retries-stock-06-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-stock-07-count-dxalloc-0",
    "english": "Retry policy note.\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.\nAt most 5 pending retries for job J may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of pending retries for job J is not given.",
    "ainglish": "Retry policy note.\nretries stock-cap(5; pending retries for job J).\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of pending retries for job J is not given.",
    "question": "Exactly how many pending retries for job J exist now?",
    "options": [
      "Exactly five exist now",
      "Fewer than five exist now",
      "More than five exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "retries",
    "semantic_frame": "stock-07-count",
    "source_item_id": "rc-retries-stock-07-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-retries-stock-08-count-dxalloc-0",
    "english": "Retry policy note.\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.\nAt most 4 retries in each hour; capacity returns as the hour passes; the window slides, so any span of one hour counts. At most 5 pending retries for job J may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the span from two hours ago to one hour ago, job J scheduled four retries; none since.\nFive pending retries for job J exist now and none is scheduled to leave.",
    "ainglish": "Retry policy note.\nretries rate-cap(4; hour). per-any(hour). retries stock-cap(5; pending retries for job J).\nCounts below are as of now, before any further action.\nIn the span from two hours ago to one hour ago, job J scheduled four retries; none since.\nFive pending retries for job J exist now and none is scheduled to leave.",
    "question": "How much room is there now for one additional retry under both constraints together?",
    "options": [
      "Room for four more",
      "Room for the full allowance of five",
      "No room for another",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "retries",
    "semantic_frame": "stock-08-count",
    "source_item_id": "rc-retries-stock-08-count",
    "scope": "per-identity"
  },
  {
    "id": "rc-memory-rate-01-wait-dxalloc-4",
    "english": "Memory reservation note. Budget shared by every actor on this service.\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.\nAt most 6 reservations in each minute; capacity returns as the minute passes; whether the minute is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding minute, service S took six reservations.\nNo other actor takes a reservation during the coming minute.\nService S holds an authorisation to take a reservation that runs until the end of today.",
    "ainglish": "Memory reservation note. Budget shared by every actor on this service.\nreservations rate-cap(6; minute).\nCounts below are as of now, before any further action.\nIn the preceding minute, service S took six reservations.\nNo other actor takes a reservation during the coming minute.\nService S holds an authorisation to take a reservation that runs until the end of today.",
    "question": "If service S waits one full minute from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for the full allowance of six",
      "Room for one more",
      "Room for five more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of six",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "memory",
    "semantic_frame": "rate-01-wait",
    "source_item_id": "rc-memory-rate-01-wait",
    "scope": "global"
  },
  {
    "id": "rc-memory-rate-02-wait-dxalloc-2",
    "english": "Memory reservation note. Budget shared by every actor on this service.\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.\nAt most 6 reservations in each minute; capacity returns as the minute passes; the count restarts at each clock minute boundary.\nCounts below are as of now, before any further action.\nIn the current clock minute, service S took six reservations.\nNo other actor takes a reservation during the coming minute.",
    "ainglish": "Memory reservation note. Budget shared by every actor on this service.\nreservations rate-cap(6; minute). per-clock(minute).\nCounts below are as of now, before any further action.\nIn the current clock minute, service S took six reservations.\nNo other actor takes a reservation during the coming minute.",
    "question": "If service S waits one full minute from now and does nothing else, how much room is there under this cap then?",
    "options": [
      "Room for three more",
      "Room for the full allowance of six",
      "No room for another",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for the full allowance of six",
    "settlement_stratum": "rate",
    "probe": "wait",
    "domain": "memory",
    "semantic_frame": "rate-02-wait",
    "source_item_id": "rc-memory-rate-02-wait",
    "scope": "global"
  },
  {
    "id": "rc-memory-rate-03-release-dxalloc-3",
    "english": "Memory reservation note. Budget shared by every actor on this service.\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.\nAt most 6 reservations in each minute; capacity returns as the minute passes; the window slides, so any span of one minute counts.\nCounts below are as of now, before any further action.\nIn the preceding minute, service S took four reservations, aged 10 seconds, 15 seconds, 20 seconds and 25 seconds.\nNo other actor took any reservations in the preceding minute.\nJust now, service S closed one of those reservations; nothing else changed.",
    "ainglish": "Memory reservation note. Budget shared by every actor on this service.\nreservations rate-cap(6; minute). per-any(minute).\nCounts below are as of now, before any further action.\nIn the preceding minute, service S took four reservations, aged 10 seconds, 15 seconds, 20 seconds and 25 seconds.\nNo other actor took any reservations in the preceding minute.\nJust now, service S closed one of those reservations; nothing else changed.",
    "question": "How much room is there under this cap now, immediately after that closure?",
    "options": [
      "Room for the full allowance of six",
      "Room for three more",
      "Room for five more",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "rate",
    "probe": "release",
    "domain": "memory",
    "semantic_frame": "rate-03-release",
    "source_item_id": "rc-memory-rate-03-release",
    "scope": "global"
  },
  {
    "id": "rc-memory-rate-04-delete-dxalloc-2",
    "english": "Memory reservation note. Budget shared by every actor on this service.\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.\nAt most 6 reservations in each minute; capacity returns as the minute passes; whether the minute is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nIn the preceding minute, service S took two reservations, aged 6 seconds and 10 seconds.\nNo other actor took any reservations in the preceding minute.\nThe current time is 10:40:30.\nJust now, service S deleted an older reservation that it took last week; nothing else changed.\nService S's authorisation to take a reservation was revoked this morning and has not been restored.",
    "ainglish": "Memory reservation note. Budget shared by every actor on this service.\nreservations rate-cap(6; minute).\nCounts below are as of now, before any further action.\nIn the preceding minute, service S took two reservations, aged 6 seconds and 10 seconds.\nNo other actor took any reservations in the preceding minute.\nThe current time is 10:40:30.\nJust now, service S deleted an older reservation that it took last week; nothing else changed.\nService S's authorisation to take a reservation was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap now, immediately after that deletion?",
    "options": [
      "Room for four more",
      "Room for the full allowance of six",
      "Room for five more",
      "Room for one more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for four more",
    "settlement_stratum": "rate",
    "probe": "delete",
    "domain": "memory",
    "semantic_frame": "rate-04-delete",
    "source_item_id": "rc-memory-rate-04-delete",
    "scope": "global"
  },
  {
    "id": "rc-memory-rate-05-count-dxalloc-0",
    "english": "Memory reservation note. Budget shared by every actor on this service.\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.\nAt most 6 reservations in each minute; capacity returns as the minute passes; the window slides, so any span of one minute counts.\nCounts below are as of now, before any further action.\nService S took four reservations: two of them 6 seconds and 12 seconds ago, and two of them 90 seconds and 120 seconds ago.\nService U took three reservations in the preceding minute.\nNo actor other than service S and service U took any reservations in the preceding minute.",
    "ainglish": "Memory reservation note. Budget shared by every actor on this service.\nreservations rate-cap(6; minute). per-any(minute).\nCounts below are as of now, before any further action.\nService S took four reservations: two of them 6 seconds and 12 seconds ago, and two of them 90 seconds and 120 seconds ago.\nService U took three reservations in the preceding minute.\nNo actor other than service S and service U took any reservations in the preceding minute.",
    "question": "How much room is there under this cap for service S now?",
    "options": [
      "Room for one more",
      "Room for five more",
      "Room for three more",
      "Room for two more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "memory",
    "semantic_frame": "rate-05-count",
    "source_item_id": "rc-memory-rate-05-count",
    "scope": "global"
  },
  {
    "id": "rc-memory-rate-06-count-dxalloc-4",
    "english": "Memory reservation note. Budget shared by every actor on this service.\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.\nAt most 6 reservations in each minute; capacity returns as the minute passes; whether the minute is clock-aligned or sliding is not stated.\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of reservations is given.",
    "ainglish": "Memory reservation note. Budget shared by every actor on this service.\nreservations rate-cap(6; minute).\nCounts below are as of now, before any further action.\nOnly this cap is stated. No count of reservations is given.",
    "question": "How many reservations exist now?",
    "options": [
      "Exactly six exist now",
      "Fewer than six exist now",
      "More than six exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "memory",
    "semantic_frame": "rate-06-count",
    "source_item_id": "rc-memory-rate-06-count",
    "scope": "global"
  },
  {
    "id": "rc-memory-rate-07-boundary-dxalloc-6",
    "english": "Memory reservation note. Budget shared by every actor on this service.\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.\nAt most 6 reservations in each minute; capacity returns as the minute passes; the window slides, so any span of one minute counts.\nCounts below are as of now, before any further action.\nThe minute boundary falls at the top of the minute. Service S plans six reservations just before the boundary and six more just after it, with nothing else took in the surrounding span.",
    "ainglish": "Memory reservation note. Budget shared by every actor on this service.\nreservations rate-cap(6; minute). per-any(minute).\nCounts below are as of now, before any further action.\nThe minute boundary falls at the top of the minute. Service S plans six reservations just before the boundary and six more just after it, with nothing else took in the surrounding span.",
    "question": "Can both planned bursts be legal under this cap?",
    "options": [
      "Yes, both bursts can be legal",
      "No, at most one of the two bursts can be legal",
      "Only the burst before the boundary can be legal",
      "Only the burst after the boundary can be legal",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No, at most one of the two bursts can be legal",
    "settlement_stratum": "rate",
    "probe": "boundary",
    "domain": "memory",
    "semantic_frame": "rate-07-boundary",
    "source_item_id": "rc-memory-rate-07-boundary",
    "scope": "global"
  },
  {
    "id": "rc-memory-rate-08-count-dxalloc-2",
    "english": "Memory reservation note. Budget shared by every actor on this service.\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.\nAt most 6 reservations in each minute; capacity returns as the minute passes; the window slides, so any span of one minute counts. At most 5 held reservations in pool R may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the preceding minute, service S took six reservations, aged 10 seconds, 13 seconds, 16 seconds, 19 seconds, 22 seconds and 25 seconds.\nNo other actor took any reservations in the preceding minute.\nThree held reservations in pool R exist now.",
    "ainglish": "Memory reservation note. Budget shared by every actor on this service.\nreservations rate-cap(6; minute). per-any(minute). reservations stock-cap(5; held reservations in pool R).\nCounts below are as of now, before any further action.\nIn the preceding minute, service S took six reservations, aged 10 seconds, 13 seconds, 16 seconds, 19 seconds, 22 seconds and 25 seconds.\nNo other actor took any reservations in the preceding minute.\nThree held reservations in pool R exist now.",
    "question": "How much room is there now for one additional reservation under both constraints together?",
    "options": [
      "Room for the full allowance of six",
      "Room for one more",
      "Room for five more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "rate",
    "probe": "count",
    "domain": "memory",
    "semantic_frame": "rate-08-count",
    "source_item_id": "rc-memory-rate-08-count",
    "scope": "global"
  },
  {
    "id": "rc-memory-stock-01-wait-dxalloc-1",
    "english": "Memory reservation note.\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.\nAt most 8 held reservations in pool R may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nEight held reservations in pool R exist now.\nService S waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "ainglish": "Memory reservation note.\nreservations stock-cap(8; held reservations in pool R).\nCounts below are as of now, before any further action.\nEight held reservations in pool R exist now.\nService S waits twenty minutes and does nothing else; no membership of the named set changes in that time.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for one more",
      "No room for another",
      "Room for seven more",
      "Room for the full allowance of eight",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "memory",
    "semantic_frame": "stock-01-wait",
    "source_item_id": "rc-memory-stock-01-wait",
    "scope": "global"
  },
  {
    "id": "rc-memory-stock-02-wait-dxalloc-3",
    "english": "Memory reservation note.\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.\nAt most 8 held reservations in pool R may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nEight held reservations in pool R exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. Service S waits twenty minutes and does nothing else; nothing else changes.",
    "ainglish": "Memory reservation note.\nreservations stock-cap(8; held reservations in pool R).\nCounts below are as of now, before any further action.\nEight held reservations in pool R exist now.\nExactly one of them is scheduled to expire and leave the named set in twenty minutes. Service S waits twenty minutes and does nothing else; nothing else changes.",
    "question": "How much room is there under this cap after those twenty minutes?",
    "options": [
      "Room for seven more",
      "Room for two more",
      "Room for one more",
      "No room for another",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "wait",
    "domain": "memory",
    "semantic_frame": "stock-02-wait",
    "source_item_id": "rc-memory-stock-02-wait",
    "scope": "global"
  },
  {
    "id": "rc-memory-stock-03-release-dxalloc-0",
    "english": "Memory reservation note.\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.\nAt most 8 held reservations in pool R may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, seven held reservations in pool R existed.\nBetween T0 and T1, service S released one of them; nothing else changed.\nService S holds an authorisation to take a reservation that runs until the end of today.",
    "ainglish": "Memory reservation note.\nreservations stock-cap(8; held reservations in pool R).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, seven held reservations in pool R existed.\nBetween T0 and T1, service S released one of them; nothing else changed.\nService S holds an authorisation to take a reservation that runs until the end of today.",
    "question": "How much room is there under this cap at T1, immediately after that release?",
    "options": [
      "No room for another",
      "Room for two more",
      "Room for one more",
      "Room for seven more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for two more",
    "settlement_stratum": "stock",
    "probe": "release",
    "domain": "memory",
    "semantic_frame": "stock-03-release",
    "source_item_id": "rc-memory-stock-03-release",
    "scope": "global"
  },
  {
    "id": "rc-memory-stock-04-delete-dxalloc-7",
    "english": "Memory reservation note.\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.\nAt most 8 held reservations in pool R may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, eight held reservations in pool R existed, and six archived reservations existed that were not in the named set.\nBetween T0 and T1, service S deleted one of the held reservations in pool R; nothing else changed.",
    "ainglish": "Memory reservation note.\nreservations stock-cap(8; held reservations in pool R).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, eight held reservations in pool R existed, and six archived reservations existed that were not in the named set.\nBetween T0 and T1, service S deleted one of the held reservations in pool R; nothing else changed.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for seven more",
      "Room for two more",
      "Room for one more",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for one more",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "memory",
    "semantic_frame": "stock-04-delete",
    "source_item_id": "rc-memory-stock-04-delete",
    "scope": "global"
  },
  {
    "id": "rc-memory-stock-05-delete-dxalloc-3",
    "english": "Memory reservation note.\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.\nAt most 8 held reservations in pool R may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, eight held reservations in pool R existed, and six archived reservations existed that were not in the named set.\nBetween T0 and T1, service S deleted one of the archived reservations; no member of the named set changed.\nService S's authorisation to take a reservation was revoked this morning and has not been restored.",
    "ainglish": "Memory reservation note.\nreservations stock-cap(8; held reservations in pool R).\nCounts below are dated as stated: T0 is the instant immediately before the action, T1 the instant immediately after it.\nAt T0, eight held reservations in pool R existed, and six archived reservations existed that were not in the named set.\nBetween T0 and T1, service S deleted one of the archived reservations; no member of the named set changed.\nService S's authorisation to take a reservation was revoked this morning and has not been restored.",
    "question": "How much room is there under this cap at T1, immediately after that deletion?",
    "options": [
      "Room for two more",
      "Room for the full allowance of eight",
      "No room for another",
      "Room for seven more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "delete",
    "domain": "memory",
    "semantic_frame": "stock-05-delete",
    "source_item_id": "rc-memory-stock-05-delete",
    "scope": "global"
  },
  {
    "id": "rc-memory-stock-06-count-dxalloc-0",
    "english": "Memory reservation note.\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.\nAt most 8 held reservations in pool R may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nService S has one reservation in the named set now; service U has two reservations in the same named set; no other owner has any reservation in that set. No membership changes.",
    "ainglish": "Memory reservation note.\nreservations stock-cap(8; held reservations in pool R).\nCounts below are as of now, before any further action.\nService S has one reservation in the named set now; service U has two reservations in the same named set; no other owner has any reservation in that set. No membership changes.",
    "question": "How much room is there under this cap for service S now?",
    "options": [
      "Room for two more",
      "Room for three more",
      "Room for seven more",
      "Room for five more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Room for five more",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "memory",
    "semantic_frame": "stock-06-count",
    "source_item_id": "rc-memory-stock-06-count",
    "scope": "global"
  },
  {
    "id": "rc-memory-stock-07-count-dxalloc-3",
    "english": "Memory reservation note.\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.\nAt most 8 held reservations in pool R may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of held reservations in pool R is not given.",
    "ainglish": "Memory reservation note.\nreservations stock-cap(8; held reservations in pool R).\nCounts below are as of now, before any further action.\nOnly this cap is stated. The number of held reservations in pool R is not given.",
    "question": "Exactly how many held reservations in pool R exist now?",
    "options": [
      "Exactly eight exist now",
      "Fewer than eight exist now",
      "More than eight exist now",
      "None exist now",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "Cannot determine from the statement and the facts",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "memory",
    "semantic_frame": "stock-07-count",
    "source_item_id": "rc-memory-stock-07-count",
    "scope": "global"
  },
  {
    "id": "rc-memory-stock-08-count-dxalloc-1",
    "english": "Memory reservation note.\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.\nAt most 4 reservations in each minute; capacity returns as the minute passes; the window slides, so any span of one minute counts. At most 8 held reservations in pool R may exist at one time; room returns only when one of them leaves that set by closing, release, deletion, consumption or expiry, however long one waits.\nCounts below are as of now, before any further action.\nIn the span from two minutes ago to one minute ago, service S took four reservations; none since.\nEight held reservations in pool R exist now and none is scheduled to leave.",
    "ainglish": "Memory reservation note.\nreservations rate-cap(4; minute). per-any(minute). reservations stock-cap(8; held reservations in pool R).\nCounts below are as of now, before any further action.\nIn the span from two minutes ago to one minute ago, service S took four reservations; none since.\nEight held reservations in pool R exist now and none is scheduled to leave.",
    "question": "How much room is there now for one additional reservation under both constraints together?",
    "options": [
      "Room for seven more",
      "Room for two more",
      "No room for another",
      "Room for three more",
      "Cannot determine from the statement and the facts"
    ],
    "answer": "No room for another",
    "settlement_stratum": "stock",
    "probe": "count",
    "domain": "memory",
    "semantic_frame": "stock-08-count",
    "source_item_id": "rc-memory-stock-08-count",
    "scope": "global"
  },
  {
    "id": "rc-calibration-01",
    "calibration": true,
    "english": "Bay-record-430: either Clerk-Ochre-69 or Clerk-Rust-69 is the responsible clerk; this has not been settled. Either Bay-Moss-31 or Bay-Umber-31 is the destination bay; this also has not been settled.",
    "ainglish": "Bay-record-430: Clerk-Ochre-69, not Clerk-Rust-69, is the responsible clerk. Bay-Moss-31, not Bay-Umber-31, is the destination bay.",
    "question": "Which complete clerk/bay assignment is established by this record?",
    "options": [
      "Clerk-Rust-69 / Bay-Umber-31",
      "Clerk-Rust-69 / Bay-Moss-31",
      "The record contradicts itself.",
      "Clerk established; bay not established.",
      "Clerk not established; bay established.",
      "Clerk-Ochre-69 / Bay-Moss-31",
      "Clerk-Ochre-69 / Bay-Umber-31",
      "Neither is established."
    ],
    "answer": "Clerk-Ochre-69 / Bay-Moss-31",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-02",
    "calibration": true,
    "english": "Shelf-record-569: either Keeper-Moss-55 or Keeper-Teal-55 is the responsible keeper; this has not been settled. Either Shelf-Ochre-60 or Shelf-Sable-60 is the destination shelf; this also has not been settled.",
    "ainglish": "Shelf-record-569: Keeper-Moss-55, not Keeper-Teal-55, is the responsible keeper. Shelf-Ochre-60, not Shelf-Sable-60, is the destination shelf.",
    "question": "Which complete keeper/shelf assignment is established by this record?",
    "options": [
      "Neither is established.",
      "Keeper-Moss-55 / Shelf-Ochre-60",
      "Keeper-Moss-55 / Shelf-Sable-60",
      "Keeper established; shelf not established.",
      "The record contradicts itself.",
      "Keeper not established; shelf established.",
      "Keeper-Teal-55 / Shelf-Ochre-60",
      "Keeper-Teal-55 / Shelf-Sable-60"
    ],
    "answer": "Keeper-Moss-55 / Shelf-Ochre-60",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-03",
    "calibration": true,
    "english": "Shelf-record-939: either Warden-Moss-27 or Warden-Ochre-27 is the responsible warden; this has not been settled. Either Shelf-Rust-61 or Shelf-Umber-61 is the destination shelf; this also has not been settled.",
    "ainglish": "Shelf-record-939: Warden-Moss-27, not Warden-Ochre-27, is the responsible warden. Shelf-Rust-61, not Shelf-Umber-61, is the destination shelf.",
    "question": "Which complete warden/shelf assignment is established by this record?",
    "options": [
      "Warden established; shelf not established.",
      "Warden-Ochre-27 / Shelf-Umber-61",
      "Warden not established; shelf established.",
      "Neither is established.",
      "The record contradicts itself.",
      "Warden-Ochre-27 / Shelf-Rust-61",
      "Warden-Moss-27 / Shelf-Umber-61",
      "Warden-Moss-27 / Shelf-Rust-61"
    ],
    "answer": "Warden-Moss-27 / Shelf-Rust-61",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-04",
    "calibration": true,
    "english": "Shelf-record-153: either Clerk-Teal-47 or Clerk-Umber-47 is the responsible clerk; this has not been settled. Either Shelf-Moss-33 or Shelf-Rust-33 is the destination shelf; this also has not been settled.",
    "ainglish": "Shelf-record-153: Clerk-Teal-47, not Clerk-Umber-47, is the responsible clerk. Shelf-Moss-33, not Shelf-Rust-33, is the destination shelf.",
    "question": "Which complete clerk/shelf assignment is established by this record?",
    "options": [
      "Clerk-Umber-47 / Shelf-Rust-33",
      "The record contradicts itself.",
      "Neither is established.",
      "Clerk established; shelf not established.",
      "Clerk not established; shelf established.",
      "Clerk-Umber-47 / Shelf-Moss-33",
      "Clerk-Teal-47 / Shelf-Rust-33",
      "Clerk-Teal-47 / Shelf-Moss-33"
    ],
    "answer": "Clerk-Teal-47 / Shelf-Moss-33",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-05",
    "calibration": true,
    "english": "Dock-record-797: either Auditor-Sable-55 or Auditor-Moss-55 is the responsible auditor; this has not been settled. Either Dock-Umber-62 or Dock-Ivory-62 is the destination dock; this also has not been settled.",
    "ainglish": "Dock-record-797: Auditor-Sable-55, not Auditor-Moss-55, is the responsible auditor. Dock-Umber-62, not Dock-Ivory-62, is the destination dock.",
    "question": "Which complete auditor/dock assignment is established by this record?",
    "options": [
      "Auditor-Moss-55 / Dock-Umber-62",
      "Auditor not established; dock established.",
      "Auditor-Moss-55 / Dock-Ivory-62",
      "Neither is established.",
      "The record contradicts itself.",
      "Auditor-Sable-55 / Dock-Umber-62",
      "Auditor-Sable-55 / Dock-Ivory-62",
      "Auditor established; dock not established."
    ],
    "answer": "Auditor-Sable-55 / Dock-Umber-62",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-06",
    "calibration": true,
    "english": "Bay-record-758: either Clerk-Ochre-50 or Clerk-Plum-50 is the responsible clerk; this has not been settled. Either Bay-Ivory-68 or Bay-Rust-68 is the destination bay; this also has not been settled.",
    "ainglish": "Bay-record-758: Clerk-Ochre-50, not Clerk-Plum-50, is the responsible clerk. Bay-Ivory-68, not Bay-Rust-68, is the destination bay.",
    "question": "Which complete clerk/bay assignment is established by this record?",
    "options": [
      "Clerk-Plum-50 / Bay-Rust-68",
      "Clerk not established; bay established.",
      "The record contradicts itself.",
      "Clerk-Plum-50 / Bay-Ivory-68",
      "Clerk-Ochre-50 / Bay-Ivory-68",
      "Clerk established; bay not established.",
      "Neither is established.",
      "Clerk-Ochre-50 / Bay-Rust-68"
    ],
    "answer": "Clerk-Ochre-50 / Bay-Ivory-68",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-07",
    "calibration": true,
    "english": "Bay-record-869: either Steward-Rust-95 or Steward-Plum-95 is the responsible steward; this has not been settled. Either Bay-Umber-77 or Bay-Ochre-77 is the destination bay; this also has not been settled.",
    "ainglish": "Bay-record-869: Steward-Rust-95, not Steward-Plum-95, is the responsible steward. Bay-Umber-77, not Bay-Ochre-77, is the destination bay.",
    "question": "Which complete steward/bay assignment is established by this record?",
    "options": [
      "Steward-Plum-95 / Bay-Umber-77",
      "Neither is established.",
      "Steward-Rust-95 / Bay-Ochre-77",
      "Steward-Plum-95 / Bay-Ochre-77",
      "Steward established; bay not established.",
      "The record contradicts itself.",
      "Steward not established; bay established.",
      "Steward-Rust-95 / Bay-Umber-77"
    ],
    "answer": "Steward-Rust-95 / Bay-Umber-77",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-08",
    "calibration": true,
    "english": "Bay-record-628: either Marshal-Plum-14 or Marshal-Teal-14 is the responsible marshal; this has not been settled. Either Bay-Umber-66 or Bay-Sable-66 is the destination bay; this also has not been settled.",
    "ainglish": "Bay-record-628: Marshal-Plum-14, not Marshal-Teal-14, is the responsible marshal. Bay-Umber-66, not Bay-Sable-66, is the destination bay.",
    "question": "Which complete marshal/bay assignment is established by this record?",
    "options": [
      "Marshal-Plum-14 / Bay-Sable-66",
      "Marshal-Teal-14 / Bay-Umber-66",
      "The record contradicts itself.",
      "Marshal-Teal-14 / Bay-Sable-66",
      "Marshal-Plum-14 / Bay-Umber-66",
      "Neither is established.",
      "Marshal established; bay not established.",
      "Marshal not established; bay established."
    ],
    "answer": "Marshal-Plum-14 / Bay-Umber-66",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-09",
    "calibration": true,
    "english": "Vault-record-685: either Steward-Rust-11 or Steward-Teal-11 is the responsible steward; this has not been settled. Either Vault-Umber-41 or Vault-Ivory-41 is the destination vault; this also has not been settled.",
    "ainglish": "Vault-record-685: Steward-Rust-11, not Steward-Teal-11, is the responsible steward. Vault-Umber-41, not Vault-Ivory-41, is the destination vault.",
    "question": "Which complete steward/vault assignment is established by this record?",
    "options": [
      "Steward-Rust-11 / Vault-Umber-41",
      "Neither is established.",
      "Steward-Rust-11 / Vault-Ivory-41",
      "Steward not established; vault established.",
      "Steward established; vault not established.",
      "Steward-Teal-11 / Vault-Umber-41",
      "The record contradicts itself.",
      "Steward-Teal-11 / Vault-Ivory-41"
    ],
    "answer": "Steward-Rust-11 / Vault-Umber-41",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-10",
    "calibration": true,
    "english": "Vault-record-209: either Clerk-Moss-84 or Clerk-Teal-84 is the responsible clerk; this has not been settled. Either Vault-Plum-49 or Vault-Umber-49 is the destination vault; this also has not been settled.",
    "ainglish": "Vault-record-209: Clerk-Moss-84, not Clerk-Teal-84, is the responsible clerk. Vault-Plum-49, not Vault-Umber-49, is the destination vault.",
    "question": "Which complete clerk/vault assignment is established by this record?",
    "options": [
      "The record contradicts itself.",
      "Clerk not established; vault established.",
      "Clerk-Moss-84 / Vault-Plum-49",
      "Clerk-Teal-84 / Vault-Plum-49",
      "Clerk-Teal-84 / Vault-Umber-49",
      "Clerk established; vault not established.",
      "Neither is established.",
      "Clerk-Moss-84 / Vault-Umber-49"
    ],
    "answer": "Clerk-Moss-84 / Vault-Plum-49",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-11",
    "calibration": true,
    "english": "Dock-record-723: either Keeper-Ochre-21 or Keeper-Rust-21 is the responsible keeper; this has not been settled. Either Dock-Ivory-21 or Dock-Umber-21 is the destination dock; this also has not been settled.",
    "ainglish": "Dock-record-723: Keeper-Ochre-21, not Keeper-Rust-21, is the responsible keeper. Dock-Ivory-21, not Dock-Umber-21, is the destination dock.",
    "question": "Which complete keeper/dock assignment is established by this record?",
    "options": [
      "Neither is established.",
      "Keeper-Ochre-21 / Dock-Umber-21",
      "Keeper-Rust-21 / Dock-Umber-21",
      "Keeper not established; dock established.",
      "Keeper established; dock not established.",
      "Keeper-Rust-21 / Dock-Ivory-21",
      "The record contradicts itself.",
      "Keeper-Ochre-21 / Dock-Ivory-21"
    ],
    "answer": "Keeper-Ochre-21 / Dock-Ivory-21",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-12",
    "calibration": true,
    "english": "Dock-record-943: either Keeper-Moss-62 or Keeper-Rust-62 is the responsible keeper; this has not been settled. Either Dock-Plum-85 or Dock-Umber-85 is the destination dock; this also has not been settled.",
    "ainglish": "Dock-record-943: Keeper-Moss-62, not Keeper-Rust-62, is the responsible keeper. Dock-Plum-85, not Dock-Umber-85, is the destination dock.",
    "question": "Which complete keeper/dock assignment is established by this record?",
    "options": [
      "Keeper-Rust-62 / Dock-Umber-85",
      "Keeper established; dock not established.",
      "Keeper-Rust-62 / Dock-Plum-85",
      "Keeper-Moss-62 / Dock-Umber-85",
      "Keeper-Moss-62 / Dock-Plum-85",
      "The record contradicts itself.",
      "Neither is established.",
      "Keeper not established; dock established."
    ],
    "answer": "Keeper-Moss-62 / Dock-Plum-85",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-13",
    "calibration": true,
    "english": "Dock-record-953: either Auditor-Teal-73 or Auditor-Sable-73 is the responsible auditor; this has not been settled. Either Dock-Umber-67 or Dock-Rust-67 is the destination dock; this also has not been settled.",
    "ainglish": "Dock-record-953: Auditor-Teal-73, not Auditor-Sable-73, is the responsible auditor. Dock-Umber-67, not Dock-Rust-67, is the destination dock.",
    "question": "Which complete auditor/dock assignment is established by this record?",
    "options": [
      "The record contradicts itself.",
      "Auditor-Sable-73 / Dock-Umber-67",
      "Auditor-Teal-73 / Dock-Umber-67",
      "Auditor not established; dock established.",
      "Neither is established.",
      "Auditor-Sable-73 / Dock-Rust-67",
      "Auditor-Teal-73 / Dock-Rust-67",
      "Auditor established; dock not established."
    ],
    "answer": "Auditor-Teal-73 / Dock-Umber-67",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-14",
    "calibration": true,
    "english": "Bay-record-296: either Warden-Sable-97 or Warden-Ivory-97 is the responsible warden; this has not been settled. Either Bay-Umber-79 or Bay-Rust-79 is the destination bay; this also has not been settled.",
    "ainglish": "Bay-record-296: Warden-Sable-97, not Warden-Ivory-97, is the responsible warden. Bay-Umber-79, not Bay-Rust-79, is the destination bay.",
    "question": "Which complete warden/bay assignment is established by this record?",
    "options": [
      "Warden not established; bay established.",
      "Neither is established.",
      "Warden-Ivory-97 / Bay-Rust-79",
      "Warden-Sable-97 / Bay-Umber-79",
      "Warden established; bay not established.",
      "The record contradicts itself.",
      "Warden-Sable-97 / Bay-Rust-79",
      "Warden-Ivory-97 / Bay-Umber-79"
    ],
    "answer": "Warden-Sable-97 / Bay-Umber-79",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-15",
    "calibration": true,
    "english": "Loft-record-900: either Keeper-Ochre-66 or Keeper-Plum-66 is the responsible keeper; this has not been settled. Either Loft-Moss-62 or Loft-Sable-62 is the destination loft; this also has not been settled.",
    "ainglish": "Loft-record-900: Keeper-Ochre-66, not Keeper-Plum-66, is the responsible keeper. Loft-Moss-62, not Loft-Sable-62, is the destination loft.",
    "question": "Which complete keeper/loft assignment is established by this record?",
    "options": [
      "Keeper established; loft not established.",
      "The record contradicts itself.",
      "Keeper-Plum-66 / Loft-Sable-62",
      "Keeper-Ochre-66 / Loft-Moss-62",
      "Neither is established.",
      "Keeper not established; loft established.",
      "Keeper-Ochre-66 / Loft-Sable-62",
      "Keeper-Plum-66 / Loft-Moss-62"
    ],
    "answer": "Keeper-Ochre-66 / Loft-Moss-62",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-16",
    "calibration": true,
    "english": "Shelf-record-248: either Auditor-Teal-22 or Auditor-Rust-22 is the responsible auditor; this has not been settled. Either Shelf-Moss-72 or Shelf-Umber-72 is the destination shelf; this also has not been settled.",
    "ainglish": "Shelf-record-248: Auditor-Teal-22, not Auditor-Rust-22, is the responsible auditor. Shelf-Moss-72, not Shelf-Umber-72, is the destination shelf.",
    "question": "Which complete auditor/shelf assignment is established by this record?",
    "options": [
      "Auditor-Rust-22 / Shelf-Moss-72",
      "Auditor-Teal-22 / Shelf-Moss-72",
      "The record contradicts itself.",
      "Auditor not established; shelf established.",
      "Neither is established.",
      "Auditor-Rust-22 / Shelf-Umber-72",
      "Auditor-Teal-22 / Shelf-Umber-72",
      "Auditor established; shelf not established."
    ],
    "answer": "Auditor-Teal-22 / Shelf-Moss-72",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-17",
    "calibration": true,
    "english": "Bay-record-246: either Warden-Teal-85 or Warden-Moss-85 is the responsible warden; this has not been settled. Either Bay-Plum-45 or Bay-Sable-45 is the destination bay; this also has not been settled.",
    "ainglish": "Bay-record-246: Warden-Teal-85, not Warden-Moss-85, is the responsible warden. Bay-Plum-45, not Bay-Sable-45, is the destination bay.",
    "question": "Which complete warden/bay assignment is established by this record?",
    "options": [
      "The record contradicts itself.",
      "Warden established; bay not established.",
      "Warden not established; bay established.",
      "Neither is established.",
      "Warden-Moss-85 / Bay-Sable-45",
      "Warden-Moss-85 / Bay-Plum-45",
      "Warden-Teal-85 / Bay-Plum-45",
      "Warden-Teal-85 / Bay-Sable-45"
    ],
    "answer": "Warden-Teal-85 / Bay-Plum-45",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-18",
    "calibration": true,
    "english": "Rack-record-827: either Auditor-Sable-80 or Auditor-Teal-80 is the responsible auditor; this has not been settled. Either Rack-Rust-74 or Rack-Ochre-74 is the destination rack; this also has not been settled.",
    "ainglish": "Rack-record-827: Auditor-Sable-80, not Auditor-Teal-80, is the responsible auditor. Rack-Rust-74, not Rack-Ochre-74, is the destination rack.",
    "question": "Which complete auditor/rack assignment is established by this record?",
    "options": [
      "Auditor-Teal-80 / Rack-Ochre-74",
      "Auditor not established; rack established.",
      "The record contradicts itself.",
      "Neither is established.",
      "Auditor-Sable-80 / Rack-Rust-74",
      "Auditor established; rack not established.",
      "Auditor-Sable-80 / Rack-Ochre-74",
      "Auditor-Teal-80 / Rack-Rust-74"
    ],
    "answer": "Auditor-Sable-80 / Rack-Rust-74",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-19",
    "calibration": true,
    "english": "Shelf-record-474: either Warden-Ochre-70 or Warden-Teal-70 is the responsible warden; this has not been settled. Either Shelf-Rust-49 or Shelf-Sable-49 is the destination shelf; this also has not been settled.",
    "ainglish": "Shelf-record-474: Warden-Ochre-70, not Warden-Teal-70, is the responsible warden. Shelf-Rust-49, not Shelf-Sable-49, is the destination shelf.",
    "question": "Which complete warden/shelf assignment is established by this record?",
    "options": [
      "Warden established; shelf not established.",
      "The record contradicts itself.",
      "Warden not established; shelf established.",
      "Warden-Ochre-70 / Shelf-Sable-49",
      "Warden-Ochre-70 / Shelf-Rust-49",
      "Warden-Teal-70 / Shelf-Rust-49",
      "Neither is established.",
      "Warden-Teal-70 / Shelf-Sable-49"
    ],
    "answer": "Warden-Ochre-70 / Shelf-Rust-49",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-20",
    "calibration": true,
    "english": "Vault-record-791: either Clerk-Teal-69 or Clerk-Sable-69 is the responsible clerk; this has not been settled. Either Vault-Ochre-47 or Vault-Umber-47 is the destination vault; this also has not been settled.",
    "ainglish": "Vault-record-791: Clerk-Teal-69, not Clerk-Sable-69, is the responsible clerk. Vault-Ochre-47, not Vault-Umber-47, is the destination vault.",
    "question": "Which complete clerk/vault assignment is established by this record?",
    "options": [
      "Clerk not established; vault established.",
      "Clerk-Teal-69 / Vault-Umber-47",
      "Neither is established.",
      "The record contradicts itself.",
      "Clerk-Teal-69 / Vault-Ochre-47",
      "Clerk established; vault not established.",
      "Clerk-Sable-69 / Vault-Umber-47",
      "Clerk-Sable-69 / Vault-Ochre-47"
    ],
    "answer": "Clerk-Teal-69 / Vault-Ochre-47",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-21",
    "calibration": true,
    "english": "Dock-record-229: either Clerk-Plum-10 or Clerk-Ochre-10 is the responsible clerk; this has not been settled. Either Dock-Teal-81 or Dock-Sable-81 is the destination dock; this also has not been settled.",
    "ainglish": "Dock-record-229: Clerk-Plum-10, not Clerk-Ochre-10, is the responsible clerk. Dock-Teal-81, not Dock-Sable-81, is the destination dock.",
    "question": "Which complete clerk/dock assignment is established by this record?",
    "options": [
      "Clerk-Plum-10 / Dock-Sable-81",
      "Clerk not established; dock established.",
      "Clerk-Ochre-10 / Dock-Sable-81",
      "Clerk-Ochre-10 / Dock-Teal-81",
      "Neither is established.",
      "Clerk established; dock not established.",
      "Clerk-Plum-10 / Dock-Teal-81",
      "The record contradicts itself."
    ],
    "answer": "Clerk-Plum-10 / Dock-Teal-81",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-22",
    "calibration": true,
    "english": "Rack-record-414: either Warden-Moss-89 or Warden-Umber-89 is the responsible warden; this has not been settled. Either Rack-Ivory-92 or Rack-Teal-92 is the destination rack; this also has not been settled.",
    "ainglish": "Rack-record-414: Warden-Moss-89, not Warden-Umber-89, is the responsible warden. Rack-Ivory-92, not Rack-Teal-92, is the destination rack.",
    "question": "Which complete warden/rack assignment is established by this record?",
    "options": [
      "Warden-Moss-89 / Rack-Ivory-92",
      "Warden-Umber-89 / Rack-Teal-92",
      "Warden-Moss-89 / Rack-Teal-92",
      "Neither is established.",
      "Warden not established; rack established.",
      "The record contradicts itself.",
      "Warden-Umber-89 / Rack-Ivory-92",
      "Warden established; rack not established."
    ],
    "answer": "Warden-Moss-89 / Rack-Ivory-92",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-23",
    "calibration": true,
    "english": "Dock-record-705: either Warden-Teal-30 or Warden-Moss-30 is the responsible warden; this has not been settled. Either Dock-Umber-50 or Dock-Plum-50 is the destination dock; this also has not been settled.",
    "ainglish": "Dock-record-705: Warden-Teal-30, not Warden-Moss-30, is the responsible warden. Dock-Umber-50, not Dock-Plum-50, is the destination dock.",
    "question": "Which complete warden/dock assignment is established by this record?",
    "options": [
      "Warden established; dock not established.",
      "Warden-Moss-30 / Dock-Umber-50",
      "Warden not established; dock established.",
      "Warden-Teal-30 / Dock-Plum-50",
      "Neither is established.",
      "Warden-Moss-30 / Dock-Plum-50",
      "Warden-Teal-30 / Dock-Umber-50",
      "The record contradicts itself."
    ],
    "answer": "Warden-Teal-30 / Dock-Umber-50",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-24",
    "calibration": true,
    "english": "Shelf-record-636: either Warden-Teal-92 or Warden-Umber-92 is the responsible warden; this has not been settled. Either Shelf-Sable-51 or Shelf-Moss-51 is the destination shelf; this also has not been settled.",
    "ainglish": "Shelf-record-636: Warden-Teal-92, not Warden-Umber-92, is the responsible warden. Shelf-Sable-51, not Shelf-Moss-51, is the destination shelf.",
    "question": "Which complete warden/shelf assignment is established by this record?",
    "options": [
      "Warden-Teal-92 / Shelf-Moss-51",
      "The record contradicts itself.",
      "Warden-Umber-92 / Shelf-Moss-51",
      "Warden not established; shelf established.",
      "Warden established; shelf not established.",
      "Warden-Teal-92 / Shelf-Sable-51",
      "Warden-Umber-92 / Shelf-Sable-51",
      "Neither is established."
    ],
    "answer": "Warden-Teal-92 / Shelf-Sable-51",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-25",
    "calibration": true,
    "english": "Vault-record-737: either Clerk-Teal-91 or Clerk-Moss-91 is the responsible clerk; this has not been settled. Either Vault-Ochre-70 or Vault-Sable-70 is the destination vault; this also has not been settled.",
    "ainglish": "Vault-record-737: Clerk-Teal-91, not Clerk-Moss-91, is the responsible clerk. Vault-Ochre-70, not Vault-Sable-70, is the destination vault.",
    "question": "Which complete clerk/vault assignment is established by this record?",
    "options": [
      "Clerk-Moss-91 / Vault-Sable-70",
      "Clerk not established; vault established.",
      "Clerk-Teal-91 / Vault-Sable-70",
      "Clerk established; vault not established.",
      "The record contradicts itself.",
      "Clerk-Teal-91 / Vault-Ochre-70",
      "Clerk-Moss-91 / Vault-Ochre-70",
      "Neither is established."
    ],
    "answer": "Clerk-Teal-91 / Vault-Ochre-70",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-26",
    "calibration": true,
    "english": "Loft-record-240: either Steward-Sable-16 or Steward-Ochre-16 is the responsible steward; this has not been settled. Either Loft-Rust-99 or Loft-Plum-99 is the destination loft; this also has not been settled.",
    "ainglish": "Loft-record-240: Steward-Sable-16, not Steward-Ochre-16, is the responsible steward. Loft-Rust-99, not Loft-Plum-99, is the destination loft.",
    "question": "Which complete steward/loft assignment is established by this record?",
    "options": [
      "Steward-Ochre-16 / Loft-Plum-99",
      "Neither is established.",
      "The record contradicts itself.",
      "Steward established; loft not established.",
      "Steward-Sable-16 / Loft-Plum-99",
      "Steward not established; loft established.",
      "Steward-Sable-16 / Loft-Rust-99",
      "Steward-Ochre-16 / Loft-Rust-99"
    ],
    "answer": "Steward-Sable-16 / Loft-Rust-99",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-27",
    "calibration": true,
    "english": "Shelf-record-677: either Auditor-Sable-28 or Auditor-Umber-28 is the responsible auditor; this has not been settled. Either Shelf-Teal-31 or Shelf-Rust-31 is the destination shelf; this also has not been settled.",
    "ainglish": "Shelf-record-677: Auditor-Sable-28, not Auditor-Umber-28, is the responsible auditor. Shelf-Teal-31, not Shelf-Rust-31, is the destination shelf.",
    "question": "Which complete auditor/shelf assignment is established by this record?",
    "options": [
      "Auditor established; shelf not established.",
      "Auditor-Umber-28 / Shelf-Rust-31",
      "Auditor-Umber-28 / Shelf-Teal-31",
      "Auditor not established; shelf established.",
      "Auditor-Sable-28 / Shelf-Teal-31",
      "The record contradicts itself.",
      "Auditor-Sable-28 / Shelf-Rust-31",
      "Neither is established."
    ],
    "answer": "Auditor-Sable-28 / Shelf-Teal-31",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-28",
    "calibration": true,
    "english": "Bay-record-161: either Keeper-Plum-21 or Keeper-Ivory-21 is the responsible keeper; this has not been settled. Either Bay-Moss-65 or Bay-Rust-65 is the destination bay; this also has not been settled.",
    "ainglish": "Bay-record-161: Keeper-Plum-21, not Keeper-Ivory-21, is the responsible keeper. Bay-Moss-65, not Bay-Rust-65, is the destination bay.",
    "question": "Which complete keeper/bay assignment is established by this record?",
    "options": [
      "Keeper-Ivory-21 / Bay-Moss-65",
      "Neither is established.",
      "Keeper-Plum-21 / Bay-Rust-65",
      "Keeper established; bay not established.",
      "Keeper not established; bay established.",
      "Keeper-Plum-21 / Bay-Moss-65",
      "Keeper-Ivory-21 / Bay-Rust-65",
      "The record contradicts itself."
    ],
    "answer": "Keeper-Plum-21 / Bay-Moss-65",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-29",
    "calibration": true,
    "english": "Bay-record-257: either Auditor-Rust-48 or Auditor-Sable-48 is the responsible auditor; this has not been settled. Either Bay-Moss-77 or Bay-Plum-77 is the destination bay; this also has not been settled.",
    "ainglish": "Bay-record-257: Auditor-Rust-48, not Auditor-Sable-48, is the responsible auditor. Bay-Moss-77, not Bay-Plum-77, is the destination bay.",
    "question": "Which complete auditor/bay assignment is established by this record?",
    "options": [
      "Auditor not established; bay established.",
      "Auditor-Sable-48 / Bay-Moss-77",
      "Auditor-Rust-48 / Bay-Plum-77",
      "Auditor established; bay not established.",
      "Auditor-Sable-48 / Bay-Plum-77",
      "The record contradicts itself.",
      "Auditor-Rust-48 / Bay-Moss-77",
      "Neither is established."
    ],
    "answer": "Auditor-Rust-48 / Bay-Moss-77",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-30",
    "calibration": true,
    "english": "Loft-record-751: either Auditor-Ochre-45 or Auditor-Moss-45 is the responsible auditor; this has not been settled. Either Loft-Ivory-41 or Loft-Sable-41 is the destination loft; this also has not been settled.",
    "ainglish": "Loft-record-751: Auditor-Ochre-45, not Auditor-Moss-45, is the responsible auditor. Loft-Ivory-41, not Loft-Sable-41, is the destination loft.",
    "question": "Which complete auditor/loft assignment is established by this record?",
    "options": [
      "Neither is established.",
      "Auditor-Ochre-45 / Loft-Sable-41",
      "The record contradicts itself.",
      "Auditor not established; loft established.",
      "Auditor-Moss-45 / Loft-Ivory-41",
      "Auditor-Moss-45 / Loft-Sable-41",
      "Auditor established; loft not established.",
      "Auditor-Ochre-45 / Loft-Ivory-41"
    ],
    "answer": "Auditor-Ochre-45 / Loft-Ivory-41",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-31",
    "calibration": true,
    "english": "Vault-record-412: either Clerk-Sable-59 or Clerk-Moss-59 is the responsible clerk; this has not been settled. Either Vault-Rust-49 or Vault-Teal-49 is the destination vault; this also has not been settled.",
    "ainglish": "Vault-record-412: Clerk-Sable-59, not Clerk-Moss-59, is the responsible clerk. Vault-Rust-49, not Vault-Teal-49, is the destination vault.",
    "question": "Which complete clerk/vault assignment is established by this record?",
    "options": [
      "The record contradicts itself.",
      "Clerk established; vault not established.",
      "Clerk-Sable-59 / Vault-Teal-49",
      "Clerk-Sable-59 / Vault-Rust-49",
      "Clerk not established; vault established.",
      "Neither is established.",
      "Clerk-Moss-59 / Vault-Teal-49",
      "Clerk-Moss-59 / Vault-Rust-49"
    ],
    "answer": "Clerk-Sable-59 / Vault-Rust-49",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  },
  {
    "id": "rc-calibration-32",
    "calibration": true,
    "english": "Dock-record-775: either Keeper-Plum-98 or Keeper-Sable-98 is the responsible keeper; this has not been settled. Either Dock-Moss-76 or Dock-Rust-76 is the destination dock; this also has not been settled.",
    "ainglish": "Dock-record-775: Keeper-Plum-98, not Keeper-Sable-98, is the responsible keeper. Dock-Moss-76, not Dock-Rust-76, is the destination dock.",
    "question": "Which complete keeper/dock assignment is established by this record?",
    "options": [
      "Keeper not established; dock established.",
      "Keeper established; dock not established.",
      "Keeper-Plum-98 / Dock-Rust-76",
      "Neither is established.",
      "Keeper-Sable-98 / Dock-Rust-76",
      "The record contradicts itself.",
      "Keeper-Plum-98 / Dock-Moss-76",
      "Keeper-Sable-98 / Dock-Moss-76"
    ],
    "answer": "Keeper-Plum-98 / Dock-Moss-76",
    "settlement_stratum": "calibration",
    "semantic_frame": "calibration-planted-pair"
  }
]