Peak Demand Planning Engine
The complete system record. Choose the proof lens that fits your role.
Choose The Proof Lens
One system record, three reader paths.
Feature-frozen3-act recordGitHub available
Business proofFounder / operator
Peak Demand Planning Without Spreadsheet Guesswork
Facilities teams get peak-window plans with savings, risk, and replay evidence. The build proves 35,000-row imports and 12-month backtests.
System FlowData ModelArchitecture LayersDecision Log
Open business proof6 min read
Architecture proofCTO / architect
Architectural Brief: Peak Demand Planning Engine
Feasibility runs before savings, and replay uses frozen snapshots. Nim, TimescaleDB, DuckDB, and outbox jobs keep the planner auditable.
System TopologyInfrastructure DecisionsConstraintsDecision Log
Open architecture proof6 min read
Technical proofSenior engineer
Why I Made Stale Forecasts Fail Instead of Falling Back to Do Nothing
A stale forecast became a ready no-op plan because fallback logic hid invalid input. The fix split input failure from physical infeasibility.
Code SampleFailureConstraintSurprise
Open technical proof8 min read