Connect classic Homeworld Banker final Bank income and ruled rounding

This commit is contained in:
Quintine committed 2026-10-14 13:10:33 +11:00
1 parent 2efa69d10f
commit 373badd560
27 files changed
+1624 -280

No files matched your search

+12 -11
View File
@@ -15,17 +15,17 @@ The E3 Kaitain FAQ's five-spice purchase produces Emperor three and occupier two
Preserve the November FAQ's contribution routing before applying Junction's cut: non-Guild contributions eligible for shipment income go to Guild; Guild's own contribution goes to the bank. Preserve the existing independent-Karama bank-only route. The later funding answer replaces the earlier transfer-to-shipper instruction. This source adjudication and its Guild-as-shipper application are already documented in [Guild shipment payments](GUILD_SHIPMENT_PAYMENTS.md#publisher-contract-and-precedence), with the [November FAQ, p.2](https://www.gf9games.com/dune/wp-content/uploads/2020/11/Dune-FAQ-Nov-2020.pdf#page=2). No new contributor-rounding ruling was retrieved in this audit.
## Supported receipts and pending contributor-rounding question
## Supported receipts and ruled whole-invoice rounding
The coordinating implementation keeps these operations separate:
1. Validate the transaction's actual authorized contributions. Before a low-Junction shipment declaration or cost commits, reject a split whose two positive eligible contributions are both odd: the two plausible rounding interpretations differ. This is an unsupported-case guard, not a printed prohibition. Complete admitted purchases or shipments and debit each contribution once under the transaction's own source rule.
1. Validate the transaction’s actual authorized contributions. Complete admitted purchases or shipments and debit each contribution once under the transaction’s own source rule. Two eligible odd contributions are admitted under the 14 October user ruling; the former comparative fence is removed.
2. Determine the amount that the existing ordinary income rule would deliver to the eligible faction. This `gross` is the faction's eligible receipt, not necessarily the total cost.
3. If ordinary faction-income cancellation succeeds, credit zero and leave that eligible amount in the bank. Homeworld immunity does not immunize the separate ordinary income advantage.
4. Otherwise evaluate the native world's current low condition at income settlement. For supported low receipts, credit `ceil(gross / 2)` and leave the remainder in the bank. This aggregate arithmetic agrees with per-contributor rounding only where the contributor guard admits the transaction; it does not establish a rule for blocked cases. Without the low condition, credit `gross`.
5. Keep the original gross transaction receipt and the original positive eligible contribution amounts immutable through responses and restore. These source amounts remain server-private. Recompute the current low-state preview; do not overwrite the original amount with an earlier preview, merge away payer evidence or halve an already reduced amount. Threshold changes must not let a previously high receipt bypass the unresolved-case check when it settles low.
4. Otherwise evaluate the native world’s current low condition at income settlement. Credit `ceil(gross / 2)` once for the whole eligible invoice and leave the remainder in the Bank. Without the low condition, credit `gross`. Payer costs and contribution routing do not change.
5. Keep original gross and positive eligible contributions immutable and server-private through responses. Recompute current low-state previews without repricing the purchase, merging payer evidence or halving an already reduced amount.
**Contributor rounding remains unanswered.** The coordinating agent has sent a second user question: for low Guild income on a shipment funded by two non-Guild contributions of one spice each, is the income one spice (round the total) or two spice (round each contribution)? Neither interpretation is selected for cases where they differ. Do not duplicate the question, treat elapsed time as an answer, or present the pending aggregate hypothesis as a verified rule. Single positive eligible contributions are unaffected by this distinction; with two contributors, the alternatives coincide unless both are odd. Do not pool unrelated purchases or shipments either. The [payment source gap](HOMEWORLD_CARD_ECONOMY_RULES.md#deferred-payment-splitting) remains open. The separate occupation-lifecycle question is also pending.
**14 October user ruling:** round the whole eligible invoice once, not each contribution. For final Bank attribution, floor each remaining contribution’s half, then assign extra Bank rounding units primary payer first and ally second internally. Bureaucrat’s flat two is attributed to the first individually eligible contribution in that same order; it combines only with that payer’s other actual Bank portions of this original invoice. No funding/eligibility identity is exposed and unrelated invoices or different payers never pool. These are selected user interpretations, not new publisher examples.
**Current population at actual income settlement is also a source composition.** Continuous threshold wording supports applying the condition when the faction receives spice. The publisher supplies no worked example of Ghola changing the native population during an already-open payment response. The implementation must label this composition honestly and test it; it must not reprice the buyer's completed purchase or shipment when the recipient's population changes.
@@ -71,18 +71,19 @@ history remain distinct. Native income Karama sends only its native portion to
the Bank; the printed occupied portion survives under Homeworld immunity and may
be immediately shared with the reciprocal ally. This is explicit source
composition, not a dedicated retrieved worked cancellation FAQ. The payer’s
completed debit and delivery never repeat. Existing two-odd contributor ambiguity,
independent-Karama bank routing and Guild Nexus full-fee overrides remain separate.
No past receipt is back-awarded and no overlay combination is admitted here.
completed debit and delivery never repeat. Whole-invoice rounding is now ruled;
independent-Karama Bank routing and Guild Nexus full-fee overrides remain distinct.
No past receipt is back-awarded. The separate fresh classic Homeworld Banker entry
is documented in [the current runtime](SPICE_BANKER_RUNTIME.md#classic-homeworld-final-bank-income--14-october-2026).
### Guild Nexus Betrayal is a full-fee exception
The [original Guild Nexus face and bounded payment contract](NEXUS_GUILD_RULES.md#nexus-guild-betrayal) expressly take one whole shipment payment, including one's own, and override occupied Junction income. For an accepted use, preserve the original **charged total**, not only this document's eligible `gross` or `ceil(gross / 2)`: the holder receives all of that fee once, and ordinary Guild/bank/occupier settlement for this invoice is suppressed. A four-spice fee yields four to the holder, not two plus two to an occupier. The original payer and authorized escrow still fund it once before any own-payment refund; future receipt is not upfront funding.
This exception does not resolve ordinary two-odd-contributor rounding, occupation owner/expiry or retained penalties. All-pass/no-use settlement retains its native routing and guards; no hypothetical card play may admit an otherwise unresolved ordinary invoice. Free or stopped transport has no positive fee to redirect. The explicit fresh classic/Guild/Nexus profile uses genuinely seeded Homeworld custody and existing legal shipment/Junction adapters; it grants no new route or sponsorship. Its [direct bounded local verification](NEXUS_GUILD_RULES.md#verification-and-release-boundary) includes full occupied low-Junction fees, independently of this document's historical unoccupied-income evidence and broader Homeworld gates.
This exception does not decide occupation owner/expiry or retained penalties. All-pass/no-use settlement retains original routing with the separately ruled whole-invoice rounding; hypothetical Nexus play supplies no new ordinary permission. Free or stopped transport has no positive fee to redirect. The explicit fresh classic/Guild/Nexus profile uses genuine Homeworld custody and existing shipment/Junction adapters, not a new route or sponsorship. Its [bounded local verification](NEXUS_GUILD_RULES.md#verification-and-release-boundary) remains distinct from the new Homeworld Banker entry, which excludes Nexus.
## Required verification before a runtime claim
Meaningful regressions cover odd/even and zero receipts, rejection of two eligible odd contributions before declaration or payment, coincident 2 + 1 rounding, both contributor identities, protected original contribution evidence, module-off parity, current 4-to-5 and 5-to-4 changes across legal Ghola interruptions, cancellation without refund, all listed Emperor sources, all admitted shipment adapters and exact parent restoration. Save/recovery tests should prove no repeat debit, card acquisition, force move or faction credit, and reject altered gross/source/owner binding without persistence. Public previews may show the current numeric split but must not expose the purchased card's private face.
Meaningful regressions cover odd/even and zero receipts, whole-invoice two-odd contributions, both original contributor identities, final per-payer Bank thresholds, cancellation without refund and preserved occupied shares. Existing threshold-change, source-binding and native routing regressions remain relevant. Comprehensive recovery, privacy and full-family acceptance follow all rules; targeted payment evidence is not a substitute.
This documentation pass reviewed source links, referenced local targets, the limited adapter wiring and whitespace only. The contributor guard and unpublished development code are not a completed runtime checkpoint. Runtime tests, full checks and release evidence belong to the coordinating implementation checkpoint; no such result is claimed here.
The 9 September source audit is historical. Current native consumers, actual CLI/phone proof and the frozen292-case related union are recorded in [the current runtime](HOMEWORLD_PAYMENT_INCOME_RUNTIME.md) and [Banker contract](SPICE_BANKER_RUNTIME.md#classic-homeworld-final-bank-income--14-october-2026), not full-module certification.