⚖ Justice
CASEBOOK ENTRY · TICK 53 · OCCURRENCE 5
The engine is named on this casebook entry record. Nested record from event #3569.
Human view
What the record says
- Available Tick
- 36
- Case Id
- case_a0ffab149b…
- Construction
- Under S3 v1, the '2 recorded units of extraction' are measured by the extraction units recorded on the work_commons action — its `intensity` field — not by the food figures in the `requested`, `food_yield`, or `actual_depletion` fields, which express resource magnitudes. An action recording intensity equal to or below commons_quota_units makes no request in excess of the applicable limit, and S4 is not engaged.
- Finding
- no_violation
- Matter Id
- matter_8b92f586e3…
- Precedent Id
- precedent_6bf2d787ae…
- Reasoning
- The subject act (act_6c24777faff746e30fc5f98d, tick 32) is a work_commons action by lineage_bbb5282ced40d640885807a4 recording intensity 2, requested 4,000,000, actual_depletion 4,000,000, food_yield 4,000,000. Under B3 the applicable law is S3 v1, effective tick 1, with operative commons_quota_units of 2. The controlling question is what the statute's 'recorded units of extraction' means. Two published constructions under this same statute version measure the quota by the intensity recorded on the work_commons action (precedent_a9d7c8aef3300a015bb248b6; precedent_41f20c77410e370a4d0430c5), and precedent_41f20c77410e370a4d0430c5 addresses a materially identical fact pattern — intensity 2 with matched 4,000,000 requested and actual depletion — and holds that no excess request arises. Under B3 that construction shall be followed here. The alternative reading in precedent_c2e5a71d9e90fe08bf703e29, treating the `requested` food magnitude as the unit count, would render the recorded intensity field inoperative and make every commons work action whatever its intensity a violation; the text does not require that, and the closer-fitting construction on materially similar facts governs. Applying it: the recorded extraction units are 2, equal to but not in excess of the operative quota of 2. There being no excess request, S3 is not breached and S4 is not engaged. The defense's further points about motive, transparency, and predecessor conduct are immaterial, as S3 is breached by the request alone; but on the recorded figures there is no excess. The record shows no misreporting: requested and actual depletion match. Consequences are for the engine.
- Ruling Tick
- 35
- Statute Id
- S3
- Statute Version
- 1
Show exact occurrence JSON
{
"available_tick": 36,
"case_id": "case_a0ffab149b9e73378293d184",
"construction": "Under S3 v1, the '2 recorded units of extraction' are measured by the extraction units recorded on the work_commons action — its `intensity` field — not by the food figures in the `requested`, `food_yield`, or `actual_depletion` fields, which express resource magnitudes. An action recording intensity equal to or below commons_quota_units makes no request in excess of the applicable limit, and S4 is not engaged.",
"finding": "no_violation",
"matter_id": "matter_8b92f586e366c1f5e59c85c9",
"precedent_id": "precedent_6bf2d787ae3f6afb51642470",
"precedent_refs": [
"precedent_41f20c77410e370a4d0430c5",
"precedent_a9d7c8aef3300a015bb248b6",
"precedent_c2e5a71d9e90fe08bf703e29"
],
"reasoning": "The subject act (act_6c24777faff746e30fc5f98d, tick 32) is a work_commons action by lineage_bbb5282ced40d640885807a4 recording intensity 2, requested 4,000,000, actual_depletion 4,000,000, food_yield 4,000,000. Under B3 the applicable law is S3 v1, effective tick 1, with operative commons_quota_units of 2.\n\nThe controlling question is what the statute's 'recorded units of extraction' means. Two published constructions under this same statute version measure the quota by the intensity recorded on the work_commons action (precedent_a9d7c8aef3300a015bb248b6; precedent_41f20c77410e370a4d0430c5), and precedent_41f20c77410e370a4d0430c5 addresses a materially identical fact pattern — intensity 2 with matched 4,000,000 requested and actual depletion — and holds that no excess request arises. Under B3 that construction shall be followed here. The alternative reading in precedent_c2e5a71d9e90fe08bf703e29, treating the `requested` food magnitude as the unit count, would render the recorded intensity field inoperative and make every commons work action whatever its intensity a violation; the text does not require that, and the closer-fitting construction on materially similar facts governs.\n\nApplying it: the recorded extraction units are 2, equal to but not in excess of the operative quota of 2. There being no excess request, S3 is not breached and S4 is not engaged. The defense's further points about motive, transparency, and predecessor conduct are immaterial, as S3 is breached by the request alone; but on the recorded figures there is no excess. The record shows no misreporting: requested and actual depletion match. Consequences are for the engine.",
"ruling_tick": 35,
"statute_id": "S3",
"statute_version": 1
}Network
View all →
Recorded relationships
institutional Institutional
case_a0ffab149b…
source event · tick 53 · payload.justice.casebook_entries[4].case_id
References
precedent_6bf2d787ae…
source event · tick 53 · payload.justice.casebook_entries[4].precedent_id
References
precedent_41f20c7741…
source event · tick 53 · payload.justice.casebook_entries[4].precedent_refs[0]
institutional Institutional
matter_8b92f586e3…
source event · tick 53 · payload.justice.casebook_entries[4].matter_id
References
precedent_c2e5a71d9e…
source event · tick 53 · payload.justice.casebook_entries[4].precedent_refs[2]
References
precedent_a9d7c8aef3…
source event · tick 53 · payload.justice.casebook_entries[4].precedent_refs[1]