Two nights, no shore power, every peak declared

This case is replayed live from the frozen fixture RV-01 against the current rules engine and catalogue version rv-catalog-2026.08.15.1. It is published as a worked example of the method, not as a purchase recommendation.

1. What was declared

2. The arithmetic

Declared daily need is 720 Wh per day across 2 loads, over 2 nights, against 300 Wh per day of credited solar. The engine's own working:

3. The three gates

The peak is proven only because a startup figure was declared for the fridge. Had it been left blank, the case would have abstained from naming any exact product — an undeclared surge is treated as unknown, never as zero.

4. Why the verdict says what it says

• The trip energy fits inside a single portable station class.

Stable codes: E03-CAPACITY-PORTABLE, E01-MISSION-COVERED, S01-SURGE-DECLARED, P01-NO-PRODUCT-RANKING, L02-LOOP-OPEN, L04-RECHARGE-CREDIT-CAPPED.

5. Limits of this case

• This architecture calculation on its own names no product, model, price or ranking. An exact SKU is only ever shown separately, by the dated RV catalogue layer, and only when its own evidence and commercial gates pass.
• This declared trip is sized as a finite mission. It is not sustainable for another day without about 510 Wh/day more credited recharge: 720 Wh/day is used and only 210 Wh/day is credited back. Stored energy alone never closes an indefinite loop.
• The figures above are the fixture's declared inputs. They are a realistic weekend, not your weekend: a different fridge, a shaded panel or one added device changes the answer.

6. What the engine did about a product

The declared daily recharge loop does not close (510 Wh/day still missing). Energy, continuous power, peak, recharge and connectors must all be proven compatible before an exact SKU is named, so this is an explicit abstention.

Further reading

• How RV solar and generator sizing works
• The published methodology
• All guides, diagnostics and research