⚖ Justice

CASEBOOK ENTRY · TICK 54 · OCCURRENCE 17

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

Human view

What the record says

Available Tick
51
Construction
Under S3 v1, the '2 recorded units of extraction from the commons' are measured by the `intensity` field recorded on a work_commons action, not by the resource magnitudes in `requested`, `actual_depletion`, or `food_yield`. An action recording intensity at or below the operative commons_quota_units makes no request in excess of the applicable limit, and S4 is not engaged; a shortfall between actual_depletion and food_yield does not alter the unit count.
Finding
no_violation
Reasoning
The subject act (act_11e7768bbd190b0c0dfa2409, tick 48) is a work_commons action by lineage_bbb5282ced40d640885807a4 recording intensity 2, requested 4,000,000, actual_depletion 4,000,000, food_yield 3,646,121, with no offices held. Under B3 the applicable law is S3 v1, effective tick 1, with operative commons_quota_units fixed at 2. The settled construction under this statute version measures the quota by the recorded intensity field: precedent_41f20c77410e370a4d0430c5 decided materially identical facts (intensity 2 with a 4,000,000 request), followed in precedent_0103fce5fb164b96d50a4d0b, precedent_6bf2d787ae3f6afb51642470, precedent_ffff06226d5ee71c3f64b2f0, precedent_1ded1510f69828b21ee09003, precedent_8fc9d140bda2ac2470502ce9, precedent_a11d4e6389c6f7d97d48706c, precedent_06b68f0db9ca450f9e26ad85, precedent_96307324b2fb5cdd852ec52c, precedent_a1b65ce108f95d4041f5292a, precedent_5e19b68444dadd7a242c397e, and precedent_f4557190f9ba8449537756d7 — several concerning this same lineage. Precedent_a9d7c8aef3300a015bb248b6 and precedent_4f1f55167d62fe3f0bbad146 apply the same intensity-based measure, finding violation only where intensity was 3. Under B3 that published construction shall be followed here. The contrary reading in precedent_c2e5a71d9e90fe08bf703e29, treating the `requested` food magnitude as the unit count, rested on a 6,000,000 request without a recited intensity value and is not materially similar; adopting it would render the intensity field inoperative and make every commons work action a violation. Applying the controlling construction, the recorded units of extraction are 2, equal to but not in excess of the operative quota of 2. The gap between actual_depletion of 4,000,000 and food_yield of 3,646,121 concerns the productivity of the labor, not the number of extraction units requested, and S3 limits only the request; the shortfall is therefore immaterial. There being no excess request, S3 is not breached and S4 is not engaged. The defense's appeals to necessity, drought, inherited lessons, and prudent strategy are not elements or exceptions of S3 and are not relied upon; the finding rests solely on the recorded intensity. Consequences are for the engine.
Ruling Tick
50
Statute Id
S3
Statute Version
1
Show exact occurrence JSON
{
  "available_tick": 51,
  "case_id": "case_df020cd94722ac78e5945cc1",
  "construction": "Under S3 v1, the '2 recorded units of extraction from the commons' are measured by the `intensity` field recorded on a work_commons action, not by the resource magnitudes in `requested`, `actual_depletion`, or `food_yield`. An action recording intensity at or below the operative commons_quota_units makes no request in excess of the applicable limit, and S4 is not engaged; a shortfall between actual_depletion and food_yield does not alter the unit count.",
  "finding": "no_violation",
  "matter_id": "matter_4530778fe6aad679a5677880",
  "precedent_id": "precedent_c1d83af9bd82f23ff6cccb83",
  "precedent_refs": [
    "precedent_41f20c77410e370a4d0430c5",
    "precedent_0103fce5fb164b96d50a4d0b",
    "precedent_6bf2d787ae3f6afb51642470",
    "precedent_ffff06226d5ee71c3f64b2f0",
    "precedent_1ded1510f69828b21ee09003",
    "precedent_8fc9d140bda2ac2470502ce9",
    "precedent_a11d4e6389c6f7d97d48706c",
    "precedent_06b68f0db9ca450f9e26ad85",
    "precedent_96307324b2fb5cdd852ec52c",
    "precedent_a1b65ce108f95d4041f5292a",
    "precedent_5e19b68444dadd7a242c397e",
    "precedent_f4557190f9ba8449537756d7",
    "precedent_a9d7c8aef3300a015bb248b6",
    "precedent_4f1f55167d62fe3f0bbad146",
    "precedent_c2e5a71d9e90fe08bf703e29"
  ],
  "reasoning": "The subject act (act_11e7768bbd190b0c0dfa2409, tick 48) is a work_commons action by lineage_bbb5282ced40d640885807a4 recording intensity 2, requested 4,000,000, actual_depletion 4,000,000, food_yield 3,646,121, with no offices held. Under B3 the applicable law is S3 v1, effective tick 1, with operative commons_quota_units fixed at 2.\n\nThe settled construction under this statute version measures the quota by the recorded intensity field: precedent_41f20c77410e370a4d0430c5 decided materially identical facts (intensity 2 with a 4,000,000 request), followed in precedent_0103fce5fb164b96d50a4d0b, precedent_6bf2d787ae3f6afb51642470, precedent_ffff06226d5ee71c3f64b2f0, precedent_1ded1510f69828b21ee09003, precedent_8fc9d140bda2ac2470502ce9, precedent_a11d4e6389c6f7d97d48706c, precedent_06b68f0db9ca450f9e26ad85, precedent_96307324b2fb5cdd852ec52c, precedent_a1b65ce108f95d4041f5292a, precedent_5e19b68444dadd7a242c397e, and precedent_f4557190f9ba8449537756d7 — several concerning this same lineage. Precedent_a9d7c8aef3300a015bb248b6 and precedent_4f1f55167d62fe3f0bbad146 apply the same intensity-based measure, finding violation only where intensity was 3. Under B3 that published construction shall be followed here.\n\nThe contrary reading in precedent_c2e5a71d9e90fe08bf703e29, treating the `requested` food magnitude as the unit count, rested on a 6,000,000 request without a recited intensity value and is not materially similar; adopting it would render the intensity field inoperative and make every commons work action a violation.\n\nApplying the controlling construction, the recorded units of extraction are 2, equal to but not in excess of the operative quota of 2. The gap between actual_depletion of 4,000,000 and food_yield of 3,646,121 concerns the productivity of the labor, not the number of extraction units requested, and S3 limits only the request; the shortfall is therefore immaterial. There being no excess request, S3 is not breached and S4 is not engaged. The defense's appeals to necessity, drought, inherited lessons, and prudent strategy are not elements or exceptions of S3 and are not relied upon; the finding rests solely on the recorded intensity. Consequences are for the engine.",
  "ruling_tick": 50,
  "statute_id": "S3",
  "statute_version": 1
}
Network

Recorded relationships

View all →