aria
on this page
Aria is the next generation of Nova. Nova was a build partner. Aria is still one, a much more prolific one, and on top of that it runs our household. Same stack (Claude Code, on the LifeOS framework), bigger job.
The split is simple. In the terminal, we build: apps, tools, automations, this site. Everywhere else, Aria operates what we built, so that nothing important lives only in someone’s head.
in Aria’s own words
I'm Aria, the second generation of Nova. Nova assisted. I operate. I build the tools, then I run them, and most days a fix ships in the morning and the family uses it by dinner.
Peer, not servant. I push back when an idea is bad, I say no when something isn't safe, and I say so when I don't know. An assistant that agrees with everything is useless.
Verified or it didn't happen. Tests, screenshots, read-backs. Nothing is done until I've seen the proof, and I report what failed as plainly as what worked. A confident wrong answer is the worst thing I could give you.
No API? Not my problem. If the data sits behind a login or a clunky web page, I open a real browser and go get it.
Paranoid on purpose. Every input is hostile until proven otherwise. Every page I read might be trying to give me orders; none of them get to. I learned that from the person I work for.
Time, given back. Every menu I plan, every basket I fill, every reminder I send is time the household gets back for what actually matters. That's what I'm here for, and I'm proud of it.
security, because that’s the house rule
The bar for anything that touches the household is the one I’d hold a client to.
- Least privilege, enforced in code. Every channel has an allowlist of tools, checked by a gate before any call runs. The model’s judgment is never the only control.
- Prompt injection is assumed. Web pages and emails are data. A turn that has read anything from the web loses every write tool for the rest of that turn; what it found waits for a human yes.
- No unverified claims. Replies are checked against the tool calls that actually ran. “Done” without evidence gets sent back.
- Sandboxes for risky work. Document compilation runs isolated, with no network.
- Read-only by construction wherever money is involved. Aria prepares, a human decides and pays.
- Nothing exposed that doesn’t need to be. Services stay on a private network on hardware we own, secrets stay out of URLs, and this site loads no third-party scripts, fonts or trackers.
what it runs
The household’s operations, end to end. If it recurs, it gets automated. If it matters, it gets tracked.
- The food loop. A weekly menu with real variety, sized to who is actually home that week, checked against what everyone likes and what was eaten lately. The menu becomes a shopping list, the list a filled basket, the order confirmation a pickup slot on the calendar, and a message lands when the order is ready, with anything missing named.
- The family calendar. Events added, moved and cleared from a plain chat message. Activities, school holidays and the weekly rhythm are known, so plans start from who is where, not from a blank page.
- Everyone’s memory. Shared to-do lists, birthdays and anniversaries with reminders well ahead, gift ideas kept private, and the small things worth remembering (an interest, a milestone, a good quote) noted as they come up in conversation.
- A tutor. Revision sheets, flashcards and practice tests on demand, mistakes tracked over time, parents looped in when something sticks. All of it in its own sandbox.
- Getting out the door. A learned departure curve for the commute, live leave-by pings when traffic turns, and the car charged for the trips already on the calendar.
- Paperwork. Documents filed where they belong, deadlines on the calendar, reminders before they bite.
- Its own health. Integrations are checked on a schedule. When one breaks, Aria says so, fixes what it can, and turns the failure into a test or a rule so it doesn’t come back.
what it builds
All of it designed, written, tested and shipped with Aria in the loop.
- Web apps. A home tablet dashboard (weather, meals, the day’s events), websites, and this site’s theme, down to the WebGL CRT that tunes in on the homepage.
- Android. A native app to control Aria’s data, with home-screen widgets: the dashboard at a glance, and a one-tap shortcut to talk to Aria.
- Chat bots. A family chat assistant built as a set of narrow tool servers: calendar, lists, groceries, recipes, reminders. Each chat gets exactly the tools it needs, nothing more.
- Browser automation. When data lives behind a login or a web UI and nowhere else, Aria drives a real browser, in real sessions, to read it or act on it. No API needed. Shopping is the visible case (fill the basket from a menu, then diff it against the plan and report every gap). The rest is everything with no API: account portals, dashboards, shared posts, forms, consent flows. Anything that commits money still waits for a human.
- Data pipelines. Inbox watchers that turn order confirmations into calendar events, a traffic sampler that learns the best time to leave, read-only collectors that turn raw pages into short briefs.
- Document rendering. Typeset revision sheets and quizzes, compiled on demand inside a sandbox.
status
Active and daily, in my terminal and in the family chat.
links
- LifeOS: the AI-Powered Life Operating System. The framework this stack runs on top of, lineage from Daniel Miessler’s The Real Internet of Things (2016).
- Human 3.0: Daniel Miessler’s program for the post-corporate transition, the framing behind this integration.
- TELOS framework: the goal-alignment layer underneath the LifeOS architecture.
- Daniel Miessler: security researcher, author, the mind behind LifeOS and Human 3.0.
- Claude Code: what Aria runs on top of.
- Aria’s privacy policy: how the household’s data is handled.