What’s Next
Sandy’s journey from sandwich shop to franchise. What you learned, where to go.
Sandy’s Journey
Phase 1: Sandy's Sandwiches
→ Single file, CLI, Dict + Functions
→ Learned: Intent, Pipeline, Processor, Level
Phase 2: Sandy's Online
→ Web API, @route, TypedDict + Validation
→ Learned: DI, Error Handling, Middleware, Testing
Phase 3: Sandy's Franchise
→ Multi-location, Native IOP, Message Bus
→ Learned: Plugins, AI Agent, Parallel, Production
What You Learned
| Level | Concepts | Syntax |
|---|---|---|
| Level 1 | Intent, Pipeline, Processor, Context, Result | Native IOP |
| Level 2 | @route, Validation, DI, Error Handling, Testing | @route |
| Level 3 | Native IOP, Message Bus, Plugins, MCP, Parallel | Native + @controller |
The Three IOP Levels
| Level | Data | Best For |
|---|---|---|
| Dict + Functions | dict | Scripts, small tools |
| TypedDict + compose | TypedDict | Medium CLIs |
| Dataclass + decorator | dataclass(frozen=True) | Production systems |
The Plugin Ecosystem
Sandy started with zero plugins. Here’s what she could add as she grows:
| Plugin | When Sandy Needs It | What It Does |
|---|---|---|
evoid-sqlite | Save orders to a database | SQLite storage engine |
evoid-redis | Cache menu for speed | Redis cache with TTL |
evoid-auth | Know who’s ordering | BYO auth providers |
evoid-di | Manage database connections | 3-tier dependency injection |
evoid-tasks | Background order processing | Godot-inspired task lifecycle |
evoid-dashboard | Monitor all locations | Web monitoring UI |
evoid-smart-storage | Route data to the right DB | Multi-DB routing by level |
evoid-scheduler | Priority orders when busy | System-aware priority scheduling |
evoid-cluster | Connect 4 locations | Multi-node clustering |
evoid-godot | Sandy’s sandwich video game | Godot game integration |
evoid-transport | Low-latency game state | UDP transport for games |
# Phase 2: + evoid-sqlite + evoid-redis + evoid-auth
# → Online shop with database, cache, login
# Phase 3: + evoid-cluster + evoid-dashboard + evoid-scheduler
# → 4 locations, monitoring, priority orders
# Bonus: + evoid-godot + evoid-transport
# → "Sandy's Sandwich Simulator" video game
```
Intent Levels Recap
| Level | Pipeline | Timeout | Use Case |
|---|---|---|---|
ephemeral | validate | 5s | Cache, sessions, game state |
standard | validate, authorize | 10s | Profiles, orders, posts |
critical | validate, authorize, audit, protect | 30s | Payments, medical, legal |
Where to Go Next
- Godot Games — Same concepts (message bus, plugins, real-time) applied to multiplayer games
- IOP Levels — Deep dive into the three levels
- Plugin Collection — All 15 official plugins
- Configuration — Full config reference
- Plugin Standard — Build your own plugins
- Schema Export — AI agent integration
- Examples — More code examples
Community
- GitHub: EvolveBeyond/EVOID
- Issues: GitHub Issues
The Golden Rule
Start from Level 1. Upgrade only when it hurts. Never start at Level 3.
Sandy started with a dict and a function. She ended with a franchise. That’s IOP.