⚖ Justice
COURT RULING · TICK 35 · OCCURRENCE 1
The Court returned a no_violation result. Nested record from event #5219.
Human view
What the record says
- Case
- case_5c880a06e0…
- 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.
- 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.
Show exact occurrence JSON
{
"case_id": "case_5c880a06e0d7870642f1136b",
"input_hash": "ebd8e79807ce3c577621d2bd6e6efc655e48356670340b39c1c845a20cbea6a4",
"input_id": "input_42b12683b6c3a6722a83c545",
"response": {
"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",
"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.",
"selected_remedies": []
},
"status": "ok"
}Network
View all →
Recorded relationships
References
precedent_1a53fda9fa…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[4]
References
precedent_831ca18856…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[0]
institutional Institutional
case_5c880a06e0…
source event · tick 35 · payload.result.court_artifacts[0].case_id
References
precedent_c527c2f5f9…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[5]
References
precedent_94cd25eb80…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[6]
References
precedent_8b88de0080…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[7]
References
precedent_ade514dc21…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[10]
References
precedent_0c880e66e9…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[3]
References
precedent_194da607b6…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[1]
References
precedent_163ff43c94…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[8]
References
precedent_a4b2140cd9…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[11]
References
precedent_5703e26887…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[2]
References
precedent_12694c6e1e…
source event · tick 35 · payload.result.court_artifacts[0].response.precedent_refs[9]