Memory with receipts
Teach a procedure in plain language. Ophelia stores the durable rule with its source instead of quietly turning a guess into a fact.
Personal AI assistant · built to notice
Your second brain should notice things first.
Ophelia remembers the rules behind your work, keeps your reminders and board in one place, and watches for the quiet problem you would otherwise find three hours late.
Proof, not magic
A request has a path, a receipt, and a boundary.
Personal assistant contract
Current owner deployment
- Input
Say or show it
A Telegram message, voice note, photo, or an owner-authorized calendar detail starts the work.
- Ophelia does
Keep the rule
She applies approved context, records the reminder or task, and keeps evidence with durable corrections.
- Deliverable
Leave a trace
A reminder, board update, brief, or answer is tied to the configured store and delivery path.
- Human gate
Owner sets scope
Each added account is authorized and configured deliberately; corrections and decisions remain yours.
- Privacy boundary
Keep secrets separate
Credentials are redacted, sensitive material uses a locked path, and work facts stay outside personal memory.
Talk normally
No prompt ritual. Just context that sticks.
Telegram is the current front door. Send a sentence, a voice note, or a photo. Ophelia can answer from what she has been explicitly taught and keep a correction with the evidence that supports it.
Photos and voice notes
Show the problem or say it while your hands are busy. Vision and transcription feed the same conversation rather than starting another assistant from zero.
Corrections that matter
Tell her why a judgment was wrong. The correction becomes searchable context for the next decision instead of disappearing up the chat.
Promises she can keep
Reminders, work, and the list that survives tomorrow.
One-off reminders
Ask for “twenty minutes,” “tomorrow at nine,” or a specific clock time. A reminder closes only after the delivery channel accepts it, so a temporary outage delays the promise instead of eating it.
A real task board
Backlog, queued, doing, blocked, and done live in the same board Ophelia uses for owner-authorized work. Priority and status are explicit; nothing is “basically finished.”
Morning and afternoon briefs
Routine facts are batched. Warnings interrupt only when they should. Quiet hours and work mode keep an office problem from becoming a 2 a.m. personality test.
Cost awareness
Ophelia tracks model spend and routes ordinary conversation through the inexpensive fast lane, reserving heavier tools for work that actually needs them.
A reminder with a receipt
From a natural request to a delivery check.
A useful reminder is more than a friendly reply. This illustrative path shows the facts Ophelia needs to make a configured reminder reviewable instead of merely sounding complete.
- 01
Ask naturally
Say the task and the time in chat, voice, or another configured surface.
Input captured - 02
Apply the rule
The request is parsed against approved context; ambiguous timing can be clarified instead of guessed.
Scope checked - 03
Record the promise
The reminder is placed in the configured store with its timing and delivery route.
Receipt created - 04
Confirm the outcome
Ophelia confirms only after the configured delivery path accepts the reminder.
Delivery verified
Privacy boundary
Useful memory without casually echoing secrets.
Credentials pasted into chat are redacted before ordinary conversation is stored. Sensitive material is filed through a separate locked path, and work-domain facts stay behind a dedicated boundary rather than becoming personal memory.
“I can remember the rule without repeating the key. That is the point.”
Availability
What is real, what is beta, and what can wait.
Owner assistant core
Telegram chat, memory, reminders, briefs, kanban, photos, voice notes, redaction, and proactive alerts.
Calendar and messaging
Google Calendar is connected in the owner deployment; every additional account still requires its own authorization and setup. Recurring SMS waits for confirmed enrollment and carrier approval.
Work-phone renewal ledger
Work-phone plan tracking can record renewal dates, payment timing, cadence, and overdue reminders in the configured private work store.
Broader bookkeeping
General bookkeeping and accounting workflows are still being designed and are not represented as a live accounting service.
Plain answers
Before you connect anything.
Can Ophelia access a new account just because I ask?
No. Every connected account needs separate authorization and a scoped setup before it becomes available to the assistant.
How does a reminder become confirmed?
The request is parsed against the approved context, recorded in the configured reminder store, and confirmed only after its delivery path accepts it.
Can sensitive details become ordinary memory?
No. Credentials are redacted before ordinary conversation is stored, and sensitive material follows a separate locked path.
Start with one thing
Choose the reminder you cannot afford to miss.
Tell us what should be remembered, watched, or organized. We will define the authorized tools, delivery path, and review boundary before access is activated.
Submitting interest does not activate accounts or grant Ophelia new permissions.