Each ledger line in the game links to one of these ids.
F-UTIL Option utility
utility(j) = w_reliability x reliability(j) + w_automation x automation(j) + w_integration x integration(j) + w_reach x reach(j) - w_price x annualPrice(j) / referencePrice, plus the segment relationship bonus when j is the cohort's current supplier.
The outside option uses a fixed utility value and never receives a relationship bonus.
F-SOFTMAX Choice probability
share(j) = exp((utility(j) - maxUtility) / temperature) / sum over options of the same expression. The maximum logit is subtracted before exponentiating so the arithmetic stays stable.
F-ALLOC Cohort reallocation
For each segment and each origin cohort (incumbent, challenger, outside): retain (1 - reconsiderationRate) x cohort, and distribute reconsiderationRate x cohort across all three options using F-SOFTMAX. Segment totals are conserved. No customers are added afterwards.
F-REV Quarterly revenue
revenue = ending active customers x annual team price / 4.
A disclosed simplifying convention. Contracts, ramp, churn timing and partial-quarter recognition are not modelled.
F-VC Quarterly variable cost
variableCost = sum over segments of ending active customers x variable cost per customer per quarter.
F-OCF Operating cash flow
operatingCashFlow = revenue - variableCost - fixedCost.
This is not EBITDA and not audited profit. It is a simplified cash measure for the exercise.
F-CASH Ending cash
endingCash = openingCash - investmentOutlays + operatingCashFlow. Investments are one-off cash outlays, never recurring expenses.
P-SEGMENTS Segments and reconsideration
800 small teams and 200 enterprise teams. 20% of each small-team cohort and 8% of each enterprise cohort reconsider their supplier per quarter. Relationship bonus 0.08 for small teams and 0.18 for enterprise teams. Outside utility 0.20. Choice temperature 0.20.
P-WEIGHTS Segment buying weights
Small teams: reliability 0.20, automation 0.40, integration 0.10, reach 0.10, price penalty 0.20, reference price $2,400. Enterprise teams: reliability 0.35, automation 0.15, integration 0.30, reach 0.05, price penalty 0.15, reference price $24,000.
P-TRAITS Trait bounds
Reliability, automation, integration and reach are dimensionless scenario parameters clamped to [0,1]. They are preference proxies, not measurements.
P-PRICEFLOOR Price floor
No price may fall below 50% of the role's original list price. A price cut that would breach the floor is held at the floor, and the cut becomes unavailable once both segments sit on it.
P-VARCOST Variable cost changes
Autonomous delivery raises variable cost 15% at activation. The commodity-models event cuts both companies' variable costs 20%, once.
P-TIMING Activation and effort
A commitment with a one-quarter delay reserves effort in the quarter it is made and activates at the start of the next quarter. A two-quarter project reserves effort in two consecutive quarters and activates in the third. Capacity does not carry over, and a commitment that cannot reserve future effort is rejected. Projects due after the final quarter stay in the ledger as committed work with no terminal benefit.
P-EVENTS Environment events
Each preset schedules at most one event. It is revealed and applied exactly once, at the start of the quarter it fires, before either side chooses. The effect then persists and is never re-applied. Research bought in a quarter reveals the next quarter's scheduled change.
P-INSOLVENCY Funding required
Negative ending cash is marked as funding required. There is no automatic financing. Paid commitments are then blocked; price changes and hold remain available.
Environment presets
Foundation
Segment weights, costs and the outside option stay unchanged for all four quarters. Use this to read the economics without interference.
No events. Nothing changes for four quarters.
Reliability shock
At some point in the game, a publicised failure moves 0.10 of buying weight from automation to reliability in both segments. The quarter is hidden until it is revealed or researched.
- Weight shift of 0.10 from automation to reliability in both segments.
Commodity models
At some point in the game, cheap general models cut both companies' delivery costs by 20% and make the outside option more attractive. The quarter is hidden until it is revealed or researched.
- Both companies' variable costs fall 20%.
- Outside-option utility rises from 0.20 to 0.30.
The quarter an event fires is deliberately not listed here. It becomes visible when the event happens, or a quarter early if you commission research.
The opponent
The P0 opponent is deliberately simple, and it is important that you know how simple. Each quarter it:
- enumerates its legal actions in the catalog order above;
- forecasts up to 2 quarters for each one, assuming you hold and no further public events occur;
- picks the action with the highest forecast ending cash;
- breaks ties on higher ending customer count, and then on catalog order.
The look-ahead is clipped to the quarters that remain. The opponent commits from the same information snapshot as you: it is handed a public snapshot with your research and the hidden event schedule stripped out, so it cannot read your unlocked action or see what is coming. It has no memory, no model of you, and no notion of long-term positioning. Beating it is not evidence that a strategy is good.
Rewind, branching and role reversal
Rewinding a quarter creates a new run from that pre-decision snapshot. Earlier decisions and the external event sequence are preserved, the original run is left untouched, and the new run records the original as its parent. The opponent policy is recomputed from the branched state rather than replaying its old moves.
Switching sides starts a fresh game from the original opening state and environment, with your complete recorded action sequence driving the other company. Those actions are replayed when legal. When one becomes illegal the script holds and states why; it is never silently upgraded to a stronger move. That session is labelled a fixed-opponent comparison. Outcomes are only comparable within the same scenario, and there is no universal strategy score.