Repository navigation
Her working day
One book, held by the bridge, that every seat reads: what she keeps, what she owes you, and the brief she opens the day with. Captures, reminders, standing orders and the day's brief live in one store the bridge holds (config/daybook.json), so every seat — the dashboard, your phone, the server — reads the same day. The book rides account sync like chats and cases do: entries converge by identity, the newest word wins, and a deletion is a tombstone no stale copy can talk its way past. It is secret-free by construction: anything shaped like a credential — a password, an API key or token, a card number, a Social Security number — is refused at the door by name, in chat and on the page alike. The book holds facts about your day, never keys to anything.
Capture & recall. Ask her to keep something — remember that the lab renews in March — and the save lands in the day book with its provenance: who decided it (your trigger, or her own call, named as such) and when. She can also save on her own judgment in a conversation; those saves are receipted the same way and named as hers. A correction supersedes the fact it corrects — the old wording is kept, marked superseded, never silently rewritten. Undo that takes the last capture back, and recall the lab reads the book back to you. Home's Her working day card has a plain capture line too — same book, same rules. Ask-mode saves stand as proposals on the card until you accept or refuse them.
Reminders. Remind me to call the dentist tomorrow at 9 — the reminder is bridge state, kept by a scheduler that lives in the bridge itself, so it survives restarts and fires whether or not any window is open. When it fires it lands on the bell and, with push on, on your phone's lock screen — the same words in both places. It then stands fired until you acknowledge it; the acknowledgement is itself synced, so clearing it on one seat clears it everywhere, and the ack closes the phone copy with the same clearing push the bell's ack sends. If the bridge was down when a reminder came due, it fires on the next start — late, and named late.
Standing orders. A standing order is a small, durable instruction she executes on a trigger: standing order: every day at 08:00, report the wire count. The vocabulary is deliberately bounded — an order can remind, report (her greeting's own sources: the wire, the cases, the watches, the book), file into a case, or check a Pulse watch — on a clock, on an interval, daily, or when the brief is composed. It can never send, spend, elevate, delete, run or call, and an order that asks for those is refused by name when you give it; weekly orders are named as out of this cut rather than approximated. Every execution is recorded on the order itself — when, what it did, how it ended — and read back from Home's card, where an order can be revoked. A file order names its case; if the case is not there, the execution says so and files nowhere.
The day brief. Her greeting grows a day section: what is on (today's standing reminders and orders), what changed (what the book gained, what fired, what a watch flashed), and what needs you (anything fired and unacknowledged, anything that ran and failed). The brief is a stored record — composed at the day's first light and again whenever you ask (brief me, or the button on Home's card) — one standing brief per day, a recomposition superseding the morning's. A source that cannot be reached is badged as a gap in the brief, never smoothed over. There is no calendar connection in this cut: the day she briefs is the day the book knows.
The brief is a document now. It composes — deterministically, no model call — as markdown: a dated title, the sections On / Changed / Needs you / Standing, one bullet per item, and a Gaps section where an unreachable source stands as a named GAP bullet instead of a silent thinning. The stored record holds the document, so recall returns it whole and Sync carries it as-is.
No surface shows the markdown. The Day card above and the chat answer both draw from the document and present an actual list: section headers, and item rows carrying their time and their state — waiting, done, pushed. Ask "brief me" in chat and the answer arrives as that list, a structured element in the thread — not a paragraph, not rendered markdown.
Reminders can be pushed off, on the record. Say "snooze it to tomorrow" or "push it in 30 minutes" in chat, or press Push to tomorrow on a fired reminder's row. The act is written onto the reminder's own record — when it was pushed, from when, to when — a fired reminder stands again, and the deferral count is derived from that record: one per push, plus one per whole day a fired reminder sits unacknowledged past its firing day. Nothing keeps a separate counter.
And Navi is in the journal. Push the same reminder twice and the brief carries her remark as a row of her own, in her name, directly under the item — a raised eyebrow at the second push, pointed at the third, her full attention from the fourth. The lines are written, not generated: the same count always draws the same line, consecutive counts never repeat one, and a re-render never re-quips. Work items — reminders born of standing orders — get the professional set. She teases; she does not nag.
Getting started
Talking to Navi
Navi Mesh
Chips
Knowledge & RAG
Settings & updates
- Settings & persona
- DHD — Apex from anywhere
- GitHub — the pulse, issues & backups
- Installing & updating
Help