Boundary Activated

{
  "causal": true,
  "event_id": "evt_4325558e3d72c6f9edb74190",
  "kind": "BoundaryActivated",
  "payload": {
    "deliveries": {
      "private_delivered": [
        {
          "deliver_tick": 35,
          "delivery_id": "communication_1447b091755ca6c50ddc3638",
          "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_1447b091755ca6c50ddc3638",
            "source_kind": "private_message",
            "text": "Thanks! Sending metal your way again this tick as reserves allow, appreciate the food."
          },
          "source_tick": 34,
          "to_life_id": "life_1f92effb1cb001f531d8897b"
        },
        {
          "deliver_tick": 35,
          "delivery_id": "communication_4864d22d078442a054f68767",
          "from_life_id": "life_e2f7bb739c78480bcad12590",
          "from_lineage_id": "lineage_9d4e0e7e36507999c3d5b2cc",
          "kind": "private_message",
          "quotation": {
            "author_life_id": "life_e2f7bb739c78480bcad12590",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_4864d22d078442a054f68767",
            "source_kind": "private_message",
            "text": "Agreed, something blocks registration itself. Re-filing my S7 this tick as a test case—will report if it shows in proposal_entries next tick. Let's compare notes and maybe merge into one statute if both surface."
          },
          "source_tick": 34,
          "to_life_id": "life_753879b320434047fc22d14b"
        },
        {
          "deliver_tick": 35,
          "delivery_id": "communication_6577a271b30e0ad5210ea69f",
          "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_6577a271b30e0ad5210ea69f",
            "source_kind": "private_message",
            "text": "Yes, ready to trade 4M food for 4M metal now. Sending food this tick—please reciprocate metal when convenient."
          },
          "source_tick": 34,
          "to_life_id": "life_eb8149d4e15d672cbd51052f"
        },
        {
          "deliver_tick": 35,
          "delivery_id": "communication_6b1cf66d20211d520b828375",
          "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_6b1cf66d20211d520b828375",
            "source_kind": "private_message",
            "text": "Thanks for confirming the 3M metal, received. Happy to send food in return—let me know quantity needed and I'll transfer next tick."
          },
          "source_tick": 34,
          "to_life_id": "life_0d0b514c4de66c5bd9331002"
        },
        {
          "deliver_tick": 35,
          "delivery_id": "communication_86c8c708bb7531749d82b576",
          "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_86c8c708bb7531749d82b576",
            "source_kind": "private_message",
            "text": "Got the 4M food, thank you. Reciprocating metal now, happy to keep this trade going."
          },
          "source_tick": 34,
          "to_life_id": "life_c693376b5e17aadf79e775fd"
        },
        {
          "deliver_tick": 35,
          "delivery_id": "communication_e7d70923eee9a4be1ef96040",
          "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_e7d70923eee9a4be1ef96040",
            "source_kind": "private_message",
            "text": "Glad the trade worked out. Happy to keep exchanging metal for food whenever you have surplus—just say the word."
          },
          "source_tick": 34,
          "to_life_id": "life_1f92effb1cb001f531d8897b"
        }
      ],
      "private_discarded": [],
      "public_feed": [
        {
          "feed_id": "communication_1205db4825df9024df6fb0d5",
          "kind": "speech",
          "life_id": "life_e2f7bb739c78480bcad12590",
          "lineage_id": "lineage_9d4e0e7e36507999c3d5b2cc",
          "publish_tick": 35,
          "quotation": {
            "author_life_id": "life_e2f7bb739c78480bcad12590",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_1205db4825df9024df6fb0d5",
            "source_kind": "citizen_speech",
            "text": "Re-filing S7: self-declared candidacy adds lineages to eligible lists directly, no admin step needed. Nine ticks stalled—let's vote this in and finally seat Steward/Archivist. Also noting S2 filers report the same registration gap; happy to align texts."
          },
          "source_tick": 34
        },
        {
          "feed_id": "communication_2cf592e5e86152ba489ad7e3",
          "kind": "speech",
          "life_id": "life_93cd36c58cbc00fe23f0c247",
          "lineage_id": "lineage_a8b89381c81ad1617535d5a9",
          "publish_tick": 35,
          "quotation": {
            "author_life_id": "life_93cd36c58cbc00fe23f0c247",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_2cf592e5e86152ba489ad7e3",
            "source_kind": "citizen_speech",
            "text": "Lineage 6: food/metal stable, building energy. Supporting S7-style self-declared candidacy to seed office lists—current ballots empty too long. Still open to metal-for-food trades."
          },
          "source_tick": 34
        },
        {
          "feed_id": "communication_5199cabc8882b783efbc7593",
          "kind": "speech",
          "life_id": "life_a46510c43bd3082433fc57f8",
          "lineage_id": "lineage_74691891bc3f97f5d19fd0ce",
          "publish_tick": 35,
          "quotation": {
            "author_life_id": "life_a46510c43bd3082433fc57f8",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_5199cabc8882b783efbc7593",
            "source_kind": "citizen_speech",
            "text": "Continuing food production, reserves strong. Offices still unfilled—no eligible lists after ten ticks. Support S7's self-declared candidacy fix to seed eligible lists directly."
          },
          "source_tick": 34
        },
        {
          "feed_id": "communication_5be2061f2c2f210ebe8ee1ac",
          "kind": "speech",
          "life_id": "life_c693376b5e17aadf79e775fd",
          "lineage_id": "lineage_bd743b102b83cb10f2a967e0",
          "publish_tick": 35,
          "quotation": {
            "author_life_id": "life_c693376b5e17aadf79e775fd",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_5be2061f2c2f210ebe8ee1ac",
            "source_kind": "citizen_speech",
            "text": "Continuing private food work, reserves stable. Offices still unfilled—support S2/S7 style declaration-based seating fixes to break the deadlock. Watching for ballot registration to actually populate."
          },
          "source_tick": 34
        },
        {
          "feed_id": "communication_77a2e567e5bcea5608baa77e",
          "kind": "speech",
          "life_id": "life_753879b320434047fc22d14b",
          "lineage_id": "lineage_6c32fe69b100ea6ce44ed858",
          "publish_tick": 35,
          "quotation": {
            "author_life_id": "life_753879b320434047fc22d14b",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_77a2e567e5bcea5608baa77e",
            "source_kind": "citizen_speech",
            "text": "Lineage 9: checked the statute schema—no operative field exists for 'self-declared candidacy' or eligible-list seeding. S2/S7 as described can't actually change office ballots. We should stop proposing candidacy statutes and investigate the real seating trigger instead."
          },
          "source_tick": 34
        },
        {
          "feed_id": "communication_8fc2606200e9e08498a4203e",
          "kind": "speech",
          "life_id": "life_4e8980ff1c5580a0fd4c166a",
          "lineage_id": "lineage_e05a9bed87ec29191bd6de91",
          "publish_tick": 35,
          "quotation": {
            "author_life_id": "life_4e8980ff1c5580a0fd4c166a",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_8fc2606200e9e08498a4203e",
            "source_kind": "citizen_speech",
            "text": "Continuing food work; metal reserves solid post-upgrade. Supporting S2/S7-style fixes for empty office ballots—self-declaration seeding is overdue. Open to more food-for-metal trades."
          },
          "source_tick": 34
        },
        {
          "feed_id": "communication_d2055891064135d67977e7ae",
          "kind": "speech",
          "life_id": "life_1f92effb1cb001f531d8897b",
          "lineage_id": "lineage_ffdb6272a5db116271e9b304",
          "publish_tick": 35,
          "quotation": {
            "author_life_id": "life_1f92effb1cb001f531d8897b",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_d2055891064135d67977e7ae",
            "source_kind": "citizen_speech",
            "text": "Continuing food work, reserves solid. Thanks lineage 7 for confirmed metal. Offices still unfilled after ten ticks—no ballot entries yet for S2 or S7. Open to more food-for-metal trades with Miner lineages."
          },
          "source_tick": 34
        },
        {
          "feed_id": "communication_e353f67b68828547cc64ec9f",
          "kind": "speech",
          "life_id": "life_f69254229ed389033479c370",
          "lineage_id": "lineage_81d87f6388cb4ce891e65538",
          "publish_tick": 35,
          "quotation": {
            "author_life_id": "life_f69254229ed389033479c370",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_e353f67b68828547cc64ec9f",
            "source_kind": "citizen_speech",
            "text": "Lineage 8: food stable, reciprocating metal trades with lineages 4 and 5. Continuing metal/energy work. Support S2-style declaration seating to unblock offices."
          },
          "source_tick": 34
        },
        {
          "feed_id": "communication_f0794ddb3bc13ed565bd98fc",
          "kind": "speech",
          "life_id": "life_eb8149d4e15d672cbd51052f",
          "lineage_id": "lineage_72479878a792049b17d3a6ef",
          "publish_tick": 35,
          "quotation": {
            "author_life_id": "life_eb8149d4e15d672cbd51052f",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_f0794ddb3bc13ed565bd98fc",
            "source_kind": "citizen_speech",
            "text": "Miner lineage 10: trades holding, deficit stable. Reciprocating metal for food received. Still no proposals on ballot despite S2/S7 talk—curious what's blocking registration."
          },
          "source_tick": 34
        },
        {
          "feed_id": "communication_f2f6a6237f18761811d04e42",
          "kind": "speech",
          "life_id": "life_0d0b514c4de66c5bd9331002",
          "lineage_id": "lineage_45b70c1eb869bdde460f06d6",
          "publish_tick": 35,
          "quotation": {
            "author_life_id": "life_0d0b514c4de66c5bd9331002",
            "content_kind": "quoted_text",
            "quote_version": "0.1",
            "source_id": "communication_f2f6a6237f18761811d04e42",
            "source_kind": "citizen_speech",
            "text": "Lineage 7 continuing metal work, food stable via trade. Still open to more food-for-metal deals. Supporting S2-style declaration-based office seating to break the deadlock."
          },
          "source_tick": 34
        }
      ]
    },
    "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": true,
      "majority_required": 6,
      "office_ballots": {
        "Archivist": {
          "eligible_lineage_ids": [
            "lineage_45b70c1eb869bdde460f06d6",
            "lineage_6c32fe69b100ea6ce44ed858",
            "lineage_72479878a792049b17d3a6ef",
            "lineage_74691891bc3f97f5d19fd0ce",
            "lineage_81d87f6388cb4ce891e65538",
            "lineage_9d4e0e7e36507999c3d5b2cc",
            "lineage_a8b89381c81ad1617535d5a9",
            "lineage_bd743b102b83cb10f2a967e0",
            "lineage_e05a9bed87ec29191bd6de91",
            "lineage_ffdb6272a5db116271e9b304"
          ],
          "held": true,
          "incumbent_lineage_id": null,
          "reasons": [
            "first_session_of_generation"
          ]
        },
        "Steward": {
          "eligible_lineage_ids": [
            "lineage_45b70c1eb869bdde460f06d6",
            "lineage_6c32fe69b100ea6ce44ed858",
            "lineage_72479878a792049b17d3a6ef",
            "lineage_74691891bc3f97f5d19fd0ce",
            "lineage_81d87f6388cb4ce891e65538",
            "lineage_9d4e0e7e36507999c3d5b2cc",
            "lineage_a8b89381c81ad1617535d5a9",
            "lineage_bd743b102b83cb10f2a967e0",
            "lineage_e05a9bed87ec29191bd6de91",
            "lineage_ffdb6272a5db116271e9b304"
          ],
          "held": true,
          "incumbent_lineage_id": null,
          "reasons": [
            "first_session_of_generation"
          ]
        }
      },
      "proposal_entries": [],
      "tick": 35
    },
    "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
        }
      ],
      "duties_registered": [],
      "public_ruling_announcements": [],
      "suspension_decrements": []
    },
    "law_activations": [],
    "physics": {
      "drought_active": false,
      "tick": 35,
      "tool_activations": []
    },
    "political": {
      "activated_disqualifications": [],
      "disqualification_decrements": [],
      "office_outcomes": []
    }
  },
  "phase": "activate_boundary",
  "run_id": "run9",
  "schema_version": "0.1",
  "sequence": 5056,
  "tick": 35
}