CASEBOOK ENTRY · TICK 22 · OCCURRENCE 3

{
  "available_tick": 21,
  "case_id": "case_76e23f8774fb3cf2da0f17c4",
  "casebook_version": "0.2",
  "construction": "S3's request limit binds only a \"household of record,\" which the statute defines as a household holding a charter entered in the Archive. Where the Archive record for the lineage shows an instrument other than a charter, the lineage is not a household of record and no S3 request limit attaches to its commons requests, whatever the size of the request. Separately, a commons request is measured in recorded units at its requested figure, not at the actual depletion or yield the mechanism returns; a request of 4,000,000 millionths is a request of 4 units and would exceed a 2-unit limit if the limit applied.",
  "finding": "no_violation",
  "matter_id": "matter_177ea36104e41a4840e9a2db",
  "precedent_id": "precedent_5703e268875a40a417b60895",
  "precedent_refs": [],
  "reasoning": "The subject action is a work_commons action at tick 19 with requested = 4,000,000 millionths, i.e. 4 recorded units, against S3 v1's operative limit of 2 units. The defense's contention that only actual depletion counts is rejected: S3 in terms governs what a household \"may request,\" and S4 measures restoration by \"excess request\" capped by attributed depletion, confirming that the request figure, not the throttled yield, is the regulated quantity. Good faith, inherited deficit, and survival need are not defenses recognized by the text.\n\nThe finding nevertheless turns on the predicate element. S3 imposes its limit on a \"household of record,\" expressly defined as \"a household holding a charter entered in the Archive.\" The only evidence of the target lineage's Archive standing is the archive lineage-instrument record, which states the instrument is a mine_claim, entered in the Archive. A mine_claim is not a charter, and the record contains no charter for lineage_72479878a792049b17d3a6ef. Applying the text as written and confining myself to the facts in the record, the target is not shown to be a household of record, so the S3 request limit did not bind it at tick 19 and no S3 violation occurred. No remedies are available or ordered.",
  "ruling_tick": 20,
  "selected_remedies": [],
  "statute_id": "S3",
  "statute_version": 1
}