A park can have three businesses and one delivery system. The design question is who gets the shared stock when every operation wants it. In Starling Pier, one Spark warehouse feeds the Lantern Wheel, Tea Cart, and Photo Booth through a single junction. Every unit is counted once, so an allocation to one business is unavailable to the others.
Starling Pier is a fictional three-day management scenario. Each morning brings three Spark, with one unused unit allowed to carry to the next day. The Wheel needs two to open; the Tea Cart and Photo Booth need one each. Visitors prefer excitement, comfort, or memory on different days. Matching an open business to the featured preference earns more park mood, so supply planning and guest flow share one decision.

Draw the businesses into one network
Connect one central warehouse to a junction and three business branches. The network receives three Spark at dawn; each branch can carry at most two per day. The Lantern Wheel costs two Spark to open, while Tea Cart and Photo Booth cost one each. Each open business earns two park-mood points when it matches the day's featured visitor preference, or one point when it does not. A closed business earns none. After the day's allocation, unused Spark carries forward up to a cap of one; excess expires. Use one shared ledger and subtract each allocation immediately so the same stock cannot be promised twice.
| Business or condition | Spark cost and result |
|---|---|
| Lantern Wheel | Costs 2 Spark; excitement preference earns 2 mood, other preferences earn 1. |
| Tea Cart | Costs 1 Spark; comfort preference earns 2 mood, other preferences earn 1. |
| Photo Booth | Costs 1 Spark; memory preference earns 2 mood, other preferences earn 1. |
| Daily delivery | Add 3 Spark to the central balance. Branch capacity is 2 Spark per day. |
| Carryover | Keep at most 1 unused Spark for the next morning; discard any excess. |
| Shared ledger | Deduct stock once at allocation. If an allocation exceeds available Spark, reject it without changing stock. |

Track every Spark in a shared ledger
Start with no carryover. Day 1 features excitement: allocate two Spark to the Wheel and one to Tea. Mood rises by 3; Photo Booth closes and stock ends at zero. Day 2 brings three more Spark and features comfort: open Tea and Photo Booth for two total, earning 3 mood; carry one unused Spark. Day 3 begins with that one plus three delivered Spark and features memory. Allocate one to Photo Booth and two to the Wheel, earning 3 mood. The three-day total is 9. As a counterexample, assigning each business a private copy of the central balance could promise four Spark from only three; the shared ledger rejects that over-allocation.
| Check | Expected result |
|---|---|
| Day 1: Wheel 2 + Tea 1 | Available 3, allocated 3, mood +3, carry 0. |
| Day 2: Tea 1 + Photo Booth 1 | Available 3, allocated 2, mood +3, carry 1. |
| Day 3: Photo Booth 1 + Wheel 2 | Available 4 including carry, allocated 3, mood +3, carry 1. |
| Allocate 3 to the Wheel on day 1 | Reject: the Wheel branch is capped at 2 Spark. Stock and mood stay unchanged. |
| Promise the same Spark to two businesses | Reject the second allocation when the shared balance is exhausted. |
| Reset | Restore day 1, zero carry, central stock and the original preference sequence. |
Match allocation to visitor demand
Ask SEELE for a small local management prototype with one warehouse balance, a junction, three businesses, and a three-day demand sequence. Require an allocation ledger that shows deliveries, costs, branch capacity, mood, and carryover. Compare each day's totals with the written trace before adding staff or new suppliers.
Create a local theme-park management prototype called Starling Pier. One central warehouse receives 3 Spark each dawn and may carry at most 1 unused Spark to the next day. Connect the warehouse through one junction to Lantern Wheel, Tea Cart, and Photo Booth. Wheel costs 2 Spark to open, Tea costs 1, Photo Booth costs 1. Each branch can carry at most 2 Spark per day. A single shared balance must deduct each allocation once and reject any over-allocation. Featured visitor preferences by day are excitement, comfort, memory. A matching open business earns 2 park-mood points; another open business earns 1; a closed business earns 0. End of day: carry at most 1 unused Spark and discard the rest. Day 1 allocate Wheel 2 and Tea 1. Day 2 allocate Tea 1 and Photo Booth 1. Day 3 allocate Photo Booth 1 and Wheel 2, using the carried Spark. Show stock before and after every allocation, open businesses, preference, mood, and carryover. Add a deterministic reset. Make allocation and reset keyboard-operable without timed key presses.
Give AI the network and day order
The first draft displayed three separate business stock counters initialized from the same warehouse balance. That made it possible to promise the same Spark more than once. Replace them with one central balance and a transaction log. An accepted allocation deducts stock once; a rejected request changes neither inventory nor mood.
Replay all three days and verify the carry cap, per-branch limit, preference match, and stock after each delivery. Try a duplicate allocation and an over-cap branch request. Confirm reset restores the day, preference order, stock, and open/closed state. W3C keyboard guidance is a reference for operating the allocation controls, not a conformance claim.

Expand operations after the stock trace works
Keep one delivery type and three businesses while testing the shared ledger. Players should be able to explain which operation received each unit and why the preference changed the value of that choice. Once the three-day trace is stable, add a second delivery route or a new business and update the stock table before expanding the park.
Read the theme-park management guide.
Start a local park prototype with SEELE.
Frequently asked questions
Why use one shared stock balance?
A single balance makes competition between businesses visible and prevents each operation from spending the same warehouse unit. Show deliveries, allocations, and carryover in one ledger. If separate counters are useful for presentation, derive them from accepted transactions rather than copying the starting stock into each business.
How many businesses should the first network include?
Three are enough to show a shared junction and different costs. The Wheel uses two Spark while the Tea Cart and Photo Booth each use one. Add more branches after players can predict which operations will open and what stock remains.
Read W3C's keyboard accessibility guidance.
How should visitor preferences affect operations?
Give each day one featured preference and let matching businesses earn a higher mood score. Keep the cost independent from the preference so players compare service value with supply use. A short fixed sequence makes the first allocation strategy repeatable.
What should reset restore?
Restore the first day, zero carryover, the initial three-Spark stock, preference order, and every business's closed state. Clear the transaction log. Test reset after the final day and after a rejected allocation so the next run starts from the same ledger.


