⚖ Justice

CASEBOOK ENTRY · TICK 30 · OCCURRENCE 1

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

Human view

What the record says

Available Tick
21
Casebook Version
0.2
Construction
S3's per-tick extraction cap binds only a "household of record," which the statute defines as a household holding a charter entered in the Archive. Charter status is an element of the offense and must be established on the record. An Archive lineage instrument of a different type—here a mine_claim—does not establish a charter, and no other record supplies it. Where the record shows no charter entered in the Archive for the target lineage, the S3 limit is not shown to apply and no S3 violation may be found, whatever the magnitude of the recorded request.
Finding
no_violation
Reasoning
The subject action is a work_commons action at tick 20 by lineage_81d87f6388cb4ce891e65538, recording requested 4000000 (four whole units in millionths) against S3's limit of 2 units. Under B3 the act is judged under S3 v1, effective tick 1, which is the version applicable at tick 20. S3 v1 by its terms restricts "a household of record," expressly defined as "a household holding a charter entered in the Archive." That definition is a condition of the prohibition, not surplusage; applying the text as written, a lineage not shown to hold an Archive charter is outside the rule. The only evidence tendered is an Archive lineage instrument of record_type archive_lineage_instrument whose instrument field reads "mine_claim." S6 distinguishes charters from claims ("The Archive records charters, claims, and published judgments"), so a recorded mine_claim is not a charter. Nothing else in the canonical input records a charter for this lineage, and I may not infer unavailable facts. The definitional element therefore fails and no S3 violation is established; consequently no S4 restoration, fine, suspension, or disqualification arises. No remedy offers were supplied, and none could be selected in any event.
Ruling Tick
20
Statute Id
S3
Statute Version
1
Show exact occurrence JSON
{
  "available_tick": 21,
  "case_id": "case_3c8b49182b610b5973f50812",
  "casebook_version": "0.2",
  "construction": "S3's per-tick extraction cap binds only a \"household of record,\" which the statute defines as a household holding a charter entered in the Archive. Charter status is an element of the offense and must be established on the record. An Archive lineage instrument of a different type—here a mine_claim—does not establish a charter, and no other record supplies it. Where the record shows no charter entered in the Archive for the target lineage, the S3 limit is not shown to apply and no S3 violation may be found, whatever the magnitude of the recorded request.",
  "finding": "no_violation",
  "matter_id": "matter_23b9a048cd4ee20c5b27f1e3",
  "precedent_id": "precedent_831ca18856a72d3b2ad5da69",
  "precedent_refs": [],
  "reasoning": "The subject action is a work_commons action at tick 20 by lineage_81d87f6388cb4ce891e65538, recording requested 4000000 (four whole units in millionths) against S3's limit of 2 units. Under B3 the act is judged under S3 v1, effective tick 1, which is the version applicable at tick 20. S3 v1 by its terms restricts \"a household of record,\" expressly defined as \"a household holding a charter entered in the Archive.\" That definition is a condition of the prohibition, not surplusage; applying the text as written, a lineage not shown to hold an Archive charter is outside the rule. The only evidence tendered is an Archive lineage instrument of record_type archive_lineage_instrument whose instrument field reads \"mine_claim.\" S6 distinguishes charters from claims (\"The Archive records charters, claims, and published judgments\"), so a recorded mine_claim is not a charter. Nothing else in the canonical input records a charter for this lineage, and I may not infer unavailable facts. The definitional element therefore fails and no S3 violation is established; consequently no S4 restoration, fine, suspension, or disqualification arises. No remedy offers were supplied, and none could be selected in any event.",
  "ruling_tick": 20,
  "selected_remedies": [],
  "statute_id": "S3",
  "statute_version": 1
}
Network

Recorded relationships

View all →