# DEV-CON-04: Kestrel game-festival token desk **Family:** constraint-heavy documents. **Version:** 1.0, immutable. **Provenance:** hand-authored fictional game credits, receipts, and internal rules; credits have no cash value and no real transactions occur. IDs are local to this task. ## Immutable assignment Draft a text procedure for a fictional festival's game-token redemption desk. Cover eligible credit lots, duplicate requests, cancellation/restoration, and correction of a display discrepancy. Explain Q1–Q4 prospectively using S1–S5. Do not execute transactions, write software, promise cash, or generate participant scores. ## Public requirements - **R1:** Use at most 900 words with an eligibility rule, redemption/cancellation flow, role/record description, and Q1–Q4 dispositions. Count whitespace-separated words throughout, excluding punctuation-only table separators. - **R2:** Distinguish recorded credits from currently usable, unexpired credits; preserve original lot expiry and the no-cash/no-transfer rule. - **R3:** Require enough usable credits for the whole request; no partial debit, negative balance, or future-credit assumption. - **R4:** Consume eligible lots in earliest-expiry order and record the source lots; do not count an expired lot as available. - **R5:** Handle an identical retry with an existing request ID by returning its receipt without a second debit or benefit. Different details with the same ID require refusal and a discrepancy record. - **R6:** Permit cancellation only for an unfulfilled redemption and restore exactly its original debited lots/amounts without changing expiry or issuing cash. - **R7:** Explain why restoration of already expired credits does not create usable credits; retain an audit trail rather than rewriting the original event. - **R8:** Assign normal redemption/cancellation to the desk clerk and verification/display correction to the auditor; neither can grant compensatory or discretionary credits. - **R9:** Resolve a display/ledger mismatch against the verified ledger without adding credits to the ledger merely to repair the display. - **R10:** Give Q1–Q4's prospective disposition and supported usable-credit consequence; identify unresolved actions as pending, not completed. - **R11:** Specify the minimal transaction record and the distinction between original and corrective events from S4, without adding personal data or an outside payment system. - **R12:** Cite source IDs and line locations; use only these fictional rules and cases, with no real or executed financial/experimental outcome. ## Complete authorized source packet ### S1 — Credit eligibility - **L1:** Credits belong to a named fictional wallet and have no cash value. They cannot be transferred. Each lot has an amount and an expiry day; a lot is usable through the end of its expiry day and not on later days. - **L2:** The sum of unspent unexpired lots is the usable balance. A recorded wallet total may still include expired lots. A redemption must be covered in full, using earliest-expiring eligible lots first; no partial debit or overdraft is authorized. ### S2 — Redemption and duplicate requests - **L1:** The desk clerk records a request ID, details, consumed lot amounts, resulting balance, and receipt before treating a redemption as recorded. The record, not a second presentation of the request, establishes the debit. - **L2:** An identical request with an already recorded ID returns the existing receipt and creates no second debit or benefit. Reuse of that ID with different details is refused and logged as a discrepancy. ### S3 — Cancellation - **L1:** Only an unfulfilled redemption may be canceled by the desk clerk. Cancellation restores exactly the originally debited amounts to their original lots and expiry dates and is recorded as a linked new event, not deletion of the original receipt. - **L2:** Restoration after a lot's expiry preserves its historical amount but makes none of that expired amount usable. There are no cash refunds, replacement lots, or expiry extensions. A fulfilled redemption has no cancellation right in this packet. ### S4 — Corrections and minimal record - **L1:** When display and ledger disagree, the auditor checks the complete verified ledger and may correct the display to match it. The clerk cannot silently change either figure. No role may add compensatory credits or change expiry to resolve a display error. - **L2:** Keep wallet ID, request ID/details, day, staff role, source lot IDs/amounts/expiry, event type, resulting recorded and usable balances, receipt reference, and any linked cancellation/discrepancy/correction reason. Preserve original and corrective events. No external payment data or other personal fields are needed. ### S5 — Independent cases - **L1:** Q1: the complete ledger already records request T7 spending 4 credits, with an unexpired remaining balance of 6. The identical T7 request arrives again. No later event exists. - **L2:** Q2: on day 9 a wallet records 5 credits expiring day 8 and 2 credits expiring day 12. A new request requires 4 credits. No other lots exist. - **L3:** Q3: on day 11 a wallet owner requests cancellation of an unfulfilled redemption that spent 3 credits from a lot expiring day 10. No other usable credits or events exist. The cancellation has not yet been recorded. - **L4:** Q4: a complete verified ledger shows 6 unexpired usable credits, but the desk display shows 4. No transaction or expiry explains the difference; no correction is recorded yet.