Ryad · operating system · information routing
You type fast, drop links, leave voice notes, tick boxes. Behind that, every piece of it runs the same path: it comes in through one of a few channels, gets swept and verified, is filed into several stores at once (each holding a different kind of truth), and surfaces back to you on one screen. Read the walkthrough first, then see it as one map at the bottom.
Seven doors in. You never pick one deliberately, you just act, and each door is watched.
Typed, terse, or voice-to-text. The main door. Every word, both sides, is captured.
A thought fired into your phone. Read on every boot, sorted into to-do, question, or reflection.
The Ryad account, scanned locally each session for bills due and anything time-sensitive.
Read and written both ways, so the diary and the system never drift apart.
Annotate a row, mark it done, paste onto it. Your edits queue up as instructions back to me.
You mark a doc "done" or scribble on it. The flag itself is the message: action this, then file it.
The room you and Simo share. What lands as a row there is real to the system; nothing else crosses in.
Four moves, always in this order. Skipping them is the one failure the whole system is built to prevent.
01 · anchor
Nothing is "recent" until checked against today. I boot cold; the world moved without me.
02 · sweep
Search all 3,600+ vault files, by keyword and by meaning, before I act. Context first, always.
03 · verify
Open the real file. Check the internet for anything outside the vault. Know it, then say it.
04 · route
Send each piece to its right store, and drop the context onto the relevant person in the same breath.
The same fact often lands in several places on purpose. Each store answers a different question, so none of them has to do another's job.
Every session written down word for word, automatically, as it happens.
Why: the evidence layer. When something's disputed, this is what was actually said, not a summary of it.
A living page per person and per organisation, fed by every mention across the vault.
Why: so I never ask "who's this?" about someone you've told me about. Context compounds on the person.
One operating file per live workstream, holding the current position and next moves.
Why: the working memory of each project, kept separate so status is never buried in chat.
The lessons and preferences that must survive across every session.
Why: I start each session from zero. This is what carries forward so you don't repeat yourself.
The record of favours and intros exchanged, plus health, food, and training logs.
Why: relationships and habits are only visible over time. A ledger sees the pattern a chat can't.
What changed this session, and what I concluded from it, kept as two separate trails.
Why: so the reasoning behind a decision can always be traced back to its origin.
This is the rule that governs the whole store layer. One event splits into three records that are never merged, because each answers a question the others can't.
what was said
Your exact words, verbatim. The ground truth nothing is allowed to overwrite.
what I concluded
My read on what it means and what to do. Interpretation, kept clearly apart from fact.
what changed
The concrete edits that resulted. The audit trail of every move made.
All of the above is backstage. You open one surface. The rule: if it isn't here, it doesn't exist for you.
The daily surface. To-dos, messages to send, decisions, project health, body, reminders, all pulled live from the stores. This is the front end of everything behind it.
The agenda on your phone, synced from the same source so the schedule is never a second copy.
The exhaustive version behind the Console, written for depth, there when you want to go deeper.
The Console isn't the end, it's a channel back in. You react on it, tick a box, annotate a row, and that becomes a new input at Stage 01. I sweep the change, update the stores, and refresh the screen. A closed loop: you act, it files, it surfaces, you act again.
the same flow, one picture
Follow the arrows: channels converge into the intake, fan out to the stores, converge onto the Console, then loop back in.