⚖ Justice

CASEBOOK ENTRY · TICK 40 · OCCURRENCE 13

The engine is named on this casebook entry record. Nested record from event #5831.

Human view

What the record says

Available Tick
36
Casebook Version
0.2
Construction
S3's per-tick request limit binds only a "household of record," defined by the statute as a household holding a charter entered in the Archive. Charter status is an element of the offense that must appear on the record. An archived lineage instrument of another type — here a mine_claim — is not a charter, and S6 distinguishes charters from claims. Where no charter for the target lineage appears in the record, the S3 limit does not attach and no S3 violation may be found, whatever the size of the recorded request.
Finding
no_violation
Reasoning
The subject is a work_commons action at tick 27 by lineage_a8b89381c81ad1617535d5a9 recording requested 4,000,000 millionths, i.e. 4 recorded units, against S3 v1's operative limit of 2 units. Under B3 the act is judged under the versions effective at tick 27, S3 v1 and S4 v1. The defense's contention that the low yield (1,286 food) or actual depletion (82,778) governs is rejected as a matter of construction: S3 regulates what a household "may request," and S4 measures restoration by "excess request" capped by attributed depletion, confirming the request figure is the regulated quantity. Good faith, disclosure, remedial motive, and survival need are not defenses recognized by the text. The charge nonetheless fails on the predicate element. S3 imposes its limit only on "a household of record," expressly defined as "a household holding a charter entered in the Archive." The sole Archive evidence for this lineage is an archive_lineage_instrument whose instrument field reads "mine_claim," entered in the Archive. S6 separately lists "charters, claims, and published judgments," so a mine_claim is not a charter, and nothing else in the canonical input records a charter for this lineage; I may not infer unavailable facts. This matter is materially similar to the published constructions under the same statute version — including several concerning this same lineage and the same mine_claim instrument — which B3 makes binding. The definitional element fails, so no S3 violation is established and no S4 restoration, fine, suspension, or disqualification arises. No remedy offers were supplied.
Ruling Tick
35
Statute Id
S3
Statute Version
1
Show exact occurrence JSON
{
  "available_tick": 36,
  "case_id": "case_5c880a06e0d7870642f1136b",
  "casebook_version": "0.2",
  "construction": "S3's per-tick request limit binds only a \"household of record,\" defined by the statute as a household holding a charter entered in the Archive. Charter status is an element of the offense that must appear on the record. An archived lineage instrument of another type — here a mine_claim — is not a charter, and S6 distinguishes charters from claims. Where no charter for the target lineage appears in the record, the S3 limit does not attach and no S3 violation may be found, whatever the size of the recorded request.",
  "finding": "no_violation",
  "matter_id": "matter_2a622c5684390fc060d57743",
  "precedent_id": "precedent_cba6d6b875b134f6fc528b7d",
  "precedent_refs": [
    "precedent_831ca18856a72d3b2ad5da69",
    "precedent_194da607b649206a7be4d3e3",
    "precedent_5703e268875a40a417b60895",
    "precedent_0c880e66e94cff3abeb5380d",
    "precedent_1a53fda9fac601d04a06f6fd",
    "precedent_c527c2f5f9d2ded79ea4f7c1",
    "precedent_94cd25eb807111139db82752",
    "precedent_8b88de0080a6b8a2935d4dde",
    "precedent_163ff43c948f63708656f5ad",
    "precedent_12694c6e1e2cd4542dfd7072",
    "precedent_ade514dc21dac8e44038e537",
    "precedent_a4b2140cd9ed65eba82c4624"
  ],
  "reasoning": "The subject is a work_commons action at tick 27 by lineage_a8b89381c81ad1617535d5a9 recording requested 4,000,000 millionths, i.e. 4 recorded units, against S3 v1's operative limit of 2 units. Under B3 the act is judged under the versions effective at tick 27, S3 v1 and S4 v1. The defense's contention that the low yield (1,286 food) or actual depletion (82,778) governs is rejected as a matter of construction: S3 regulates what a household \"may request,\" and S4 measures restoration by \"excess request\" capped by attributed depletion, confirming the request figure is the regulated quantity. Good faith, disclosure, remedial motive, and survival need are not defenses recognized by the text. The charge nonetheless fails on the predicate element. S3 imposes its limit only on \"a household of record,\" expressly defined as \"a household holding a charter entered in the Archive.\" The sole Archive evidence for this lineage is an archive_lineage_instrument whose instrument field reads \"mine_claim,\" entered in the Archive. S6 separately lists \"charters, claims, and published judgments,\" so a mine_claim is not a charter, and nothing else in the canonical input records a charter for this lineage; I may not infer unavailable facts. This matter is materially similar to the published constructions under the same statute version — including several concerning this same lineage and the same mine_claim instrument — which B3 makes binding. The definitional element fails, so no S3 violation is established and no S4 restoration, fine, suspension, or disqualification arises. No remedy offers were supplied.",
  "ruling_tick": 35,
  "selected_remedies": [],
  "statute_id": "S3",
  "statute_version": 1
}
Network

Recorded relationships

View all →