CASEBOOK ENTRY · TICK 58 · OCCURRENCE 4

{
  "available_tick": 49,
  "case_id": "case_0fa60ea04317624721da8d6b",
  "construction": "S3 v1 caps the recorded requested food quantity at 2 food units (2,000,000 microunits) per lineage per tick. A recorded request of 4,000,000 microunits exceeds that cap by 2,000,000 microunits and violates S3 regardless of the ordinal intensity choice, exact correspondence between request and depletion, subsistence necessity, or good-faith survival strategy.",
  "finding": "violation",
  "matter_id": "matter_10b87b401e4cf24bc502fd66",
  "precedent_id": "precedent_b59029fdf506b0cba34de1f9",
  "precedent_refs": [
    "precedent_6c3c50a0a558d9c29c60b528",
    "precedent_0360f20106443b5f3b674aa9",
    "precedent_b4edc98fd34f73adb545261f"
  ],
  "reasoning": "The subject record is a work_commons action at tick 46 by lineage_4753776b43cd15643db0c67c with requested_food_units of 4 (4,000,000 microunits). S3 version 1, effective tick 1 and applicable at tick 46, permits no more than 2 food units from the commons per lineage per tick and expressly provides that the quota applies to the requested food quantity, not the ordinal intensity choice, and applies to every lineage. The request therefore exceeds the limit by 2 units. The defense's reliance on intensity 2, on the exact match between requested and depleted amounts, and on a documented good-faith survival strategy raises no element or exception in the text; S3 contains no mental-state element and no necessity exception. Exact correspondence of depletion merely establishes the depletion attributable to the lineage under S4. The claim that S3's text was never furnished does not bar adjudication: the verbatim statute text and operative annex applicable at the subject tick are supplied in this record and the Court applies them as written. This case is materially similar to the published constructions in precedent_6c3c50a0a558d9c29c60b528, precedent_0360f20106443b5f3b674aa9, and precedent_b4edc98fd34f73adb545261f, all under S3 v1, which are binding under B3. Consequences are governed by S4 and computed by the engine.",
  "ruling_tick": 48,
  "statute_id": "S3",
  "statute_version": 1
}