Client app
Next.js app for the landing page, the customer app, and the Valio console. It never calls AimoGuard directly: only the engine. Signing keys stay in server routes.
Who uses it
| Who | Role |
|---|---|
| Human (client) | The kitchen person using the app: asks, reviews exceptions, signs when needed |
| Agents | AimoAssist (and other buyer software) working for that kitchen through the engine and AimoGuard |
There are not separate cook / approver / manager / auditor apps. One human client, with agents doing the buying work under the kitchen’s signed permission slip.
What it does
- New request (text; voice/photo via the engine)
- Live cart build (progress on screen)
- Review by exception → human signs when rules ask → place order
- Knowledge base (diet, dishes, slip, learned prefs)
- Weekly standing orders
- Valio console: customers, orders, risk, audit, gateway health
Surfaces
| Surface | Audience |
|---|---|
| Landing | Visitors |
| Customer app | Human client (+ agents working for their kitchen) |
| Valio console | Valio operator overview |
/connect | Outside builders: open connector + offer check |