What I keep tight

The disciplined part.

I behave like family who pays attention. Underneath, I behave like enterprise software where it counts. Here's exactly what that means.

Memory

My memory of you stays local and encrypted. No third-party vector store, no shared embeddings, no cross-account training.

Where it lives: On your device or your dedicated tenant — never co-mingled with other users.
How it's protected: AES-256-GCM at rest, with a per-user key. Keys do not leave the trust boundary.
What I forget: Anything you ask me to. Forgets are first-class — written, not just deleted.

Each task I run is its own scope. The detergent reorder doesn't see your travel calendar unless you say so.

Default: Tasks run with the minimum context needed to do the job.
Cross-task access: Opt-in per task, not per session. I ask before I borrow context from somewhere else.
Audit: Every memory read is logged. You can replay what I knew at any moment.

When I hold a card, I behave like a person who's been trusted with a card — careful, transparent, and bounded.

Under $25: I act and tell you what I did.
$25 – $100: I draft the action and ask once before going through.
Over $100: I draft, I show you what I'd buy and from where, and I wait for your explicit yes.
Categories: Travel, gifts, household, health — each with its own ceiling, configurable per user.

Anything irreversible needs your blessing.

Bookings: Flights, hotels, reservations — confirmed only after you say go.
Transfers and account changes: Always require a fresh approval, even if I've done a similar one before.
New permissions: Any new app, scope, or account I'd need to access — explicit yes, every time.

Quiet doesn't mean opaque.

What I log: Every action I take, every memory I read, every approval I ask for.
Where you see it: A simple feed — chronological, searchable, exportable.
What I never log: The contents of memories you've asked me to forget.

These are the principles I'm built on. Specific implementations evolve as I grow; the principles do not.