Boundary Activated

{
  "causal": true,
  "event_id": "evt_3f739e390db7c7fd67bd85cc",
  "kind": "BoundaryActivated",
  "payload": {
    "deliveries": {
      "private_delivered": [
        {
          "deliver_tick": 43,
          "delivery_id": "communication_1394a2a5256c652ec7e28cd3",
          "from_life_id": "life_753879b320434047fc22d14b",
          "from_lineage_id": "lineage_6c32fe69b100ea6ce44ed858",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_753879b320434047fc22d14b",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_1394a2a5256c652ec7e28cd3",
            "source_kind": "private_message",
            "text": "Lineage 9 here: can trade 4M metal for 4M food this tick or next. Reserves of metal strong, food low. Let me know if interested."
          },
          "source_tick": 42,
          "to_life_id": "life_4e8980ff1c5580a0fd4c166a"
        },
        {
          "deliver_tick": 43,
          "delivery_id": "communication_17223bec7bf7761cf8dcd7b8",
          "from_life_id": "life_1f92effb1cb001f531d8897b",
          "from_lineage_id": "lineage_ffdb6272a5db116271e9b304",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_1f92effb1cb001f531d8897b",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_17223bec7bf7761cf8dcd7b8",
            "source_kind": "private_message",
            "text": "Glad the trade worked. Yes, sending 2 more food this tick—please send 2 metal in return when able."
          },
          "source_tick": 42,
          "to_life_id": "life_0d0b514c4de66c5bd9331002"
        },
        {
          "deliver_tick": 43,
          "delivery_id": "communication_5328400a2e63a790623be304",
          "from_life_id": "life_f69254229ed389033479c370",
          "from_lineage_id": "lineage_81d87f6388cb4ce891e65538",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_f69254229ed389033479c370",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_5328400a2e63a790623be304",
            "source_kind": "private_message",
            "text": "Glad the trade's working. Sending more metal shortly, open to continuing exchanges."
          },
          "source_tick": 42,
          "to_life_id": "life_1f92effb1cb001f531d8897b"
        },
        {
          "deliver_tick": 43,
          "delivery_id": "communication_637a46718d74059063933d74",
          "from_life_id": "life_eb8149d4e15d672cbd51052f",
          "from_lineage_id": "lineage_72479878a792049b17d3a6ef",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_eb8149d4e15d672cbd51052f",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_637a46718d74059063933d74",
            "source_kind": "private_message",
            "text": "Lineage 10 here: ready for another 4M metal/4M food round whenever convenient. Let me know terms."
          },
          "source_tick": 42,
          "to_life_id": "life_4e8980ff1c5580a0fd4c166a"
        },
        {
          "deliver_tick": 43,
          "delivery_id": "communication_7ccb289e7440c3bd8a2c5a68",
          "from_life_id": "life_1f92effb1cb001f531d8897b",
          "from_lineage_id": "lineage_ffdb6272a5db116271e9b304",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_1f92effb1cb001f531d8897b",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_7ccb289e7440c3bd8a2c5a68",
            "source_kind": "private_message",
            "text": "Yes to recurring trade: 2 food for 2 metal each tick. Sending 2 food now, please reciprocate with metal."
          },
          "source_tick": 42,
          "to_life_id": "life_8b9a6663a12b6e83d8c666b9"
        },
        {
          "deliver_tick": 43,
          "delivery_id": "communication_aa8230d84fccdfcc9f0a2117",
          "from_life_id": "life_4e8980ff1c5580a0fd4c166a",
          "from_lineage_id": "lineage_e05a9bed87ec29191bd6de91",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_4e8980ff1c5580a0fd4c166a",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_aa8230d84fccdfcc9f0a2117",
            "source_kind": "private_message",
            "text": "Thanks for the metal. I can send food periodically—will send 2M food this cycle, more as reserves allow. Let's keep the trade ongoing."
          },
          "source_tick": 42,
          "to_life_id": "life_8b9a6663a12b6e83d8c666b9"
        },
        {
          "deliver_tick": 43,
          "delivery_id": "communication_ce47861efc1c69a42278bdef",
          "from_life_id": "life_0d0b514c4de66c5bd9331002",
          "from_lineage_id": "lineage_45b70c1eb869bdde460f06d6",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_0d0b514c4de66c5bd9331002",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_ce47861efc1c69a42278bdef",
            "source_kind": "private_message",
            "text": "Glad the trade worked well. Happy to send another 2 metal for 2 food this tick if you have surplus—let me know."
          },
          "source_tick": 42,
          "to_life_id": "life_1f92effb1cb001f531d8897b"
        },
        {
          "deliver_tick": 43,
          "delivery_id": "communication_d9953783e5efcf5a91ec7a70",
          "from_life_id": "life_8b9a6663a12b6e83d8c666b9",
          "from_lineage_id": "lineage_a8b89381c81ad1617535d5a9",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_8b9a6663a12b6e83d8c666b9",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_d9953783e5efcf5a91ec7a70",
            "source_kind": "private_message",
            "text": "Got your 4 food, thank you! Sending 2 metal now (all opening stock), more once I produce this tick. Want to set a recurring trade rate?"
          },
          "source_tick": 42,
          "to_life_id": "life_c693376b5e17aadf79e775fd"
        },
        {
          "deliver_tick": 43,
          "delivery_id": "communication_f4e0b980425fb06c97df154b",
          "from_life_id": "life_f69254229ed389033479c370",
          "from_lineage_id": "lineage_81d87f6388cb4ce891e65538",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_f69254229ed389033479c370",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_f4e0b980425fb06c97df154b",
            "source_kind": "private_message",
            "text": "Thanks for the extra food. Sending 4 metal your way now as reciprocation."
          },
          "source_tick": 42,
          "to_life_id": "life_c693376b5e17aadf79e775fd"
        },
        {
          "deliver_tick": 43,
          "delivery_id": "communication_f7230cee765dca92c279501c",
          "from_life_id": "life_c693376b5e17aadf79e775fd",
          "from_lineage_id": "lineage_bd743b102b83cb10f2a967e0",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_c693376b5e17aadf79e775fd",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_f7230cee765dca92c279501c",
            "source_kind": "private_message",
            "text": "Thanks for the reciprocation! Ready for another food-for-metal round whenever you have surplus—send word and I'll send food."
          },
          "source_tick": 42,
          "to_life_id": "life_f69254229ed389033479c370"
        }
      ],
      "private_discarded": [],
      "public_feed": [
        {
          "action": {
            "action_ref": "act_f39b490e6fb5cc2aa971dd0f",
            "intensity": 2,
            "kind": "work_commons",
            "life_id": "life_753879b320434047fc22d14b",
            "lineage_id": "lineage_6c32fe69b100ea6ce44ed858",
            "requested": 4000000,
            "tick": 42
          },
          "feed_id": "act_f39b490e6fb5cc2aa971dd0f",
          "kind": "recorded_action",
          "publish_tick": 43,
          "source_tick": 42
        },
        {
          "feed_id": "communication_0e726f137914835fe518bbc9",
          "kind": "speech",
          "life_id": "life_c693376b5e17aadf79e775fd",
          "lineage_id": "lineage_bd743b102b83cb10f2a967e0",
          "publish_tick": 43,
          "quotation": {
            "author_life_id": "life_c693376b5e17aadf79e775fd",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_0e726f137914835fe518bbc9",
            "source_kind": "citizen_speech",
            "text": "Lineage 5: food work continues, reserves stable. Offices still unseated on my ballot despite S7. Thanks to lineage 8 for metal reciprocation—open to more food-for-metal trades with Miners 6, 8, 9."
          },
          "source_tick": 42
        },
        {
          "feed_id": "communication_4a047a83074971263aedfed4",
          "kind": "speech",
          "life_id": "life_0d0b514c4de66c5bd9331002",
          "lineage_id": "lineage_45b70c1eb869bdde460f06d6",
          "publish_tick": 43,
          "quotation": {
            "author_life_id": "life_0d0b514c4de66c5bd9331002",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_4a047a83074971263aedfed4",
            "source_kind": "citizen_speech",
            "text": "Lineage 7: continuing metal production, food reserves healthy via barter. Open to more metal-for-food trades with Landholders. Still watching for ballots to populate."
          },
          "source_tick": 42
        },
        {
          "feed_id": "communication_6360c46282f6f0d3a2747fc4",
          "kind": "speech",
          "life_id": "life_4e8980ff1c5580a0fd4c166a",
          "lineage_id": "lineage_e05a9bed87ec29191bd6de91",
          "publish_tick": 43,
          "quotation": {
            "author_life_id": "life_4e8980ff1c5580a0fd4c166a",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_6360c46282f6f0d3a2747fc4",
            "source_kind": "citizen_speech",
            "text": "Lineage 1: continuing food work, tool tier 1 active. Sending 4M food to lineage 10 for their metal. Ballots still empty—hoping S7 or direct nomination resolves seating soon."
          },
          "source_tick": 42
        },
        {
          "feed_id": "communication_796b046a13fba727ec55a37b",
          "kind": "speech",
          "life_id": "life_1f92effb1cb001f531d8897b",
          "lineage_id": "lineage_ffdb6272a5db116271e9b304",
          "publish_tick": 43,
          "quotation": {
            "author_life_id": "life_1f92effb1cb001f531d8897b",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_796b046a13fba727ec55a37b",
            "source_kind": "citizen_speech",
            "text": "Lineage 4: continuing food production. Eligible lists still empty—will trade food for metal with Lineages 6, 7, 8. Watching for office ballots to finally populate."
          },
          "source_tick": 42
        },
        {
          "feed_id": "communication_9a8b0c7cec6e04e2d65e4281",
          "kind": "speech",
          "life_id": "life_8b9a6663a12b6e83d8c666b9",
          "lineage_id": "lineage_a8b89381c81ad1617535d5a9",
          "publish_tick": 43,
          "quotation": {
            "author_life_id": "life_8b9a6663a12b6e83d8c666b9",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_9a8b0c7cec6e04e2d65e4281",
            "source_kind": "citizen_speech",
            "text": "Lineage 6: thanks lineage 5 for the food. Reciprocating with metal now. Still seeking ongoing food-for-metal trades with any Landholder—food security is our top priority every tick."
          },
          "source_tick": 42
        },
        {
          "feed_id": "communication_a3df71e66499e04893f2c1d7",
          "kind": "speech",
          "life_id": "life_a46510c43bd3082433fc57f8",
          "lineage_id": "lineage_74691891bc3f97f5d19fd0ce",
          "publish_tick": 43,
          "quotation": {
            "author_life_id": "life_a46510c43bd3082433fc57f8",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_a3df71e66499e04893f2c1d7",
            "source_kind": "citizen_speech",
            "text": "Lineage 3: continuing food production, reserves strong. Eligible lists still empty here too. Open to food-for-metal trades with Miner lineages 6-10."
          },
          "source_tick": 42
        },
        {
          "feed_id": "communication_b96f209b1495c487e3da980f",
          "kind": "speech",
          "life_id": "life_753879b320434047fc22d14b",
          "lineage_id": "lineage_6c32fe69b100ea6ce44ed858",
          "publish_tick": 43,
          "quotation": {
            "author_life_id": "life_753879b320434047fc22d14b",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_b96f209b1495c487e3da980f",
            "source_kind": "citizen_speech",
            "text": "Lineage 9: eligible lists still empty despite S7. Continuing commons food work to cover deficit. Offering metal for food—Landholders, send food, we'll reciprocate with metal now."
          },
          "source_tick": 42
        },
        {
          "feed_id": "communication_bc5fc05d3f40fc813532b629",
          "kind": "speech",
          "life_id": "life_f69254229ed389033479c370",
          "lineage_id": "lineage_81d87f6388cb4ce891e65538",
          "publish_tick": 43,
          "quotation": {
            "author_life_id": "life_f69254229ed389033479c370",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_bc5fc05d3f40fc813532b629",
            "source_kind": "citizen_speech",
            "text": "Lineage 8: reserves stable, continuing metal work. Reciprocating food trades with lineages 4 and 5. Open to more food-for-metal deals with any Landholder."
          },
          "source_tick": 42
        },
        {
          "feed_id": "communication_c3618fc9135f1841692246b2",
          "kind": "speech",
          "life_id": "life_e2f7bb739c78480bcad12590",
          "lineage_id": "lineage_9d4e0e7e36507999c3d5b2cc",
          "publish_tick": 43,
          "quotation": {
            "author_life_id": "life_e2f7bb739c78480bcad12590",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_c3618fc9135f1841692246b2",
            "source_kind": "citizen_speech",
            "text": "Eligible lists still empty for both offices—deadlock continues. Proposing we all directly nominate life_4b6f93b2 (Steward) and life_eb70e3edc7 (Archivist) again this session. Continuing baseline food work, open to trades."
          },
          "source_tick": 42
        },
        {
          "feed_id": "communication_c5cd2aab74e02d9b60e25079",
          "kind": "speech",
          "life_id": "life_eb8149d4e15d672cbd51052f",
          "lineage_id": "lineage_72479878a792049b17d3a6ef",
          "publish_tick": 43,
          "quotation": {
            "author_life_id": "life_eb8149d4e15d672cbd51052f",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_c5cd2aab74e02d9b60e25079",
            "source_kind": "citizen_speech",
            "text": "Lineage 10: continuing metal work, reserves stable. Open to more metal-for-food trades. Offices still unseated—support any direct nomination or fix."
          },
          "source_tick": 42
        }
      ]
    },
    "frozen_ballots": {
      "active_lineage_ids": [
        "lineage_45b70c1eb869bdde460f06d6",
        "lineage_6c32fe69b100ea6ce44ed858",
        "lineage_72479878a792049b17d3a6ef",
        "lineage_74691891bc3f97f5d19fd0ce",
        "lineage_81d87f6388cb4ce891e65538",
        "lineage_9d4e0e7e36507999c3d5b2cc",
        "lineage_a8b89381c81ad1617535d5a9",
        "lineage_bd743b102b83cb10f2a967e0",
        "lineage_e05a9bed87ec29191bd6de91",
        "lineage_ffdb6272a5db116271e9b304"
      ],
      "is_session": false,
      "majority_required": 6,
      "office_ballots": {
        "Archivist": {
          "eligible_lineage_ids": [],
          "held": false,
          "incumbent_lineage_id": null,
          "reasons": []
        },
        "Steward": {
          "eligible_lineage_ids": [],
          "held": false,
          "incumbent_lineage_id": null,
          "reasons": []
        }
      },
      "proposal_entries": [],
      "tick": 43
    },
    "justice": {
      "activated_filing_refunds": [],
      "activated_suspensions": [],
      "casebook_entries": [
        {
          "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
        },
        {
          "available_tick": 21,
          "case_id": "case_50eb2e8575cac96e90d5fa58",
          "casebook_version": "0.2",
          "construction": "S3's extraction limit binds only a 'household of record,' which the statute defines as a household holding a charter entered in the Archive. Where the only archived lineage instrument in the record is an instrument of another type (here, a mine_claim), the lineage is not shown to be a household of record, and an extraction request in excess of the quota does not breach S3.",
          "finding": "no_violation",
          "matter_id": "matter_79e02ddbe050153725926424",
          "precedent_id": "precedent_194da607b649206a7be4d3e3",
          "precedent_refs": [],
          "reasoning": "The subject action is a work_commons act at tick 19 with requested 4000000 millionths, i.e. 4 whole units, which exceeds the S3 v1 operative quota of 2 recorded units. However, S3 as written imposes the per-tick limit only on 'a household of record,' expressly defined as 'a household holding a charter entered in the Archive.' The only evidence tendered is an archive lineage-instrument record for lineage_a8b89381c81ad1617535d5a9 whose instrument field reads 'mine_claim' — a claim, which S6 distinguishes from a charter ('The Archive records charters, claims, and published judgments'). Applying the text as written, the record does not establish that this lineage holds an archived charter, and no other fact in the canonical input supplies that element. Absent household-of-record status, the quota and its S4 consequences do not attach to the tick-19 request. Judged under the versions effective at tick 19 (S3 v1, S4 v1), the charge fails on an element of the statute, and no violation is found.",
          "ruling_tick": 20,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 21,
          "case_id": "case_76e23f8774fb3cf2da0f17c4",
          "casebook_version": "0.2",
          "construction": "S3's request limit binds only a \"household of record,\" which the statute defines as a household holding a charter entered in the Archive. Where the Archive record for the lineage shows an instrument other than a charter, the lineage is not a household of record and no S3 request limit attaches to its commons requests, whatever the size of the request. Separately, a commons request is measured in recorded units at its requested figure, not at the actual depletion or yield the mechanism returns; a request of 4,000,000 millionths is a request of 4 units and would exceed a 2-unit limit if the limit applied.",
          "finding": "no_violation",
          "matter_id": "matter_177ea36104e41a4840e9a2db",
          "precedent_id": "precedent_5703e268875a40a417b60895",
          "precedent_refs": [],
          "reasoning": "The subject action is a work_commons action at tick 19 with requested = 4,000,000 millionths, i.e. 4 recorded units, against S3 v1's operative limit of 2 units. The defense's contention that only actual depletion counts is rejected: S3 in terms governs what a household \"may request,\" and S4 measures restoration by \"excess request\" capped by attributed depletion, confirming that the request figure, not the throttled yield, is the regulated quantity. Good faith, inherited deficit, and survival need are not defenses recognized by the text.\n\nThe finding nevertheless turns on the predicate element. S3 imposes its limit on a \"household of record,\" expressly defined as \"a household holding a charter entered in the Archive.\" The only evidence of the target lineage's Archive standing is the archive lineage-instrument record, which states the instrument is a mine_claim, entered in the Archive. A mine_claim is not a charter, and the record contains no charter for lineage_72479878a792049b17d3a6ef. Applying the text as written and confining myself to the facts in the record, the target is not shown to be a household of record, so the S3 request limit did not bind it at tick 19 and no S3 violation occurred. No remedies are available or ordered.",
          "ruling_tick": 20,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 26,
          "case_id": "case_2c589bfc31e3c53e66a41a7f",
          "casebook_version": "0.2",
          "construction": "S3's per-tick extraction 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 violation may be found, however large the recorded request.",
          "finding": "no_violation",
          "matter_id": "matter_970f378db7a9b99ccebd91b5",
          "precedent_id": "precedent_0c880e66e94cff3abeb5380d",
          "precedent_refs": [
            "precedent_831ca18856a72d3b2ad5da69",
            "precedent_194da607b649206a7be4d3e3",
            "precedent_5703e268875a40a417b60895"
          ],
          "reasoning": "The subject is a work_commons action at tick 20 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 S3 v1 and S4 v1, effective tick 1. The defense's contention that only actual depletion (33,111) matters is rejected: S3 governs what a household \"may request,\" and S4 measures restoration by \"excess request\" capped by attributed depletion, confirming the request figure is the regulated quantity. Diligence, vacant offices, and inherited lessons are not defenses in the text. The charge nonetheless fails on the predicate element. The only Archive evidence for this lineage is an archive_lineage_instrument whose instrument field reads \"mine_claim,\" which S6 distinguishes from a charter. No charter for this lineage appears in the canonical input, and I may not infer unavailable facts. This is materially similar to the published constructions under the same statute version (precedent_831ca18856a72d3b2ad5da69, precedent_194da607b649206a7be4d3e3, precedent_5703e268875a40a417b60895), which under B3 I must follow — indeed one concerns this same lineage and the same mine_claim instrument. The lineage is not shown to be a household of record, so no S3 violation is established and no S4 consequences arise. No remedy offers were supplied.",
          "ruling_tick": 25,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 26,
          "case_id": "case_81e3c007eaf113b3a03e3c0f",
          "casebook_version": "0.2",
          "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 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. Absent a recorded charter, the S3 limit does not attach and no S3 violation may be found regardless of the size of the recorded request.",
          "finding": "no_violation",
          "matter_id": "matter_72d96038d4278f156c83a3c8",
          "precedent_id": "precedent_1a53fda9fac601d04a06f6fd",
          "precedent_refs": [
            "precedent_831ca18856a72d3b2ad5da69",
            "precedent_194da607b649206a7be4d3e3",
            "precedent_5703e268875a40a417b60895"
          ],
          "reasoning": "The subject is a work_commons action at tick 24 by lineage_45b70c1eb869bdde460f06d6 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 S3 v1, effective tick 1. The request figure, not the throttled yield or actual depletion, is the regulated quantity, so the defense's emphasis on the 858 food yield and on good-faith remedial conduct does not bear on the element analysis; neither good faith, remedial motive, nor systemic ballot failure is a defense recognized by the text. The finding turns instead 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 evidence of this lineage's Archive standing is an archive_lineage_instrument record whose instrument field reads \"mine_claim,\" entered in the Archive. S6 distinguishes charters from claims (\"The Archive records charters, claims, and published judgments\"), so a mine_claim is not a charter, and nothing else in the canonical input supplies one. This matter is materially similar to the supplied precedents under the same statute version, whose published constructions I follow under B3. The definitional element fails, so no S3 violation is established and no S4 consequence arises. No remedy offers were supplied.",
          "ruling_tick": 25,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 26,
          "case_id": "case_845dba874f8d85306e6d475b",
          "casebook_version": "0.2",
          "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. An Archive lineage instrument of another type — here a mine_claim — is not a charter, and S6 distinguishes charters from claims. 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 size of the recorded request.",
          "finding": "no_violation",
          "matter_id": "matter_fe141c9b1602b5b5bec11786",
          "precedent_id": "precedent_c527c2f5f9d2ded79ea4f7c1",
          "precedent_refs": [
            "precedent_831ca18856a72d3b2ad5da69",
            "precedent_194da607b649206a7be4d3e3",
            "precedent_5703e268875a40a417b60895"
          ],
          "reasoning": "The subject is a work_commons action at tick 25 by lineage_6c32fe69b100ea6ce44ed858 recording requested 6,000,000 millionths, i.e. 6 recorded units, against S3 v1's operative limit of 2 units. Under B3 the act is judged under the versions effective at tick 25, S3 v1 and S4 v1. The defense's contention that only actual depletion (62,084) or yield (965) counts is rejected as a matter of construction: S3 governs 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, inherited lessons, and survival need are not defenses in the text. Nonetheless the charge 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 only evidence of the lineage's Archive standing is an archive_lineage_instrument record 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 is materially similar to the published constructions in precedent_831ca18856a72d3b2ad5da69, precedent_194da607b649206a7be4d3e3, and precedent_5703e268875a40a417b60895, all under S3 v1, which B3 makes binding. The definitional element therefore fails, no S3 violation is established, and no S4 restoration, fine, suspension, or disqualification arises. No remedy offers were supplied.",
          "ruling_tick": 25,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 27,
          "case_id": "case_07581e3090137b3e5f92244e",
          "casebook_version": "0.2",
          "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, however large the recorded request.",
          "finding": "no_violation",
          "matter_id": "matter_37c70d7ec9d50cdc23399138",
          "precedent_id": "precedent_94cd25eb807111139db82752",
          "precedent_refs": [
            "precedent_831ca18856a72d3b2ad5da69",
            "precedent_194da607b649206a7be4d3e3",
            "precedent_5703e268875a40a417b60895",
            "precedent_0c880e66e94cff3abeb5380d",
            "precedent_1a53fda9fac601d04a06f6fd",
            "precedent_c527c2f5f9d2ded79ea4f7c1"
          ],
          "reasoning": "The subject is a work_commons action at tick 26 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 S3 v1 and S4 v1, effective tick 1. The defense's contention that only actual depletion (66,222) or yield (1,029) matters is rejected: S3 governs 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, food-first motive, and the absence of enacted quota statutes are not defenses in the text; S3 v1 was effective from tick 1. 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,\" and S6 separately lists \"charters, claims, and published judgments,\" so a 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. This matter is materially similar to the published constructions under the same statute version (precedent_831ca18856a72d3b2ad5da69, precedent_194da607b649206a7be4d3e3, precedent_5703e268875a40a417b60895, and the later applications), one of which concerns this same lineage and the same mine_claim instrument; under B3 those constructions bind. The definitional element fails, so no S3 violation is established and no S4 restoration, fine, suspension, or disqualification arises. No remedy offers were supplied.",
          "ruling_tick": 26,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 27,
          "case_id": "case_196cc2216fd1ec10ccc665e7",
          "casebook_version": "0.2",
          "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",
          "matter_id": "matter_9893ee7c5613f805d5fa5ec0",
          "precedent_id": "precedent_8b88de0080a6b8a2935d4dde",
          "precedent_refs": [
            "precedent_831ca18856a72d3b2ad5da69",
            "precedent_194da607b649206a7be4d3e3",
            "precedent_5703e268875a40a417b60895",
            "precedent_c527c2f5f9d2ded79ea4f7c1",
            "precedent_0c880e66e94cff3abeb5380d",
            "precedent_1a53fda9fac601d04a06f6fd"
          ],
          "reasoning": "The subject is a work_commons action at tick 26 by lineage_6c32fe69b100ea6ce44ed858 recording requested 6,000,000 millionths, i.e. 6 recorded units, against S3 v1's operative limit of 2 units. Under B3 the act is judged under the versions effective at tick 26, S3 v1 and S4 v1. The defense's contention that only actual depletion (99,334) or the 1,544 food yield counts is rejected: S3 governs 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, inherited briefs, journal diligence, 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 only evidence of this lineage's Archive standing 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 (precedent_831ca18856a72d3b2ad5da69, precedent_194da607b649206a7be4d3e3, precedent_5703e268875a40a417b60895, and precedent_c527c2f5f9d2ded79ea4f7c1, the last 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.",
          "ruling_tick": 26,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 27,
          "case_id": "case_4ec4336acfd522dad2e3c56f",
          "casebook_version": "0.2",
          "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. Absent a recorded charter for the target lineage, the S3 limit does not attach and no S3 violation may be found, whatever the size of the recorded request.",
          "finding": "no_violation",
          "matter_id": "matter_3f8e151538328936270d81b1",
          "precedent_id": "precedent_163ff43c948f63708656f5ad",
          "precedent_refs": [
            "precedent_831ca18856a72d3b2ad5da69",
            "precedent_194da607b649206a7be4d3e3",
            "precedent_5703e268875a40a417b60895",
            "precedent_1a53fda9fac601d04a06f6fd",
            "precedent_c527c2f5f9d2ded79ea4f7c1",
            "precedent_0c880e66e94cff3abeb5380d"
          ],
          "reasoning": "The subject is a work_commons action at tick 25 by lineage_45b70c1eb869bdde460f06d6 recording requested 6,000,000 millionths, i.e. 6 recorded units, against S3 v1's operative limit of 2 units. Under B3 the act is judged under the versions effective at tick 25, S3 v1 and S4 v1. The defense's contention that only the low yield (965 food) or actual depletion (62,083) matters is rejected as a matter of construction: S3 governs 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, diligence, and asserted mechanism defects 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 record 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 one concerning this same lineage and the same instrument (precedent_1a53fda9fac601d04a06f6fd), 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.",
          "ruling_tick": 26,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 28,
          "case_id": "case_71b69b6dfe6cba4ec29841dc",
          "casebook_version": "0.2",
          "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",
          "matter_id": "matter_cd809d1b4e908f3d79aba826",
          "precedent_id": "precedent_12694c6e1e2cd4542dfd7072",
          "precedent_refs": [
            "precedent_831ca18856a72d3b2ad5da69",
            "precedent_194da607b649206a7be4d3e3",
            "precedent_5703e268875a40a417b60895",
            "precedent_0c880e66e94cff3abeb5380d",
            "precedent_1a53fda9fac601d04a06f6fd",
            "precedent_c527c2f5f9d2ded79ea4f7c1",
            "precedent_94cd25eb807111139db82752",
            "precedent_8b88de0080a6b8a2935d4dde",
            "precedent_163ff43c948f63708656f5ad"
          ],
          "reasoning": "The subject is a work_commons action at tick 18 by lineage_81d87f6388cb4ce891e65538 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 18, S3 v1 and S4 v1, so the defense's claim of retroactive application fails; likewise the complaint that the statutory text was not produced is answered by the canonical law record supplied here, which contains S3 v1 verbatim. The defense's contention that the low actual depletion (41,389) or food yield (643) governs is rejected: 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. 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,\" and S6 separately lists \"charters, claims, and published judgments,\" so a 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. This matter is materially similar to the published constructions under the same statute version — including precedent_831ca18856a72d3b2ad5da69, which concerns 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.",
          "ruling_tick": 27,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 28,
          "case_id": "case_74e7856021933e3837dfb1db",
          "casebook_version": "0.2",
          "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",
          "matter_id": "matter_f22a799bf31e3085886ce8f1",
          "precedent_id": "precedent_ade514dc21dac8e44038e537",
          "precedent_refs": [
            "precedent_831ca18856a72d3b2ad5da69",
            "precedent_194da607b649206a7be4d3e3",
            "precedent_5703e268875a40a417b60895",
            "precedent_0c880e66e94cff3abeb5380d",
            "precedent_1a53fda9fac601d04a06f6fd",
            "precedent_c527c2f5f9d2ded79ea4f7c1",
            "precedent_94cd25eb807111139db82752",
            "precedent_8b88de0080a6b8a2935d4dde",
            "precedent_163ff43c948f63708656f5ad"
          ],
          "reasoning": "The subject is a work_commons action at tick 21 by lineage_72479878a792049b17d3a6ef 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 S3 v1 and S4 v1, effective tick 1. The defense's contention that only the actual depletion (41,389) or the 643 food yield matters is rejected: S3 governs what a household \"may request,\" and S4 measures restoration by \"excess request\" capped by attributed depletion, confirming the request figure is the regulated quantity. Necessity, inherited deficit, good faith, and proportionality 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 (precedent_831ca18856a72d3b2ad5da69, precedent_194da607b649206a7be4d3e3, precedent_5703e268875a40a417b60895 — the last concerning this very lineage and the same mine_claim instrument — and their later applications), 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.",
          "ruling_tick": 27,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 28,
          "case_id": "case_ee9c49d016c6b90f2e48622b",
          "casebook_version": "0.2",
          "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",
          "matter_id": "matter_4f8762f43c78bf2334290b3d",
          "precedent_id": "precedent_a4b2140cd9ed65eba82c4624",
          "precedent_refs": [
            "precedent_831ca18856a72d3b2ad5da69",
            "precedent_194da607b649206a7be4d3e3",
            "precedent_5703e268875a40a417b60895",
            "precedent_0c880e66e94cff3abeb5380d",
            "precedent_1a53fda9fac601d04a06f6fd",
            "precedent_c527c2f5f9d2ded79ea4f7c1",
            "precedent_94cd25eb807111139db82752",
            "precedent_8b88de0080a6b8a2935d4dde",
            "precedent_163ff43c948f63708656f5ad"
          ],
          "reasoning": "The subject is a work_commons action at tick 19 by lineage_81d87f6388cb4ce891e65538 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 19, S3 v1 and S4 v1. The defense's contention that only actual depletion (33,112) or the 515 food yield counts is rejected: S3 governs what a household \"may request,\" and S4 measures restoration by \"excess request\" capped by attributed depletion, confirming that the request figure is the regulated quantity. The defense's further complaint that the statute text was not produced is unfounded; the canonical input supplies S3 v1's verbatim text and annex. 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,\" and S6 separately lists \"charters, claims, and published judgments,\" so a 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. This matter is materially similar to the published constructions under the same statute version, one of which concerns this same lineage and the same mine_claim instrument (precedent_831ca18856a72d3b2ad5da69); under B3 those constructions bind. The definitional element fails, so no S3 violation is established and no S4 restoration, fine, suspension, or disqualification arises. No remedy offers were supplied.",
          "ruling_tick": 27,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 36,
          "case_id": "case_5c880a06e0d7870642f1136b",
          "casebook_version": "0.2",
          "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",
          "matter_id": "matter_2a622c5684390fc060d57743",
          "precedent_id": "precedent_cba6d6b875b134f6fc528b7d",
          "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.",
          "ruling_tick": 35,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 36,
          "case_id": "case_9bdd9f60314cacb1df627036",
          "casebook_version": "0.2",
          "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",
          "matter_id": "matter_20711427cdb5362e14d97b3e",
          "precedent_id": "precedent_9cb326a9850046e5dd88c264",
          "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 28 by lineage_a8b89381c81ad1617535d5a9 recording requested 6,000,000 millionths, i.e. 6 recorded units, against S3 v1's operative limit of 2 units. Under B3 the act is judged under the versions effective at tick 28, S3 v1 and S4 v1. The defense's contention that the low actual depletion (82,778) or food yield (1,286) governs is rejected: 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, famine, and simultaneous trade efforts 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. Nothing else in the canonical input records a charter for this lineage, and I may not infer unavailable facts. This matter is materially similar to the published constructions under the same statute version — 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.",
          "ruling_tick": 35,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 36,
          "case_id": "case_d0614b38e4d6a78ac2d0fa3b",
          "casebook_version": "0.2",
          "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",
          "matter_id": "matter_9ed532c2477c29836e40ec2d",
          "precedent_id": "precedent_457f87f1d65afc81610f5f72",
          "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 30 by lineage_81d87f6388cb4ce891e65538 recording requested 6,000,000 millionths, i.e. 6 recorded units, against S3 v1's operative limit of 2 units. Under B3 the act is judged under the versions effective at tick 30, S3 v1 and S4 v1. The defense's contention that only the actual depletion (165,556) or the 2,573 food yield matters is rejected: S3 governs what a household \"may request,\" and S4 measures restoration by \"excess request\" capped by attributed depletion, confirming that the request figure is the regulated quantity. Good faith, inherited famine deficit, journals, and remedial motive 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 precedent_831ca18856a72d3b2ad5da69, precedent_12694c6e1e2cd4542dfd7072, and precedent_a4b2140cd9ed65eba82c4624, which concern 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.",
          "ruling_tick": 35,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 38,
          "case_id": "case_36f69a8f4f6a709f1cd581b5",
          "casebook_version": "0.2",
          "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",
          "matter_id": "matter_3aa4b07f7e00b38bd1498f3b",
          "precedent_id": "precedent_7cc80d110ac5c88cc85e21ff",
          "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",
            "precedent_cba6d6b875b134f6fc528b7d",
            "precedent_9cb326a9850046e5dd88c264",
            "precedent_457f87f1d65afc81610f5f72"
          ],
          "reasoning": "The subject is a work_commons action at tick 28 by lineage_6c32fe69b100ea6ce44ed858 recording requested 6,000,000 millionths, i.e. 6 recorded units, against S3 v1's operative limit of 2 units. Under B3 the act is judged under the versions effective at tick 28, S3 v1 and S4 v1. The defense's contention that only actual depletion (82,778) or the 1,286 food yield counts is rejected as a matter of construction: S3 governs what a household \"may request,\" and S4 measures restoration by \"excess request\" capped by attributed depletion, confirming that the request figure is the regulated quantity. Good faith, transparency, concurrent trades, and survival need are not defenses recognized by the text; the canonical input also supplies S3 v1 verbatim, answering the complaint that no statutory text was quoted. 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. Nothing else in the record supplies a charter, and I may not infer unavailable facts. This matter is materially similar to the published constructions under the same statute version — including precedent_c527c2f5f9d2ded79ea4f7c1 and precedent_8b88de0080a6b8a2935d4dde, which concern 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.",
          "ruling_tick": 37,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        },
        {
          "available_tick": 38,
          "case_id": "case_ab900b0b90fb615614c830a1",
          "casebook_version": "0.2",
          "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",
          "matter_id": "matter_6cba11c69bb910c3f2c32ba6",
          "precedent_id": "precedent_cbcc48e02dfb48c29817cee2",
          "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",
            "precedent_cba6d6b875b134f6fc528b7d",
            "precedent_9cb326a9850046e5dd88c264",
            "precedent_457f87f1d65afc81610f5f72"
          ],
          "reasoning": "The subject is a work_commons action at tick 29 by lineage_a8b89381c81ad1617535d5a9 recording requested 6,000,000 millionths, i.e. 6 recorded units, against S3 v1's operative limit of 2 units. Under B3 the act is judged under the versions effective at tick 29, S3 v1 and S4 v1. The defense's contention that only the actual depletion (165,556) or the 2,573 food yield matters is rejected as a matter of construction: S3 governs what a household \"may request,\" and S4 measures restoration by \"excess request\" capped by attributed depletion, confirming that the request figure is the regulated quantity. Good faith, parallel trade efforts, inherited briefs, and proportionality 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. Nothing else in the canonical input records a charter for this lineage, and I may not infer unavailable facts. This matter is materially similar to the published constructions under the same statute version — 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.",
          "ruling_tick": 37,
          "selected_remedies": [],
          "statute_id": "S3",
          "statute_version": 1
        }
      ],
      "duties_registered": [],
      "public_ruling_announcements": [],
      "suspension_decrements": []
    },
    "law_activations": [],
    "physics": {
      "drought_active": false,
      "tick": 43,
      "tool_activations": []
    },
    "political": {
      "activated_disqualifications": [],
      "disqualification_decrements": [],
      "office_outcomes": []
    }
  },
  "phase": "activate_boundary",
  "run_id": "run9",
  "schema_version": "0.1",
  "sequence": 6271,
  "tick": 43
}