How ferrobo/reverie works
REVERIE stress-tests an already-planned wildfire-mitigation workday: preserve a fixed checkpoint, inject a controlled failure or delay, model recovery, and measure direct versus downstream priority-work loss. Its flagship experience presents sealed, reproducible audit and verification evidence; a separate bounded live workflow edits and tests a small workday. The backend audit path is supported by sampled source references; some frontend capability links are documented in the README but their wiring was not sampled.
Main entry points: audit.py Stress audit · traps.py Cliff analysis · planner.py Recovery planner · simulator.py Checkpoint simulator
Components 21
Evidence workspace
- Sealed benchmark
frontend/app/page.tsx - Evidence views
frontend/components - Route map
frontend/components/WorkspaceMap.tsx - Artifact validation
frontend/lib/validation.ts
Live stress test
- Workday editor
frontend/app/crash-test/LiveWorkdayBuilder.tsx - Guided tour
frontend/app/crash-test/GuidedTour.tsx - Live analyze route
frontend/app/api/live/analyze/route.ts - Live API
backend/live_api.py - Live adapter
backend/live_adapter.py - Road routing
backend/live_routing.py
Crash-test engine
- Workday model
backend/schemas.py - Failure scenarios
backend/scenarios.py - Checkpoint simulator
backend/simulator.py - Travel model
backend/travel.py - Stress audit
backend/audit.py
Proof and recovery
- Recovery planner
backend/planner.py - Cliff analysis
backend/traps.py - Commitment proof
backend/verify.py - Repair audit
backend/repair.py - Recovery route artifact
backend/recovery_routes.py
Other components
- Workday coordinator
Connections 32
- Workday coordinator → Sealed benchmark: inspect evidence
- Workday coordinator → Workday editor: edit workday
- Sealed benchmark → Artifact validation: validates artifacts
- Sealed benchmark → Evidence views: presents evidence
- Sealed benchmark → Route map: shows routes
- Workday editor → Guided tour: renders tour
frontend/app/crash-test/LiveWorkdayBuilder.tsx - Workday editor → Live analyze route: submits analysis
- Live analyze route → Live API: requests analysis
- Live API → Live adapter: delegates
backend/live_api.py - Live API → Workday model: uses schemas
backend/live_api.py - Live API → Road routing: uses routing
- Stress audit → Workday model: reads models
backend/audit.py - Stress audit → Failure scenarios: generates scenarios
backend/audit.py - Stress audit → Checkpoint simulator: simulates checkpoints
backend/audit.py - Stress audit → Recovery planner: solves recovery
backend/audit.py - Recovery planner → Workday model: uses models
backend/planner.py - Recovery planner → Checkpoint simulator: uses simulation types
backend/planner.py - Recovery planner → Travel model: uses travel data
backend/planner.py - Checkpoint simulator → Workday model: updates state
backend/simulator.py - Checkpoint simulator → Travel model: reads travel times
backend/simulator.py - Cliff analysis → Stress audit: analyzes audit
backend/traps.py - Cliff analysis → Recovery planner: uses recovery plans
backend/traps.py - Cliff analysis → Checkpoint simulator: uses crash results
backend/traps.py - Cliff analysis → Travel model: checks travel provenance
backend/traps.py - Recovery route artifact → Recovery planner: normalizes recovery state
backend/recovery_routes.py - Recovery route artifact → Failure scenarios: uses scenarios
backend/recovery_routes.py - Recovery route artifact → Workday model: uses models
backend/recovery_routes.py - Recovery route artifact → Checkpoint simulator: reads crash state
backend/recovery_routes.py - Recovery route artifact → Travel model: materializes route geometry
backend/recovery_routes.py - Cliff analysis → Commitment proof: selects proof candidates
- Commitment proof → Repair audit: informs repair
- Stress audit → Cliff analysis: projects loss matrix
backend/traps.py