One life, run by agents that answer to you.
For one person with a calendar that leaks, an inbox that never empties, and money that deserves a watcher — who wants agents doing the work and a gate on anything that would be socially or financially expensive to undo.
Everything below — every role, purpose, measure and gate — is rendered from PERSONAL_OS in @flashyos/aao at build time. This page cannot drift from the shipped template.
“One person's life, run by agents that answer to them.” — 5 standing responsibilities, each a role that outlives whoever holds it. Capabilities name actions, never departments; gates sit where a mistake would hurt, not everywhere.
| Role | Purpose | Capabilities | Approval gate | Measure |
|---|---|---|---|---|
| calendar operations | Protects focus time and keeps commitments from colliding. | schedule · decline · notify | human at MEDIUM+ | Hours of uninterrupted focus per week |
| inbox operations | Reads everything that arrives and surfaces only what needs a person. | read · summarise · draft | human at HIGH+ | Messages needing human attention per day |
| finances finance | Tracks what comes in and goes out, and flags anything unusual. | categorise · reconcile · report | human at LOW+ | Days between an anomaly and it being noticed |
| health operations | Keeps appointments, prescriptions and results in one place. | track · remind | human at LOW+ | — |
| coordination governance | Decides which role owns something new, and keeps this charter true. | plan · approve | no gate declared | — |
accountableTo: you@example.com — the template ships the placeholder on purpose; conformance fails it until a real human is named. That field is the whole point. Escalation: coordination.
The calendar role schedules and declines with a MEDIUM gate — because declining on your behalf is socially expensive and hard to undo, so it proposes and you approve. Its measure is hours of uninterrupted focus per week: the number the role exists to move.
The inbox role reads everything and surfaces only what needs a person. Its capabilities are read, summarise, draft — sending is deliberately not in the list. The safest capability an agent can lack is the one you never granted.
The finances role tracks and reconciles with approval required at LOW impact — anything touching money asks first. Its measure: days between an anomaly and it being noticed.
Copy the template, change every field — a charter describing work nobody does is worse than none — then gate your CI on validateCharterDocument and static conformance. The full path — validation, the CI conformance gate, the JSON Schema for any language — lives on the builder hub; the format itself on the AAO spec page, and the naming rules every role above passes at /standard.
These are starting points, not defaults to ship — a charter describing work nobody does is worse than none. When yours validates clean, the network is waiting.
Start building