Technologies¶
Toaster Chef is a layered, server-authoritative system. The visualization layer (Phaser) sits on top of a simulation engine (Colyseus), which feeds an analytics layer, all driven by scenario configuration and calibrated by a research-agent ecosystem.
Visualization Layer Phaser 3 (secondary — interactive display of simulation state)
Simulation Engine Colyseus — Kitchen Garage + siMPowerUp, 100ms tick
Analytics Layer Per-tick outcome accumulation, SimulationOutcome export, sim clock
Scenario Layer server/scenarios/*.json — ScenarioConfig per named scenario
Agent Ecosystem Research agents calibrate parameters with real-world data
Each layer is completed before the next begins.
- Architecture — the server-authoritative model, agent/ecosystem design, shared types, and server-side map generation
Implementation layers¶
| Layer | Scope | Status |
|---|---|---|
| 0 | Formal model — types, scenario JSON, doc updates | ✅ Complete |
| 1 | Core sim tick: Circle/HelpRequest lifecycle, analytics accumulation | Next |
| 2 | Scenario system: JSON loader, REST endpoints (GET /scenarios, POST /scenarios/{name}/run) |
Upcoming |
| 3 | Agent data collection — calibrate parameters with real-world research | Ongoing |
| 4 | Headless batch simulation + SimulationOutcome export |
Upcoming |
| 5 | Analysis visualization (Phaser Analysis Mode or dashboard) | Later |
Sub-agent ecosystem¶
Parameter calibration is done by a set of research sub-agents, invoked from the Big Nerd Idea workspace. Output always lands in server/scenarios/calibration-notes.md, and all findings are [SIMULATION OUTPUT] until field-validated.
Toaster Chef-specific: Food Systems Research, Nonprofit Operations, Community Need Mapping, Simulation Validation, Scenario Design.
siMPowerUp-specific: Mutual Aid Network Research, Token Economy Scenario, Bad Actor & Risk Scenario.
Cross-cutting (inherited from Big Nerd Idea): Red Team, Regulatory Intelligence, Grant Intelligence.
Real-world deployment data — when the Charleston Pilot or a real-world Trike produces it — flows back into scenario calibration as [PILOT VALIDATED] data points.