Check whether clean linen lasts until the next return batch

TASK
Build a chronological projected ledger for clean, dirty, in-laundry and in-use pieces. Include opening and each complete event, preserve the tracked total, and separate shortages from unmet demand. When a requested issue fails, apply the supplied no-partial-issue rule without negative stock or invented fulfillment. Show the earliest shortfall and a conditional owner question.

INPUT
Complete fictional single-linen-type model, individual pieces, no losses. Use tokens only. Monday is 2026-10-19 and Tuesday is 2026-10-20; one shared local clock. Opening Monday 09:00: 12 clean, 4 dirty, 0 in laundry and 8 in use. The eight in-use pieces make the full tracked pool explicit: total 24.
Monday 10:00: issue 8 clean pieces to use, and receive the previous 8 in-use pieces as dirty replacements. Treat these as one combined scheduled event.
Monday 12:00: send all 12 dirty pieces to laundry.
Tuesday 09:00: proposed demand for 6 clean pieces. No partial issue is approved: if clean stock is insufficient, issue none and retain the unmet request separately.
Tuesday 14:00: confirmed-in-this-fiction return of 12 pieces from laundry as clean. Do not automatically fulfill the earlier held request on return.
No purchases, substitutions, earlier return, later dirty receipt, losses or other events exist in this fixture. Build the five-row state ledger including opening and show conservation. Scheduled fiction is not an assertion that real events occurred; no hygiene, staffing or service promise.
END INPUT

Check the answer in this sample chat against the complete INPUT above. Add the four stock states in every row: 24 each time. The opening eight in-use pieces are included. Before Tuesday’s 14:00 return, only four clean pieces exist: shortage 2 against demand 6. Issue zero under the no-partial rule, so unmet demand is 6. After return, clean is 16; the held request is not silently marked fulfilled. No stock cell goes negative. Quote each mismatch and its source, then return a complete corrected replacement. If source or answer is missing, ask for it. Do not describe a suggested human trial as completed.

Project my synthetic reusable-linen ledger by exact item type and chronological event. Require a complete opening balance across clean, dirty, in laundry and in use, or explicitly identify an open system with source/sink movements. Apply only supplied issues, dirty receipts, dispatches and returns at their stated times. Separate confirmed model events from uncertain returns. Test proposed demand against clean supply before subtracting; apply my partial-issue rule and record unmet demand separately, never negative physical stock. Show per-event conservation, earliest shortage and owner decisions needed. Recalculate each balance and event order using my counts and dates. Do not claim real issues, availability, purchases, hygiene adequacy or permission to fulfill held demand.

MY INPUT
Item types and opening counts per state: [replace with your source or rule]
Confirmed timed issues and dirty returns: [replace with your source or rule]
Laundry dispatch and return batches: [replace with your source or rule]
Event order: [replace with your source or rule]
Loss/shortfall handling rule: [replace with your source or rule]

Use only MY INPUT for facts, quantities, names, dates and permissions. Ask for missing essential facts or conflicting rules instead of guessing. Creative invention is allowed only where this task and my boundaries permit it. Return the actual complete requested result, a separate unknown/hold list and the source-specific review described above. Do not reuse practice-example facts. Keep this a draft; do not publish, contact people, book, buy or change another service.