Decision cases
Worked cases, replayed against the live engine
Each case below is a frozen set of declared inputs. Nothing on those pages is typed by hand: the inputs are replayed at render time against the current rules engine and the current catalogue, so a published case can never drift away from the method it claims to illustrate.
A decision case is not a review and not a recommendation. It shows one declared situation, the arithmetic the engine produced from it, the three gates it evaluated — mission energy, daily recharge loop, startup peak — and the reasons and limits attached to the verdict. When the evidence does not support naming an exact product, the case publishes that refusal and the measurement that would change it.
- Decision case · RV-01RV-01 — Two nights, no shore power, every peak declared“Can a portable station cover a two-night weekend with no hookup?”What a complete declaration looks like: every startup figure given, the mission energy covered, the peak gate closed, and a verdict that the method is willing to stand behind.Verdict status: sized · Peak: proven · Replay reproduces its frozen expectations
- Decision case · RV-02RV-02 — RV air conditioner, no shore power, no soft start“Will a battery run my RV air conditioner off-grid?”The opposite outcome: the arithmetic is published in full, the peak stays unproven, the daily loop stays open, and the method escalates instead of naming a product.Verdict status: escalate · Peak: unproven · Replay reproduces its frozen expectations
More cases: further cases are published when a frozen fixture exists for them and the replay passes. There is no publishing quota and no schedule — a case appears here because it demonstrates something the existing cases do not.