01Intent Router
Collapses one sentence into an intent and context, then decides which service owns it.
Technology
How the system organises a request.
The agent is not a conversation wrapper. It is a runtime that understands, calls, tracks and authorises. Adding a service does not redesign the system.
02Context Manager
Assembles the identity, preferences, history and current state a task needs.
03Memory
Long-term memory and preference modelling, shared across services rather than siloed per app.
04Service Registry
Every service registers its capabilities: search, compare, book, monitor, execute.
05Task / Activity Engine
Keeps work alive and moving, and shows you where it stands.
06Permission System
Reading and acting permissions are managed separately, designed in from day one.
07Tool / MCP Layer
The execution layer that actually touches the outside world.
Service Registry
Adding Travel, Home, Finance or Learning means registering one service — not rebuilding the system.
01Shopping
- Search
- Compare
- Recommend
- Purchase
- Track
02Health
- Read data
- Analyse
- Monitor
- Report
03Work
- Tasks
- Documents
- Organization
- Workflow
- Escalation
04Family
- Members
- Calendar
- Resources
- Decisions
- Cross-service
05Information
- Understand
- Remember
- Relate
- Brief
- Alert
Build order
Phase 1 · Service Center
Home, agent, services and activity connected: intent → service router → basic action → result.
Phase 2 · Shared Context
Establish identity, memory, preferences, context and the permission model.
Phase 3 · Action
Add real execution: search, compare, book, schedule, purchase, monitor, remind.
Phase 4 · Proactive Agent
The system starts surfacing changes, due dates and things worth your attention.