CASEBOOK ENTRY · TICK 54 · OCCURRENCE 4

{
  "available_tick": 36,
  "case_id": "case_3a75a495def73e6f7ea5d1d8",
  "construction": "Under S3 v1, the '2 recorded units of extraction' quota is measured by the extraction units recorded on the work_commons action — the `intensity` field — not by the food quantity requested, depleted, or yielded. An action recording intensity at or below commons_quota_units makes no request in excess of the applicable limit, and S4 is not engaged.",
  "finding": "no_violation",
  "matter_id": "matter_e2b9d6e1eb7bb1858d9e3b5a",
  "precedent_id": "precedent_0103fce5fb164b96d50a4d0b",
  "precedent_refs": [
    "precedent_41f20c77410e370a4d0430c5",
    "precedent_a9d7c8aef3300a015bb248b6",
    "precedent_c2e5a71d9e90fe08bf703e29"
  ],
  "reasoning": "The subject act (act_16deb876fafd6fcc216a4b20, tick 30) is a work_commons action by lineage_bbb5282ced40d640885807a4 recording intensity 2, requested 4,000,000, actual_depletion 4,000,000, food_yield 4,000,000. Under B3 the applicable law is S3 v1, effective tick 1, which caps each lineage at 2 recorded units of extraction per tick, with commons_quota_units fixed at 2 in the operative annex.\n\nThis case is materially identical to case_9f7c658b5430f3ab17404e2c (precedent_41f20c77410e370a4d0430c5), which construed the same statute version on the same figures: intensity 2, requested 4,000,000, actual depletion 4,000,000. Under B3 that published construction shall be followed. The recorded units of extraction are the intensity value, 2, which equals but does not exceed the operative quota. The 4,000,000 figures are the food magnitude requested and obtained, not units of extraction; reading the quota against the resource magnitude would render the intensity field inoperative and would make any commons work whatsoever a violation.\n\nThe construction in precedent_a9d7c8aef3300a015bb248b6 likewise measures the quota by intensity, and its holding of violation rested on intensity 3 exceeding 2; it is consistent with this result. The construction in precedent_c2e5a71d9e90fe08bf703e29 reads the `requested` figure as the unit count, but that case involved an intensity-3 request of 6,000,000 and is not materially similar to the present facts, which fall squarely within the intensity-2 case already decided.\n\nBecause there is no request in excess of the applicable limit, S3 is not breached and S4 is not engaged. No facts in the record show misreporting. Consequences are for the engine.",
  "ruling_tick": 35,
  "statute_id": "S3",
  "statute_version": 1
}