Scenarios and controls
Tune population, time, pressure, message volume, decision mode, and transports.
Configuration
| Field | Range or values | Effect |
|---|---|---|
profileCount | 2–60 | Number of actors seeded into the world |
randomSeed | 1–999,999 | Repeatable source for seeded and tick behavior |
speedMinutes | 5–240 | Simulated minutes per tick |
appointmentPressure | 0–1 | Intensity of appointment demand |
messageVolume | 0–1 | Intensity of organic messages |
evaluatorMode | deterministic, ask-human, ask-ai | How organic decisions are resolved |
aiEnabled | boolean | Whether Claude may generate messages and decisions |
transports | mechanism per capability | Where booking, messaging, and cancellation execute |
Scenarios
The scenario is a named behavioral context carried into the world and AI prompts.
quiet-morningstarts with lighter operational demand.winter-pressurerepresents a busier, more strained care context.follow-up-backlogemphasizes waiting and unresolved work.mixed-realityis the broad default.
Deterministic runs
Use the same random seed, configuration, and sequence of inputs to reproduce pure simulation behavior. For strict comparisons, disable AI because external model output is not guaranteed to repeat.
curl -X POST http://localhost:3000/api/simulation \
-H 'Content-Type: application/json' \
-d '{"config":{"randomSeed":7331,"aiEnabled":false,"evaluatorMode":"deterministic"}}'Changing a world
Patch in place
PATCH /api/simulation merges configuration into the current state. Nested transports are merged so changing one mechanism does not reset the other two.
Reset and reseed
POST /api/simulation validates a complete configuration with defaults, seeds a new world, and replaces the current state. Use this for profile count, seed, organizations, or location changes that should start cleanly.