Make room for the contract before you sign
A service contract can look profitable and still bankrupt a young network. In this fictional Alder Exchange example, the company has 6 credits and 2 service units. An existing customer reserves 1 unit, leaving just 1 free. The library contract needs 2 free units, so it cannot be accepted yet.

Expand first, then sign. A small cabinet costs 3 credits and adds 1 unit. Capacity becomes 3 total, with 2 free after the existing reservation. The library fits exactly. A larger cluster costs 5 and adds 3, leaving 4 free, but it consumes nearly all the available cash. Show total capacity and free capacity as separate numbers so reservations cannot disappear from the decision.
Put the runway beside each expansion choice
Before confirming a build, show its price, added capacity, remaining cash, reserved units, and free units. The small option changes cash from 6 to 3. The large option changes it from 6 to 1. Then preview the service cost: 1 credit each day for two qualifying days. The contract pays 5 once after day two, not when accepted and not after every daily tick.

This small preview exposes the real tradeoff. The large build has spare capacity for later clients, but its cash runway cannot cover both service days. The small build leaves 3 credits for operations. After day one it has 2; after day two it has 1; then the 5-credit settlement brings the balance to 6. That last balance can fund another district choice.
Settle once, after the second qualifying day
Use a contract ID and a clear state sequence: offered, accepted, day one served, day two served, settled. Deduct daily operating cost only for a qualifying service day. When the second day completes, record one settlement against that contract ID. Reject a second settlement request for the same ID. The ledger in this article is a fictional rule example, not a report from a shipped or playtested game.
A deterministic local rule test checks the cash and capacity arithmetic. It confirms that the small build can pay both days and finish at 6, while the large build reaches 0 after day one and cannot fund day two before the payout. It also calls settlement twice and verifies the balance increases only once. This narrow test does not simulate a city, telecom network, user interface, or player behavior. In a playable prototype, exercise pause, cancellation, failed coverage, and save/load separately.

Prototype the ledger before decorating the district
Start with one customer reservation, one expansion decision, and one two-day library contract. Keep capacity, reservations, free units, cash, day count, and settlement ID visible. Give each transition a button or deterministic turn action, then compare the displayed ledger with the expected table. Only after those states are stable should the map add more streets or competing contracts.
SEELE AI Game Maker offers a prompt-based starting point for a playable game concept. Describe this as an original fictional management prototype, then check the contract rules in the resulting build yourself. Godot Resources can also store fixed contract templates as reusable data; the official documentation explains how Resources are created and saved. Neither reference validates this example's gameplay.
Create an original telecom management prototype with 6 credits, 2 capacity units, and 1 unit reserved by an existing customer. Add a fictional library contract needing 2 free units. Offer a 3-credit expansion adding 1 unit and a 5-credit expansion adding 3. Service costs 1 credit per qualifying day for two days. Pay 5 exactly once after day two. Show total and free capacity, daily cash, and contract state. Do not claim real network behavior.
Start a fictional management prototype in SEELE · Godot's Resources documentation
Frequently asked questions
Why separate total capacity from free capacity?
The existing customer already reserves one of the two starting units. A contract requiring two free units cannot fit just because the total looks close. Show total, reserved, and free capacity together before signing and again after every build or cancellation. This makes the constraint visible and gives the player a clear reason for an expansion.
When should the contract payout arrive?
In this example, pay 5 credits once after the second qualifying service day. Deduct the 1-credit operating cost at the end of each qualifying day, before settlement. This ordering makes the large build fail its second day at zero cash, while the smaller build reaches the payout. State the order in the UI and encode it in the ledger.
How can I prevent a contract from paying twice?
Give each accepted contract a stable ID and store whether it has settled. The settlement action should require two completed qualifying days and an unsettled state, then atomically mark the ID paid while adding the reward. Test the same settlement call twice. The second call must leave both the cash balance and settlement record unchanged.


