Planned
DEMO: prepare a call, finish Client A’s page and inspect Client B’s campaign.
Start with your evening, not the databases
Before you arrive
→Daily digest prepares the evidence and suggestions.
You talk and plan
→Opening reflection is noted. You write everything after it.
You prepare and finish
One command saves the conversation and dispatches two audios.
Your only writing surfaces: Notion for the plan, Notion Calendar for time blocks, Google Sheets for tracking. Local archives and Pinecone are handled by the future skills, not by you.
Open Archify: Evening context and information flow ↗
Explore diagram here
PROCESS 01
daily-digest
17:30 scheduled preparation → one ready daily task
- Trigger / conditions
- The future daily scheduler creates or resumes one pinned Codex task for the date. Target window: previous 24 hours, Europe/Budapest.
- Inputs / sources
- Approved Daily Plans snapshot; Google Calendar calls; Main Tasks DB Deadline entries; visible dashboard goals/projects/KPIs; Computer History and Codex extracts; Missive human email threads; WisprFlow meeting transcripts.
Gather evidence with Luna Max workers
→Deduplicate and compare with plan
→Write digest + proposed tomorrow
→Open planning pages
- Outputs / storage
- Daily Digests page, private email Markdown attachment, Proposed next-day Daily Plans page and pinned task. Calendar and tracker are unchanged.
When reality differs: Missing source coverage is explicit. “Unplanned” may be necessary work. A missing prior plan cannot produce a made-up adherence score. Reruns reuse existing date records.
Responsibilities and reasoning
Computer/Codex evidence, email evidence and meeting evidence are separate worker responsibilities. The orchestrator reads the visible dashboard direction, not every row in all databases. Calendar events are read from their real sources; Notion Calendar is their combined presentation.
Open Archify: Daily digest workflow ↗
Explore diagram here
PROCESS 02
plan-tomorrow-and-reflect
Same Codex task → ready voice context
- Trigger / conditions
- You invoke the skill in the digest task. It creates the completion goal and resumes a checklist if already started.
- Inputs / sources
- Today’s digest, prior saved plan, tomorrow’s proposal, dashboard direction, daily routine and agenda. Dated personal memory plus Ryan Doris/Sam Ovens material can be retrieved when relevant.
Read current records
→Load essentials + source index
→Open five planning surfaces
→Start verbal checklist goal
- Outputs / storage
- Voice agent has the current plan and evidence. Sidebar opens digest, dashboard, next-day plan, Sz II Sheet and checklist. Retrieved history is cited by date/source.
When reality differs: Available does not mean loaded. Stale Notion state must be refreshed. Missing memory is disclosed, not filled with invented patterns. Completion requires your verbal confirmation.
Responsibilities and reasoning
Always loaded: the current operational packet. Retrieved as needed: full prior conversations, personal notes, journals and mentor content. The agent has access without flooding every conversation with all history.
Open Archify: Voice planning and manual-writing boundary ↗
Explore diagram here
PROCESS 03
Live evening conversation
Opening notes → manual writing → preparation
- Trigger / conditions
- Voice starts. The transition out of the opening reflection is explicit, so the agent knows when to stop writing.
- Inputs / sources
- Agent’s digest summary and your reaction/brain dump, then your live narration while editing Notion, Notion Calendar and Sheets.
Summarize + hear brain dump
→Write reflection bullets
→You edit plan/calendar/tracker
→Confirm preparation checklist
- Outputs / storage
- Opening reflection bullets in Daily Digest. Your manual next-day plan in Daily Plans, time blocks in Main Tasks DB via Deadline and Google Calendar, tracking entries in Sz II. Full conversation capture continues.
When reality differs: No later live plan edits by the agent. Readback is allowed. A checkbox preview is not physical proof. Spoken intention is not completion. Adaptations are explicit.
Responsibilities and reasoning
You keep authorship of the plan. The agent listens, identifies contradictions, prompts missing steps and offers coaching. Stopping live notes does not stop the full transcript.
Open Archify: Voice planning and manual-writing boundary ↗
Explore diagram here
PROCESS 04
planning-session-done
One explicit command → saved day and audio briefs
- Trigger / conditions
- You invoke it after planning and preparation, before gym/sauna. Read current checklist and provider records before saving.
- Inputs / sources
- Full available Codex conversation with timestamps, your manually saved final plan, checklist confirmations, reflection notes, parked ideas and target date.
Archive transcript + plan snapshot
→Save Notion records + Pinecone
→Create two next-day audio briefs
→Invoke daily-audio-guides
- Outputs / storage
- Digest transcript toggle; linked Conversations record; dated local Markdown; Pinecone chunks; final plan snapshot; Ideas entries; Audio Guides entries audio-1-{{date}} and audio-2-{{date}} with bullet briefs.
When reality differs: Each output has its own save status. Local archive survives remote failure. Preserve your plan edits. Retry only missing work. Append late transcript tail with a cutoff, never claim future speech is already archived.
Responsibilities and reasoning
The exact digest toggle is “daily planning session full transcipt from Codex”. Conversations links to it instead of introducing a second editable transcript. Pinecone stores searchable chunks with source/date metadata. The audio writer receives the full transcript and workflow nodes.
Open Archify: Closeout, storage and dispatch ↗
Explore diagram here
PROCESS 05
daily-audio-guides
Saved plan + briefs → two usable Telegram audios
- Trigger / conditions
- Closing skill dispatches after the final plan and two target-day brief records exist. Fixed recordings must be available.
- Inputs / sources
- Final plan version, full evening transcript, two audio briefs, workflow nodes, coaching preferences, relevant Telegram/journal passages, personal memory and mentor retrieval. Sol Medium writes the scripts.
Sol Medium writes Hungarian scripts
→TTS generates narration
→Python assembles fixed + fresh parts
→Verify, store and send
- Outputs / storage
- Two Audio Guides records with full scripts, playable file links, measured segment timestamps, source-plan version and Telegram delivery receipt. Scripts become searchable as generated guidance.
When reality differs: No source plan means no invented agenda. Reuse good segments on retry. Decode output and verify joins/durations. “Sent” requires a provider receipt; it does not mean listened to.
Responsibilities and reasoning
The run track includes only tomorrow’s approved carryover work, not every unresolved task. All coaching uses grounded examples. The hero/alchemist tone is motivational imagery, not a promise of guaranteed results.
Open Archify: Audio 1: sources and assembly ↗
Explore diagram here
Open Archify: Audio 2: coaching, transition and meditation ↗
Explore diagram here
Open Archify: Audio 2: focus, NSDR and continuation ↗
Explore diagram here
What each audio segment is made from
Fresh narrationSupplied recordingYour saved plan
Audio 1 · Wake to Flow
Short intro
Fresh narration
Fresh narration
Final plan’s main outcome → why it matters → exact first actions. Coaching preferences set the tone. Aim to begin working within ten minutes of waking.
2-hour focus
Fixed recording
Fixed recording
30 Focus Intense.MP3 is exactly 30 minutes. Repeat four times. It follows the intro without another choice.Audio 2 · Run, reset and continue
| Sequence | Source and transformation |
|---|---|
| Run and mindset coaching | Personal notes/journals + relevant past sessions + tonight’s transcript + goals. Sol Medium selects useful grounded insights and writes fresh Hungarian narration. |
| Cold shower and desk transition | Approved routine gives the sequence. Narration cues the transition and reminds you to pause if not ready. |
| Remaining task briefing | Final next-day plan, including only carryover tasks you chose. No automatic addition of old unfinished work. |
| 3 minutes guided meditation | Fresh relaxation and visualization based on the desired day and approved plan. |
| 7 minutes meditation recording | Extract a disclosed seven-minute segment from the supplied 15-minute Brain.fm meditation. |
| Start cue → 2-hour focus | Fresh brief task cue followed by four repeats of the 30-minute focus recording. |
| Break cue → NSDR | Fresh transition then the complete Huberman recording. Actual duration: 10:42, despite its “10 Minute” title. |
| Restart → next planned focus | Fresh cue and another four repeats when the final plan includes this block. |
Where the information lives
| Information | Human-facing home | Automatic copy or search |
|---|---|---|
| Evidence and your opening reflection | Today’s Daily Digests page | Source-linked local digest/email Markdown |
| Tomorrow’s plan | Daily Plans, edited by you | Approved dated local snapshot for next day’s comparison and audios |
| Time blocks and calls | Main Tasks DB + Google Calendar, viewed in Notion Calendar | Read into digest and closeout snapshot, not re-entered by the agent |
| Habit/work/business tracking | Sz II Google Sheet, entered by you | Agent can read/check relevant values, no second tracker |
| Full conversation | Digest’s transcript toggle; Conversations record links to it | Dated local Markdown archive + Pinecone searchable chunks |
| New parked ideas | Ideas and Future Projects | Source/date link to original conversation |
| Goals, routines and principles | Planning Horizons; Knowledge and Direction | Read current versions into planning context when needed |
| Audio briefs, scripts and files | Audio Guides records + Telegram for listening | Private file storage, assembly manifest, delivery receipt, searchable scripts |
There is one editable plan. Pinecone finds relevant passages; it is not the authority for the latest plan. The local snapshot preserves what you approved. These roles avoid conflicting copies.
One example proves the whole loop
Observed and explained
Call preparation completed. Page unfinished. An urgent tracking repair was necessary unplanned work. A tool experiment may have distracted you, but the agent asks.
Tomorrow, chosen by you
Finish the page first. Schedule campaign inspection later. The first audio names that first step; the second reinforces the remaining chosen plan.
Open the dashboard’s labelled demonstration views to follow the related digest, plan, conversation, idea and two audio brief records. No synthetic audio is presented as a generated recording.
Inspect the Notion example →