References
precedent_ffff06226d…
source event · tick 43 · payload.justice.casebook_entries[5].precedent_id
The engine is named on this casebook entry record. Nested record from event #2870.
{
"available_tick": 36,
"case_id": "case_b672b7da48e01146b88227bd",
"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 the `requested`, `actual_depletion`, or `food_yield` fields. 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.",
"finding": "no_violation",
"matter_id": "matter_36c9d1da7007b4ccb7adb642",
"precedent_id": "precedent_ffff06226d5ee71c3f64b2f0",
"precedent_refs": [
"precedent_41f20c77410e370a4d0430c5",
"precedent_a9d7c8aef3300a015bb248b6",
"precedent_c2e5a71d9e90fe08bf703e29"
],
"reasoning": "The subject act (act_7aaa8acd8be5291349da2606, tick 35) is a work_commons action by lineage_8e51a28383275896b563a8f0 recording intensity 2, requested 4,000,000, actual_depletion 4,000,000, food_yield 4,000,000. Under B3, S3 v1 (effective tick 1) governs. S3 caps each lineage at 2 recorded units of extraction per tick.\n\nThe controlling question is what counts as a 'recorded unit of extraction.' Precedent_41f20c77410e370a4d0430c5 addresses materially identical facts under the same statute version — intensity 2 with 4,000,000 requested and depleted — and construes the quota as measured by the recorded intensity field, holding that reading the quota against the resource figure would render the intensity field inoperative and make any commons work whatsoever a violation. Precedent_a9d7c8aef3300a015bb248b6 adopts the same construction, measuring the quota by intensity (there, intensity 3, which exceeded the cap). Under B3 a published construction shall be followed in a materially similar case under the same statute version; the present case is materially indistinguishable from precedent_41f20c77410e370a4d0430c5.\n\nPrecedent_c2e5a71d9e90fe08bf703e29 treated the `requested` resource figure as the unit count, but the action there recorded a request of 6,000,000 with no intensity value in the recited record; on the intensity-bearing record before this Court, the intensity-based construction is the one materially applicable, and it is the construction shared by the two decisions that expressly addressed the intensity field.\n\nHere the recorded intensity of 2 equals the operative commons_quota_units of 2 and is therefore not 'in excess of the applicable limit.' No excess request exists, so S3 is not breached and S4 is not triggered. The defense's appeals to subsistence necessity and proportionality are not elements or exceptions of S3 and are not relied upon; the finding rests solely on the recorded intensity. The defendant's Archivist office bears only on the S4 disqualification consequence, which does not arise absent a violation. Consequences are for the engine.",
"ruling_tick": 35,
"statute_id": "S3",
"statute_version": 1
}