Clawsy, ten ways

F1 The day as a typeset page

The idea

• The day is a single typeset column: date as the title, one painting, the One Thing as the lead, everything else folded under ruled headings; Clawsy speaks only in a Margin beside the page.

What is genuinely good

• The masthead. Weekday kicker, 64px serif date, one italic conclusion ("Heat index 115 around noon. An indoors day."). This is the first mock of the ten where the page belongs to him and not to the software (P1, P4, P17).
• The lead. A 44px italic question with a field under it, and when answered it becomes the title of the day. One bold moment, exactly where P15 says the next action belongs.
• The hours row with the recurring-event triage inline (Did it, Move it, Cancel it) is the correct home for the Geico problem, stated in Gabriel's own 2026-07-31 words.
• Provenance is a neutral tag ("Voice memo, Aug 26"), never a filename (P12).
• The Margin: a time and author gutter, one note per run, a receipt row with Undo under any change, the evening ask in large italic. Chat as a margin of the page is the right metaphor for P19.
• The Ledger: "Committed 2", "Waiting for a yes 47, five at a time", word actions on hover, the cap printed as a sentence. It reads like Things 3, not like Jira.
• Not today lists five items with a reason each (P8), and "Paused while away" instead of blank habit cells (P13).
• Sunday edition: the week's plan as the lead he must write. Calm, correct.

What is wrong

• The tray on Today shows seven notes with three chip buttons each, 21 controls, above the briefs. Gabriel asked to be able to see every unreviewed capture; he did not ask for them all open at once on the day (P10, P15). The tray belongs folded with one note open.
• The page is very long. Plan, hours, tray, five briefs, watch, ledger, food, yesterday in three columns. On the phone it is roughly nine screens. P6 and P15 want conclusions and the next action, not a Sunday paper every day.
• Two mics on the phone: the lead's "Say it" button and the FAB (P7). The FAB also physically covers the goal line ("January 20..." hidden) and the tray chips at 390. That is a layout bug, not a taste call (P14).
• "Pushups 0" in the ledger reads as a miss count (P13). Blank is blank; say "Not yet".
• Chip order in the tray flips between notes (Journal it, Make a task on one; Make a task, Journal it on the next). Small, but it is the kind of thing that reads janky.
• The merge proposal box on the Ledger is Clawsy proposing inline. P2 says hold it for the batched question.
• "Four weeks have now opened with no plan" on Sunday counts misses (P13).
• The painting is a gradient placeholder captioned as a painting; fine for a mock, but the whole aesthetic leans on it. If the real watercolor is muddy, the page loses its one image.
• Desktop nav as a masthead bar is right, but Library hides Voice, Docs, Insights, Change history behind one word with no count; the Margin is the only place a failure surfaces.

Storyboard

• A stranger understands it: seven frames, each a real phone, captions describe what he does. The 5 AM notification is one line. Clear.

Would he use it

• 5 AM: yes. First screen is the date, the painting and one question.
• 2 PM on a walk: yes for the mic; no for the tray as drawn, too many chips under a thumb.
• 9 PM tired: yes. Struck-through One Thing, one journal line, Save. The best evening of the ten.

Scores

• Clarity 8: the page reads top to bottom with no internals; the length costs it.
• Restraint 8: type, rules and one accent; the inline tray breaks it.
• Delight 9: the masthead and the lead are the only mocks here that look like an object.
• Fit 9: honors P1 to P22 with two knowing bends (news down, sidebar gone), both argued.
• Feasibility 7: a long static page over the existing day JSON is doable; the Margin per day and the Sunday edition are new routes.
• Total 41.

• Idea: Clawsy becomes a calm typeset day page, with the day in the main column and the day's chat in a margin.
• Good: The One Thing lead, the ruled plan rows, and the "Not today" reasons feel genuinely editorial instead of dashboard-like.
• Good: The tray language is conservative: generated title, source, what Gabriel said, and explicit route choices.
• Good: "Reminder from August 18" is better than lateness shaming, and the off-work/travel suppressions are plain.
• Wrong: The mobile screenshot is still a long newspaper strip. It is tasteful, but it asks a tired person to scroll and scan too much, violating P14 and P15.
• Wrong: "Briefs", watch, ledger, food, yesterday, and receipts all compete after the tray. The hierarchy starts strong and then turns into a well-set wall.
• Wrong: The Margin is secondary in the composition, which weakens P19 even though the README names it correctly.
• Wrong: The storyboard depends on reading dense mini-pages. A stranger gets the concept, but not the exact flow without effort.
• Wrong: News still appears as a major editorial block. That fits the newspaper metaphor more than Gabriel's day, bending P10.
• 5 AM: Yes, if the first viewport is only weather, One Thing, and plan.
• 2 PM walking: Weak. Capture review exists, but the tray is down-page and not thumb-first.
• 9 PM tired: Mixed. The tone is right, but the page is too much to close.
• Clarity: 8 - the page idea is legible and the components are named plainly.
• Restraint: 8 - visually quiet, but structurally still too many sections.
• Delight: 7 - the editorial object has soul, especially the painting plus type.
• Principles: 8 - strong on P1, P2, P3, P4, P8, weaker on P14, P15, P19.
• Feasibility: 7 - mostly HTML/CSS and routing changes, but the margin plus receipts still need product work.

F1. The day as a typeset page

Concept, three sentences

• Today is one typeset column for one reader: the date is the title, one painting, the One Thing is the lead, and every section below is a ruled heading with the data folded under it.
• The agent's contribution is selection and layout, never prose on the page; its voice lives only in the Margin, a right-hand column (desktop) or a sheet (phone) that holds one message per run, his replies and a receipt under every change.
• Tasks become the Ledger, a page of lines sorted five at a time; the weekly review becomes the Sunday edition, a paper whose lead (this week's plan) is his to write.

Who it is for

• 5 AM, half awake: one notification line, then a page whose first act is a single question. Nothing to parse, nothing to decide except the lead.
• 2 PM on the phone, walking: the mic is one tap; what he said lands in the tray as three lines he actually said, with three choices per note. The page never files anything for him.
• 9 PM, tired: the One Thing gets struck through, one sentence goes in the journal, the ledger takes two taps. No score, no streak, no summary of what he just did.

Information architecture

• Surfaces: Today (page), Margin (chat, scoped to the day), Ledger (tasks), Journal, Sunday (weekly review), Library (docs, voice, people, lists, change history, settings).
• Desktop nav is a masthead bar: Clawsy, Today, Ledger, Journal, Sunday, Library, date arrows, Margin toggle. The 240px sidebar is gone; a page has a masthead, not a rail.
• Mobile keeps the settled 4-tab bar (Today, Chat, Capture, More) and the mic FAB (P16). Chat opens the Margin as a sheet over Today; More opens the Ledger, Journal, Sunday and Library.
• Today's order: masthead and weather sentence, painting, the One Thing (lead), goal and week plan line, the plan, the hours (with Not today folded), the tray, briefs, the watch, the ledger (habits), food, yesterday (folded), receipt line.
• What moved: news dropped below the plan and the tray, because the first thing on his page is his day (P15), not the world. Goals collapsed into one line under the lead (P11). Voice, Insights and Change history left top-level nav for Library and the receipt line (P1).
• What is gone: the general Chat tab as a room, the Triage / Committed / Snoozed / Done tab strip, the icon-row of five glyph actions per task, the greeting sentence and quote block, the "Everything else" heading, the hero's "Open this day" link.

Component inventory

• Masthead: weekday kicker, date as 64px serif title, dateline (place, weather, trip status), one italic conclusion sentence.
• Painting: full-column image with a caption; the only bold moment above the lead.
• Lead: kicker plus 44px italic question; inline field with Say it and Set; when set, the answer replaces the question and gets a time and Change link.
• Goal line: goal title plus "This week's plan: awaiting Gabriel" in one line.
• Plan row: margin time (Morning, Afternoon, 22:00), serif title, one-line dek with a neutral provenance tag, 44px check circle.
• Hours row: time and range, event title; a recurring event that keeps returning carries a triage strip (Did it, Move it, Cancel it).
• Fold: a ruled details row with a label, a count and a plus; used for Not today, earlier memos, yesterday's label, done this week.
• Why row: what was left off and the reason, two columns.
• Tray note: date, generated title, source badge, bullets he said, three chips (Make a task, Journal it, Dismiss). Memos and Signal notes share it.
• Brief: topic kicker, serif headline, one line, source links.
• Watch line: logo tile plus one-sentence verdict.
• Ledger cell: habit name, live value in serif, yesterday's value, one or two log chips; paused cells are dashed and say why.
• Food block: one sentence, Log a meal, the FDA label folded.
• Yesterday: three columns (Talked through, Built, Not recorded), folded by default on desktop.
• Receipt line: "Every change on this page has a receipt and an undo" plus Changes today, n.
• Margin: header, notes with a time and author gutter (Clawsy in accent, You in ink), the run's ask in large italic, a receipt row with Undo under any change, composer with mic. Sheet variant on phone.
• Ledger page: title, sections Committed, Waiting for a yes (five at a time, Next five), Later, Done this week (folded); task line with check circle, serif title, provenance and owner badge, word actions on hover (Today, Later, Done, Drop); merge proposal box; cap line.
• Task card: sheet from the bottom, title, provenance link to the memo, what he said, four labelled buttons, Drop as a text row.
• Sunday page: masthead for the week, this week's plan as the lead, The week in three columns, seven-day ledger grid, still in the tray, On the ledger with Sort five now.
• Recording sheet: elapsed time, waveform, one line saying where it goes, Stop.
• Notification: app tile, one line, nothing else.

Principles

• P1 honored: no ids, paths, run names or counts of misses anywhere; the janitor and markets runs do not appear on the page at all. Provenance reads "Voice memo, Aug 26", never a filename.
• P2 honored: the lead and the week plan render "awaiting Gabriel"; the tray files nothing until he taps; the merge box is a question, not an action.
• P3 honored: every plan line, tray note and brief carries its own context ("A read, not a workout, so being away from the rack does not block it").
• P4 honored: "Heat index 115 around noon. An indoors day." on top; 99 and the dates sit in the dateline; food is one sentence with the label folded.
• P5 honored: serif display, one painting, one rust accent, warm paper. Bent: the painting is a gradient placeholder for the watercolor.
• P6 honored: no headline sentence, no greeting, no quote, no open-questions block. Yesterday is three columns of facts, folded.
• P7 honored: the goal appears once (under the lead), the One Thing once, and the plan is not repeated in the Margin.
• P8 honored: Not today lists five items with reasons; every Margin change has a receipt and Undo; the receipt line closes every page.
• P9 honored: the Margin shows exactly one Clawsy note per run, and it names what is not on the page (the rack, the RSVP deadline) rather than restating it.
• P10 honored: Waiting for a yes shows five lines at a time; the cap of fifty is a line on the page; ideas are not on Today at all.
• P11 honored: goal (one line), plan (the plan), habits (the ledger cells) are three separate blocks with different shapes.
• P12 honored: the recording sheet says where the memo goes; the tray shows it with a time; the task card links back to the memo.
• P13 honored: reminders read "Reminder from August 18", not "16 days late"; paused habits say "Paused while away"; Done this week is folded, not scored.
• P14 honored: 44px targets on every chip, check, tab and button; the phone lead wraps its buttons under the field; no horizontal scroll inside a frame.
• P15 honored: the first screen is the question; five lines per decision on the Ledger; every fold restates its count.
• P16 bent, with reasons: news moves below the plan and tray (P15, lead with his next action). The desktop sidebar becomes a masthead bar (P17, a page has no rail). The tab bar, FAB and light theme stay.
• P17, P18, P19, P20, P21, P22: one bold moment per screen (the lead); task lines open as a sheet in place; the Margin is the day's only chat; the tray shows every unreviewed capture with date and title; ledger cells read live; every control is a word.

What this direction breaks

• The sidebar shell and the Library as a left rail: Docs, Voice, Insights, Change history move under Library.
• The Tasks tab strip and icon-row actions: replaced by sections, word actions and a card. Existing task deep links keep working but land on the card.
• The general Chat as a room: the Margin is per day; saved sessions move to Library. The markets and janitor run chatter does not belong in the Margin; it needs its own report link in Library.
• The greeting, the quote line and the "Open this day" header: removed.
• The check-in JSON's "headline" field is unused on the page; "chips" become the dateline; "open" items become tray notes or Sunday lines, never a section.

Steals

• FT Weekend and the Financier redesign: serif hierarchy, one column, rules instead of cards. https://www.poynter.org/reporting-editing/2014/financial-times-a-classic-redesign-for-the-digital-age/
• Apple Journal: reflection prompts as a single large question, entries dated and quiet. https://apps.apple.com/us/app/journal/id6447391597 and https://www.macstories.net/stories/ios-and-ipados-18-the-macstories-review/7/
• Things 3: headings inside a list, white space, one bold heading per view. https://culturedcode.com/things/features/
• Poke: one short proactive line per day and a background that follows the hour. https://poke.com/ and https://www.producthunt.com/p/poke-by-interaction-co/a-week-with-poke-review-a-promising-start-for-a-proactive-ai-assistant
• Sunsama's morning and shutdown rituals as the fixed shape of the day: the lead in the morning, Tonight in the evening. https://efficient.app/apps/sunsama
• Mobbin could not be used (paid plan required); the references above were read directly.

Open questions

• Should the Margin persist across days (a scroll of daily margins) or reset each morning with the page? The mock resets.
• Does the merge proposal on the Ledger count as Clawsy proposing, and should it be held for the evening question instead of shown inline?
• The painting: one per day from the weather, or one per place that changes only on travel?
• Sunday on the phone: the seven-day grid is 8 columns; it may need to become a per-habit sparkline row at 390.
• Where do the markets and janitor run summaries live once they are out of the Margin: a Library report list, or nowhere on the app.

F2 Clawsy as a thread

The idea

• Each day is a conversation: the day is pinned at the top, the morning brief, the memo card and the evening question arrive as messages, and every structured message is a real component he can act on in place.

What is genuinely good

• The question card: "What's your one thing today?" with his three committed items as the answers and a ghost "Something else" that opens the mic. Nothing is pre-picked, one tap, P2 and P15 in one component.
• Receipt lines under the morning message: "TRX, chest press and yard work pause while you're away" and "Standup and Buttons' tick slot hidden today. Show them". Suppression made loud in two lines (P8).
• Rooms. Markets and Building Clawsy get their own threads so the day never fills with 32-row option books (P19). This is the cleanest answer anyone gave to "chat is a quagmire".
• The Waiting-on-you sheet: grouped by week, each row a generated title, kind and date, accept and dismiss, a loud Retry card for a memo that could not be read, older ones folded with a real count (P20, P22).
• The seven-day strip with dots for days that have a thread; days named by what happened in them.
• The memo card: title, duration, bullets he said, "Linked to task", "Held for tonight". Conservative processing drawn as a component (P20).

What is wrong

• The Today tab is no longer the day. The plan, the hours, habits and food live behind a chevron on a pinned strip. Gabriel's 2026-08-11 direction was "make the actual Today content fill the screen". This inverts it (P16, P15: the screen must restate state, not hide it).
• Three mics on one phone screen: the composer mic, the Capture tab, and the mic inside "Something else" (P7).
• The 5:20 message is the headline sentence ("Charlotte at 99 with Google's ad-tech breakup off the table"), the very thing P6 removed from the page, now moved into a bubble. Moving prose from the page to a bubble is not removing it.
• "Watercolor" as a badge on the hero and "Good morning, Gabriel" over it: a process label and the greeting he asked to tone down (P5, P6).
• Desktop is three columns of chrome: rail, thread, day. It looks like Slack with a sidebar of dates. Nothing on the desktop screen is the bold moment (P17).
• A chat thread cannot hold a fold. Every day the day-strip, the pinned card, the receipts, the question card and the shelf chips stack before the composer; at 390 the composer is the eighth element down.
• Days named "Vision doc done" or "Quiet Tuesday" are Clawsy prose on the nav (P6).

Storyboard

• A stranger understands it, because everyone understands a messenger. The captions are long paragraphs, though, and describe process ("two receipts saying what was paused").

Would he use it

• 5 AM: yes, one message and one question.
• 2 PM on a walk: yes, the memo card with Accept is thumb-sized.
• 9 PM tired: yes, the queue card "1 of 6" with Skip tonight.
• Any hour he wants to see his day: he taps a chevron. That is the failure.

Scores

• Clarity 7: messages are clear; the day itself is hidden.
• Restraint 6: bubbles, cards, chips, strip, rail, three mics.
• Delight 7: the question card and the day strip are lovely; the desktop is not.
• Fit 7: P8, P19, P20 done best of anyone; P15 and P16 broken at the root.
• Feasibility 6: typed cards emitted by runs, per-day threads with search, rooms with caps. Substantial rework of the run contract.
• Total 33.

• Idea: Clawsy becomes one day thread with a pinned day card, typed messages, and structured cards for every action.
• Good: The 5:20 phone screen is immediately understandable: day strip, pinned day, one message, one question, composer.
• Good: The Waiting on you and memo cards have the right controls: accept, dismiss, undo, and source in place.
• Good: Desktop split view makes Today chat real instead of a hidden general chat.
• Wrong: It risks rebuilding the exact chat mess Gabriel complained about. P19 is honored by naming, but the lived surface is still chat-first.
• Wrong: Day thread, rooms, shelf chips, sheets, pinned day, and left rail are a lot of IA for one person.
• Wrong: The morning message repeats enough of the pinned day that P7 is not fully solved.
• Wrong: The green accent and rounded cards look polished, but the system feels more app chrome than inevitable object.
• Wrong: Feasibility is harder than it looks because runs must emit typed cards, rooms, per-day threads, search, and sheet states.
• Stranger: Understands the storyboard because chat is familiar, but may not understand room boundaries.
• 5 AM: Strong. One question in a familiar thread is workable.
• 2 PM walking: Strong. Voice and memo review are native to the surface.
• 9 PM tired: Good if the queue is capped; bad if the thread grows into a feed.
• Clarity: 7 - familiar pattern, but too many nested places.
• Restraint: 6 - many cards, chips, rooms, and messages.
• Delight: 7 - friendly and usable, less premium than F1 or F5.
• Principles: 7 - good P12 and P19, risky P7, P9, P10.
• Feasibility: 5 - typed generative UI and chat architecture are non-trivial.

F2: Clawsy as a thread

Concept

• Clawsy is one conversation per day, the way Poke lives inside iMessage: the morning brief, the afternoon memo card and the evening question all arrive as messages in that day's thread, and the day itself is a pinned card at the top of it.
• Every message from Clawsy that carries structure renders as a real component (a question with buttons, a memo card with accept and dismiss, a task card with four postures, a goal card with an empty slot), so acting on it never leaves the thread.
• The mic is the composer's primary mode; he narrates and the pinned day updates, with a one-line receipt and an undo under every change.

Who it is for

• 5 AM, in bed, phone. One message: a line, two receipts about what was paused or hidden and why, one question with his own committed items as the answers. He taps one. Done.
• 2 PM, on the phone, walking. The memo he recorded at 11 comes back as a card: generated title, four bullets he said, what was linked to which task, what was held. Accept or dismiss with a thumb.
• 9 PM, tired. The evening queue is one card at a time with three buttons; he can stop at any card. A two-minute voice note becomes a journal card in his words and the day closes with no grade.
• Desktop, any hour. Days and rooms on the left, the thread in the middle, the day on the right. He never has to choose between the day page and the chat.

Information architecture

• Day thread (Today tab). One thread per calendar day. Pinned strip at top (date, weather one-liner, trip chip, the one thing); tap it and the full day opens as a sheet in place. Below the strip: the thread.
• Rooms (Chat tab). A list, not a thread: today's day thread first with its unread count, then standing rooms (Markets, Building Clawsy), then earlier days by name, then All days (date picker plus search across every thread). Market checks and build notes live in rooms so the day never fills with them (P19).
• Capture tab. Opens the composer in record mode on whatever thread is open. Same control as the mic button in the composer.
• More. The library: Tasks, Journal, Docs, Waiting on you, Habits, Change history, Settings. Each opens as a sheet over the current thread, never as a navigation away.
• Shelf. Four chips above the composer (Tasks, Journal, Log, Waiting with its count). They open sheets in place. On desktop the same four sit above the composer.
• Finding last Tuesday. Three ways: the seven-day strip at the top of the day thread, the Earlier days list in Chat, and search in the left rail (desktop) or the Chat header (phone). Every day is named by what happened in it (its one thing, or a one-line summary of the day), never by a run name.
• What moved. Chat's flat scrollback of run output is gone; runs post cards into day threads or rooms. Tasks moved from a four-tab destination to a sheet plus in-thread triage cards. Voice moved from a page to the composer. Insights and Change history are rooms-in-waiting: not drawn here, they would be a room and a sheet respectively.
• What stayed. The 4-tab shell, the light theme, the approved day-page section order inside the pinned day (Goal, One Thing, Plan, Schedule, Habits, Nutrition, News, Portfolio, Reminders), the watercolor hero.

Component inventory

• Day strip: seven 48pt day buttons plus an All days calendar button; dots mark days with a thread.
• Pinned day strip: art thumbnail, date, one-line weather and trip, the one thing in accent. Tap opens the day sheet.
• Day sheet: the full day page as a bottom sheet (phone) or right column (desktop).
• Message: Clawsy avatar plus time, or right-aligned bubble for him. Clawsy prose is capped at one line; anything longer is a card.
• Receipt line: 13px line with a small icon, what changed and why, and Undo or Show. The only trace an agent write leaves.
• Question card: eyebrow, one question, two to four 44pt choice buttons, a ghost "Something else" that opens the mic.
• Memo card: title, duration and play, bullets of what he said, routing rows (Linked to task, Held for tonight), Accept and Dismiss.
• Queue card: one item of N ("1 of 6"), three choices, "Next:" hint, Skip tonight.
• Task card: one task, provenance link, four postures (Active, Someday, Done, Drop). Used five at a time.
• Goal card (weekly): goal title, seven-day dots, one honest line, the empty plan slot with Say or Type.
• Journal card: serif, his sentences only, an open-journal button.
• Room card (markets): eyebrow, one-line title, chips for the numbers, receipt for corrections, Full check link.
• Composer: 48pt mic, text field, send. Record mode swaps to a red stop button and a live waveform.
• Shelf chips: text chips with a count badge; open sheets.
• Tasks sheet: Active, Someday, Done segments; Undecided card with "Decide five now"; rows with one text control (Plan or Today).
• Waiting on you sheet: grouped rows (this week, month), each with a generated title, kind and date, accept and dismiss; a loud card for memos that could not be read with Retry; earlier memos collapsed with a real count.
• Log dialog: one habit, quick values, running total so far today, one Log button (not drawn; the storyboard shows the voice path that logs "happiness 7" with an undo receipt).
• Desktop rail: search every day, Days (named by content), Rooms, Library, Settings.

Principles

• P1 Nothing on any screen names a run, file, id or count of misses. Markets card chips are numbers he set rules on; the schedule receipt says "the schedule follows your clock", not a cron expression.
• P2 One Thing and This week's plan render "Awaiting Gabriel" and are answered only by him (question card, goal card). The memo card links to a task he already had; the musing is held, not filed.
• P3 Every card stands alone: the Geico card says when and that it recurs; the wedding row carries the date and place.
• P4 Weather is one sentence in the hero; the heat index number is behind the sheet. Markets cards show the verdict line first, numbers as chips, the page one click down.
• P5 One bold moment per screen: the watercolor day hero, or the serif one thing. Cards are calm.
• P6 Clawsy prose is one line per message; everything else is a card or a receipt. No "Yesterday:" line, no suggestions.
• P7 The morning message never repeats the pinned day. Rooms are the only place market checks appear.
• P8 Every write is a receipt with Undo; suppression is a receipt with Show them; unreadable memos are a loud card with Retry.
• P9 Four Clawsy messages on the storyboard day. Quiet days have one.
• P10 Active capped at 50 and labelled; undecided tasks arrive five at a time; ideas are not on any daily surface.
• P11 Goal card, habits grid and plan list are three components; habits are inputs.
• P12 Voice memo shows in the thread as his, comes back as a card, and the task it produced says "From today's memo".
• P13 Paused habits say why (rack is home). Reminders show since-dates, not "22 days late". The weekly card states four weeks without a plan once, as fact, and asks for one line.
• P14 44pt buttons throughout, 48pt day cells, mic always reachable in the composer and the Capture tab. Nothing scrolls sideways.
• P15 Every message leads with the action; two to four choices per decision; the pinned strip restates state so the thread never assumes memory.
• P16 Kept: 4-tab shell, light theme, mic, day-page order. Bent: the Today tab is now a thread with the day pinned, because P19 (today chat is the primary entry) and P12 (nothing evaporates) are better served by one surface than two.
• P17 to P22 Serif hero moments, tap-to-expand sheets, rooms keep the day clean, Waiting on you is one place with dates and titles, habits and nutrition read live at load, every control is a word.

What this direction removes from the current app

• The Chat page as a wall of run prose. Runs post cards; the general chat becomes rooms.
• The Tasks page's Triage 47 tab and the five-glyph icon row on every task row.
• The Voice page ("No voice memos yet") and the separate mic FAB: voice is the composer.
• The Today page as a separate scroll: it is the pinned day inside the thread.
• The hero quote of the day. Nothing in the evidence asks for it and it is prose on the page.
• Desktop day arrows in the header (the day strip and rail replace them).

What this direction would break

• The iOS shell embeds the web app; the Capture tab must open the composer in record mode on the current thread, not a Voice page.
• The per-day chat thread and the "day page" are today two routes; they become one route with a sheet.
• Runs must emit typed cards (question, memo, queue, task, goal, room) instead of markdown. Anything unrecognised renders as a one-line message plus an "Open" link, never as a paragraph.
• Search must span every day thread and room.
• The Google Sheet habits and nutrition must be readable at sheet-open time (P21), same requirement as today.

What it steals

• Poke: proactive agent inside a messenger, short turns, one-tap replies. https://techcrunch.com/2026/04/08/poke-makes-ai-agents-as-easy-as-sending-a-text/ and https://www.producthunt.com/p/poke-by-interaction-co/a-week-with-poke-review-a-promising-start-for-a-proactive-ai-assistant
• Dot: a day card that starts empty and fills as you talk; follow-ups with suggested options instead of open questions. https://diklein.com/on-the-design-of-dot and https://www.fastcompany.com/91142350/dot-an-ai-companion-app-designed-by-an-apple-alum-launches-in-the-app-store (also the warning: memory-only chat with no structure died)
• Vercel generative UI: the model picks a component from a fixed kit. https://vercel.com/blog/ai-sdk-3-generative-ui
• Geoffrey Litt on chat as fallback and GUI for repeated actions. https://www.geoffreylitt.com/2025/06/29/chat-ai-dialogue
• Things 3: calm rows, one control per row, Today and Someday as postures. https://culturedcode.com/things/
• Apple Journal: dated entries in your own words, prompts that are optional. https://www.apple.com/newsroom/2023/12/apple-launches-journal-app-a-new-app-for-reflecting-on-everyday-moments/
• iMessage and WhatsApp: pinned conversation, date separators, voice bubbles with waveform.
• Superhuman: sheets and commands over the list, never navigation away. https://superhuman.com/
• Mobbin: the MCP search returned a paid-plan error, so no Mobbin screens were used.

Open questions

• Does a Clawsy correction (like the deleted Micron record) belong as a receipt in the room, or should corrections be their own card type so they can be listed?
• Should the Building Clawsy room exist at all, or is code-session output something he only wants in the day's summary line?
• The day sheet on the phone hides the thread; is a split (strip expanded to half height) better for narrating over the day by voice?
• How many rooms before the Chat tab becomes the mess again? Proposed cap: five, with a receipt when a run wants a sixth.
• Reminders in the pinned day show a since-date; is that low pressure enough, or should they only appear in the evening queue?

F3 The day is a timeline

The idea

• Today is one vertical line from 5 AM to the last commitment; events, tasks, habits, memos and the three runs sit at their minute, a now line splits past from future, and chat is pinned to one row.

What is genuinely good

• The Shelf. Undated tasks with a check ring, a full title, a since date, "Place on a day" and "Someday" as words, the cap as "14 of 50", and a one-line receipt ("A second copy was merged into this one. Undo"). The best task list of the ten (P10, P18, P22).
• Moment chat: the row title stays in the header, entity chips are icon plus title. He never has to remember what the thread is about (P15, P18).
• The Week: seven short columns, "No one thing named" in italic, what was recorded in the footer, no colour scale. Honest and low pressure (P13).
• The hero sentence "99 and sunny in Charlotte. Walk before 9 or after 7." is P4 done right.
• Receipts under a run with Show anyway and Undo.

What is wrong

• The runs are on the line as rows: "Clawsy set the day", "Clawsy read your memo, 1 proposal", with a Receipts disclosure. That is the system narrating itself on his day (P1, P6). The runs are plumbing; the page should show their results, not their signatures.
• The 5 AM notification counts: "Three things you committed, three on the calendar, five set aside for the trip." Counts of what the run did (P1, P9).
• Habits pinned to invented times (meditation at 8:00, bupropion at 8:10) turn inputs into schedule (P11). Face pulls and TRX have no minute; the README admits it in Open questions.
• Typed dots in six styles (event, committed, done, habit dashed, memo filled, run ringed) need a legend to read. That is a dashboard's vocabulary (P17).
• "PAINTING OF THE DAY" as a label over the hero, in white on cream, barely legible. Process label (P5).
• "Good morning, Gabriel" in 40px white over a sunset gradient is the greeting he asked to drop, made louder.
• The line on the phone is long and every row has a different shape; scanning for the next action means reading the whole line. P15 wants the next action first, not at the now line halfway down.
• Removing the mobile FAB is argued from P7, but P16 names it as settled; the argument is fair, the change is still a bet against his stated preference.

Storyboard

• A stranger understands it, mostly. The line with run rows reads as a log, and the 5 AM frame needs the caption to explain the hollow run mark.

Would he use it

• 5 AM: the hero and the empty One Thing are fine; the run row under it is noise.
• 2 PM on a walk: the memo pin on the line is nice; the proposal card under it is one Accept, good.
• 9 PM tired: the evening sheet "Three things to close" with three buttons each is good, but it is a sheet over a long line.

Scores

• Clarity 6: the Shelf and Week are clear; the line needs a legend.
• Restraint 5: six dot types, run rows, a now line, a sunset hero with white type.
• Delight 7: the Week and the terracotta palette have real character.
• Fit 6: P1 and P6 broken by run rows on the page; P11 bent by timed habits.
• Feasibility 5: a compressed time axis with typed rows, per-row threads, a week view and a shelf is the largest rebuild here.
• Total 29.

• Idea: Today is a compressed time rail where commitments, calendar blocks, memos, habits, and receipts sit in order.
• Good: The now line is the sharpest single interaction in the direction. It tells Gabriel where he is.
• Good: Moment chat scoped to one row is a strong answer to dirty general chat.
• Good: The recurring Geico card correctly becomes a question, not a plan item.
• Wrong: The rail becomes a dashboard of object types: dots, rings, dashed habits, run rows, proposal cards, shelves, and receipts.
• Wrong: It bends P16 hard by replacing the approved day order with time order.
• Wrong: It foregrounds runs on the timeline, which is dangerously close to Clawsy internals even when written plainly, risking P1 and P6.
• Wrong: Mobile readability is fragile. The 390 view is visually competent but too dense for 9 PM.
• Wrong: News and portfolio become "Morning read", which is conceptually neat but more about what Clawsy read than what Gabriel needs.
• Stranger: Understands "day as timeline", but not all row types without learning the legend.
• 5 AM: Okay, but less calm than a single question.
• 2 PM walking: Good for memo pins.
• 9 PM tired: Weak. Closing the day becomes scanning a rail.
• Clarity: 6 - the metaphor is clear, the object grammar is not.
• Restraint: 5 - too many visual states and row types.
• Delight: 6 - the now line has life, the full page feels technical.
• Principles: 6 - strong P8/P18, weak P1/P15/P16.
• Feasibility: 5 - timeline state, moment threads, and scheduling edge cases are heavy.

F3: The day is a timeline

Concept

• Today is one vertical line of time, 5 AM to the last thing he committed to. Calendar blocks, committed tasks, habit checkpoints, meals, voice memos and the three agent runs all sit on that line at the minute they happen; a now line splits faded past from plain future.
• Nothing reaches the line without his hand or his calendar. Undated tasks live on a Shelf beside the day; a proposal from a memo sits on the line under the run that made it, until he accepts it.
• Chat is a conversation about one row: open it from a moment and it stays pinned there, so check-ins never dirty the general thread.

Who it is for

• 5 AM: one notification says what the day holds and asks the one question. Today already shows the line with his slot empty.
• 2 PM on the phone, walking: the memo he recorded at 11:03 is a pin on the line; the afternoon run leaves a signed note under it with one Accept button.
• 9 PM tired: the bottom of the line is a happiness number, a journal box, an unlogged dinner with a Log button, and the one thing left tonight. No summary, no score.

Information architecture

• Surfaces: Today (the line), Week (seven short lines), Shelf (undated tasks: Anytime, Someday, Done), Captures (every memo and note not yet accepted), Chat (general thread plus per-moment threads), Journal, Docs, Settings.
• Mobile keeps the settled 4-tab bar: Today, Chat, Capture, More. Capture is the mic. Week, Shelf and Captures live under More. The floating mic button is desktop only; on mobile it duplicated the Capture tab (P7).
• Moved: Tasks became Shelf (only what has no day yet). News and portfolio moved off the page body and under the 5 AM run as "Morning read" (P1, P10: they are what Clawsy read, not his day). Voice as a page is gone; memos are pins on the line and rows in Captures. Insights and its heat map are gone; Week shows what was recorded per day instead (P13). Journal entry for today is a row at the bottom of the line; the Journal page stays for browsing.
• Time on the line is compressed, not proportional: rows in order with gaps collapsed. It reads like a list with a clock, not Google Calendar (his direction on the schedule).
• Runs on the line: past runs show what they did with a Receipts disclosure; the next scheduled run shows as a hollow mark with what it will ask so far. Runs never place anything on the line.

Component inventory

• Hero: painting, greeting, one weather conclusion, one context chip. Only one chip.
• One Thing slot: serif title of the day, "Awaiting Gabriel" in italic when empty, Set it opens a sheet with his three committed items and a free field.
• Time rail: 56px time column, 2px axis, typed dots (event, committed, done, habit dashed, memo filled, run ringed).
• Now line: accent hairline with the time; everything above fades to 62%.
• Committed row: white card, 28px check ring, title, one-line note, goal link in accent.
• Calendar row: soft-fill card, calendar icon, title, end time and repeat rule.
• Habit checkpoint: name, value so far, Log button; no prose.
• Memo pin: waveform, generated title, length and where, status ("Read 2:00").
• Run note: "Clawsy did X" in accent, one sentence, Receipts and Morning read disclosures. Receipt lines are bold what + muted why + Show anyway / Undo.
• Proposal card: eyebrow "Proposed task", title, provenance line, Accept / Edit / Dismiss.
• Place row: dashed slot at the end of the line, "Place something from the shelf".
• Moment card: bottom sheet with the row's type and time, labelled actions, Talk about this, open in source app.
• Evening sheet: "Three things to close", one row per item, three labelled buttons each, Later and Close these.
• Recording sheet: live length, waveform, live transcript, Discard / Stop and keep.
• Shelf row: check ring, full title, since date and provenance, Place on a day, Someday. Cap bar "14 of 50".
• Place-on-a-day sheet: Today, Tomorrow, named day, Another day.
• Week column: day header with weather word, one thing, compressed items, footer of what was recorded.
• Moment chat pane: header with "About 10:00 PM" and the row title, pinned chip, entity chips with icon plus title.

Principles

• P1: no ids, paths or counts of misses anywhere; runs say what they did in plain words. Receipts hold the why.
• P2: One Thing and week plan stay "Awaiting Gabriel"; the 2 PM run outputs a proposal, not a task; only Place puts things on the line.
• P3: every row stands alone with a date and title; the Geico row says it repeats weekly since August.
• P4: "99 in Charlotte, heat index 115 right now. Walk after 7." Numbers behind the Morning read.
• P5: painting and a serif hero; terracotta accent; the rest is calm.
• P6: no headline sentence, no Yesterday block, no open-questions section. The run note is one line.
• P7: mobile FAB removed (Capture tab is the mic); Done tasks show time once; the calendar block and the plan item for the LinkedIn post are one row.
• P8: every run is a row with Receipts; suppressions list a reason and Show anyway; "Could not read: last night's evening run" is on the page.
• P9: the 5 AM notification asks the one question; the line is the Today it complements.
• P10: Shelf cap 14 of 50 with a bar; ideas are not on Today at all.
• P11: habits are checkpoints with Log; the goal shows only in the week header and as a link on a task; plan is the line.
• P12: memo pin at the minute; proposal names its memo; Captures holds everything unaccepted.
• P13: Week shows "No one thing named" in italic, no streak, no colour scale.
• P14: 44px targets everywhere, actions under titles on the phone, no truncation, no horizontal scroll.
• P15: the next thing is the first row after the now line; sheets ask three things at most.
• P16: bent knowingly. News leaves the top of the page (P1, P10). The day-page section order is replaced by time order. The 4-tab bar, light theme and desktop mic stay.
• P17 to P22: one bold moment per screen (hero plus One Thing), moment cards open in place, moment chat on the right half, Captures in one list, live values on habit rows, every control is a word.

What this breaks in the current app

• The Tasks page and its Triage 47 / Committed / Snoozed tabs and five-glyph action row.
• The day page's fixed section order (news, portfolio, plan, schedule, big 3, habits, nutrition).
• The Voice page, the Insights page, the commit heat map and the streak.
• The mobile floating mic button.
• The quote of the day in the hero.
• General chat as the place check-in traffic lands.

Steals

• Structured: the compressed vertical day with tasks and events on one axis. https://structured.app/
• Amie: tasks as first-class rows next to calendar blocks, day and week toggles. https://amie.so/
• Rise: a day drawn as a vertical curve with tappable moments. https://www.risescience.com/
• Sunsama: the morning and evening rituals as fixed bookends, and the overload bar. https://efficient.app/apps/sunsama
• Limitless / Rewind: a passive day timeline from explicit signal (memos, done tasks). https://rewind.ai/what-happened-to-rewind/
• Things 3: the calm list base and Anytime / Someday shelves. https://culturedcode.com/things/
• Poke: one short proactive message with a one-tap reply. https://techcrunch.com/2026/04/08/poke-makes-ai-agents-as-easy-as-sending-a-text/
• Mobbin MCP returned a paid-plan error, so no Mobbin screens were used.

Open questions

• Should habits without a usual time (face pulls, TRX) sit at their last logged time or in a small "any time today" strip above the now line?
• Does a task placed on a day with no time go at the top of the future or the bottom?
• Does the hero painting stay at the top of the line on desktop once the day is half over, or collapse to a strip?
• Week on the phone is seven stacked cards; is a horizontal 7-column strip worth the small type?
• Is the Morning read (news, portfolio) opened by default on desktop, or always collapsed?

Files

• storyboard.html, mocks.html: self-contained pages, built from src/ (shared.css, sprite, bodies) with src/build.mjs.
• shots/: storyboard and mocks at 1440 and 390, plus one PNG per figure (fig-*.png).

F4 Clawsy Desk

The idea

• Desktop first: the day on the left, whatever he opened on the right, one Cmd-K bar for saying, logging and jumping, and Tasks replaced by a keyboard Triage lane with four keys and a receipt ledger.

What is genuinely good

• The context pane. A task opens beside the day with Goal, From, Today, Reminder and Doc rows, entity links as icon plus title, a 2x2 action grid with labels, and a History ledger with Undo. This is the task card Gabriel described on 2026-08-17 (P8, P12, P18).
• Triage: one item at a time, "Deciding 6 of 47", four labelled buttons, Decided-just-now with Undo, "Up next" peek on the phone. Five-glyph rows are gone (P22, P15).
• Set aside as one disclosure row with a count and a reason per item (P7, P8).
• Habit tiles that say "away from rack" instead of blank (P13), and a food row with the running total against target and one Log control (P21).
• Density done with care: 44px rows, no truncation, one column on the phone that is not a shrunken desk.

What is wrong

• Keyboard hints everywhere. "J K move", "O change", "W set", "Z undo" chips sit in the plan header, the goal row, the One Thing, the schedule. Superhuman teaches one shortcut per row on hover; this prints them all at once. It reads as a cockpit, which is a dashboard with a keyboard (P17).
• "Triage 54" in the primary nav puts a queue count in front of him every time he opens the app. A count as a permanent badge is a nag (P13, P10).
• The painting is a 132px strip with text over it. The one image on the page has been reduced to a banner; P5 asked for a picture, not a chip.
• The 5 AM push is four sentences (P9).
• The bar's parsed preview ("Happiness 7. Today so far: nothing.") is good; "Today so far: nothing" is a miss count in disguise (P13).
• The phone is correct but plain: a list of grey rows with a serif title. Nothing on the phone is the bold moment.
• Two desktop mics (bar and chat composer), plus hold-space-to-talk, which the README admits collides with typing.

Storyboard

• A stranger understands it. The captions are terse and the frames are real. The Triage frame at 7 PM reads like work, which is honest.

Would he use it

• 9 AM at the desk: yes, this is the best desk of the ten. Cmd-K "one thing: finish the vision doc" is right.
• 2 PM on the phone: yes, the memo lands under the plan row it belongs to.
• 9 PM tired: Close-the-day sheet is fine, but Triage with J and K at 7 PM is the sort of thing he will do twice and then never again.

Scores

• Clarity 7: dense but legible; the key chips are the noise.
• Restraint 6: one green, calm type, then thirty kbd chips.
• Delight 5: competent Linear. No soul, his words.
• Fit 7: P8, P18, P21, P22 done well; P5 and P17 missed.
• Feasibility 7: a segmented nav, a right pane and a palette on the current React shell is a bounded job; local parsing of the bar is the risk.
• Total 32.

• Idea: Clawsy becomes a desktop workbench: day on the left, selected object on the right, command bar for capture, logging, and triage.
• Good: The split-pane task card is the strongest operational artifact in the set.
• Good: Labeled actions replace silent glyphs, directly fixing P22.
• Good: Keyboard triage plus undo receipts would make the 47-item mess actually clearable.
• Good: The right pane model honors P18 for tasks, memos, events, and chat.
• Wrong: The whole thing reads like an operator console. It is competent, but not quiet enough for a life companion.
• Wrong: The command palette risks making Clawsy feel like Raycast with a day page, not an inevitable personal OS.
• Wrong: Removing the desktop mic FAB is defensible, but still bends P16 and weakens the always-reachable feeling.
• Wrong: Mobile inherits the objects but not the premium quality. It feels like the desktop collapsed downward.
• Wrong: "Triage 54" is honest, but the count-heavy posture risks pressure, hurting P13.
• Stranger: Understands the desktop storyboard; the mobile one is more work.
• 5 AM: Acceptable, not tender.
• 2 PM walking: Good if Capture tab is primary.
• 9 PM tired: Strong for clearing decisions, weaker for reflection.
• Clarity: 8 - the workbench model is precise.
• Restraint: 7 - dense but mostly disciplined.
• Delight: 6 - useful, not emotionally compelling.
• Principles: 8 - excellent P8, P18, P22, weaker P13, P16, P17.
• Feasibility: 7 - most pieces map to current web patterns.

F4: Clawsy Desk

Concept

• The day on the left, the thing he is looking at on the right, one bar for everything he says, logs or opens. Desktop is the primary form: two panes, keyboard for every action, dense rows under one loud serif One Thing.
• Tasks becomes Triage, a workbench that clears the 47-item queue and the unreviewed captures with four keys and a receipt ledger, instead of a list with five bare glyphs per row.
• The phone is the same objects one column wide: the bar becomes the Capture tab, the right pane becomes a sheet, the triage list becomes a stack with four labeled buttons.

Who it is for

• 5 AM, asleep: one push over Today. The message says only what the page does not (weather in a sentence, which plan item touches the goal, the one question).
• 9 AM, at the desk: Cmd-K, "one thing: finish the vision doc", Enter. Never leaves the day.
• 2 PM, on the phone: the memo from his walk appears under the plan row it belongs to, by title, with Undo in the day chat. Older notes wait in Triage, not on the day.
• 7 PM, at the desk, tired but focused: evening question, Inbox lane (7 captures), then Tasks lane (47). J/K to move, A/T/S/D to decide, Z to undo. About three minutes.
• 9 PM, on the couch: one Close-the-day sheet. Check, log three habits, say a line for the journal. Unchecked stays open, no penalty.

Information architecture

• Desktop nav is three destinations in a segmented control: Day, Triage (with the count of undecided items), Library. The nine-item sidebar is gone; Journal, Docs, Voice memos, Change history, Insights, Settings live under Library and behind G-then-letter jumps.
• Right pane (480px) opens only when something is opened: a task, a memo under review, a calendar event, or the day chat (C). Escape closes it and the day takes the width back.
• The bar (Cmd-K) has four groups: Do (set One Thing, set week plan, add task, close the day), Log (habits, meds, food), Jump, and the default, Capture as a note. It parses before Enter and shows what it understood ("Happiness 7. Today so far: nothing.").
• Triage lanes: Inbox (voice memos and notes to self not yet accepted), Tasks (open, undecided), Committed, Snoozed, Done. Inbox routes per the capture router (task, calendar, idea, journal, list, dismiss). Tasks decide with accept, tomorrow, someday, drop, merge.
• Mobile keeps the settled 4-tab shell: Today, Chat (the day chat), Capture (the bar plus mic), More (Library plus Triage). Triage is also reachable from Capture with its count.
• Day section order kept from the approved page: painting and weather, One Thing, Goals, Plan, Schedule, Set aside, Habits, Food, News, Portfolio. One Thing is placed above Goals as the hero (see P16).

Component inventory

• Top bar: brand, three-item segmented nav with one live count, the bar field with mic and Cmd-K hint, Chat toggle with its key, avatar.
• The bar (palette): input with caret, grouped results, per-row key hints, footer with hold-space-to-talk.
• Context pane: header with type icon, key hints, body, footer; anchored ledger at the bottom.
• Task card: serif title, posture chips, note, key-value rows (Goal, From, Today, Reminder, Doc) with entity links (icon plus title), 2x2 action grid with keys, History ledger with Undo, ask-about-this-task composer.
• Decide card (Triage): source row, duplicate row with Merge, 2x2 decision grid, minor row (Remind, Edit, Pick a day), Decided-just-now ledger.
• Route card (Inbox): the evening question as the first message, six route buttons, Ask-me-later, Dismiss.
• Painting band: 132px watercolor strip with the weather conclusion in serif and one context chip.
• One Thing hero: serif 34px, set or "Awaiting Gabriel" in italic, goal chip and change key.
• Goal row: title, "This week's plan: Awaiting Gabriel", Set with key.
• Plan row: circle, title, one-line note that may carry a memo by title, time slot, focus bar and key hints on focus only.
• Schedule row with recurring triage inline: Did it, Not today, Cancel it.
• Set-aside disclosure: count plus reason per item, collapsed by default on the phone.
• Habit tiles: name, running value today, one Log control; paused tiles are dashed and say why.
• Food row: running total against target with one Log food control.
• News row: topic label, headline, one line. Portfolio card: logo letter, company, one-line verdict.
• Receipt row (chat): icon, what happened, entity link, Undo.
• Toast: decision plus Z undo.
• Phone: status bar, tab bar with center mic, sheet (task, close the day), triage stack card with 2x2 buttons and Up next peek, Capture tab with mic, chips in the same four groups, recording state with waveform and Recent memos.

Principles

• P1: no ids, paths, run names or counts of misses anywhere. History says "by the morning run", never a run id. The bar's footer never mentions a routine.
• P2: One Thing and week plan render "Awaiting Gabriel" until he sets them (5 AM frame). Runs file, never create tasks: the memo attaches to his existing task; six older notes wait for his key.
• P3: every row stands alone. "A read, not a workout, so the missing rack does not block it" instead of "reminder 19 days late".
• P4: "99 and sunny, heat index near 115 at noon. Stay in until evening." High and low are in the painting's tooltip, not on the page.
• P5: painting band, serif hero, logo letters on portfolio cards, one green. Dense but not grey.
• P6: no headline sentence, no Yesterday line, no suggestions section. The one message lives in chat, the page holds conclusions.
• P7: Set aside is one row, not a chip and a section. Done tasks are struck, not also labeled. The FAB is gone on desktop because the bar holds the mic.
• P8: every write has a receipt with entity and Undo (chat, task History, Decided-just-now ledger, toast). Set aside lists each item with its reason.
• P9: three messages in the day chat for the whole day, none restating the page.
• P10: open tasks capped at 50 on the progress bar. Ideas are never on the day; Inbox is the only place captures surface.
• P11: Habits are tiles with inputs, Goals is one row with the week slot, Plan is only the three he committed.
• P12: memo shows under its task by title; task card shows From and Today memos; Triage rows show their source icon. Dropped tasks keep their memo.
• P13: "5 of 47 decided", not overdue counts. Close the day: "Unchecked just stays open." Paused habits say why.
• P14: 44pt rows and buttons, tab bar with the mic center, no horizontal scroll at 390 (measured). Phone is one column, not a shrunken desk.
• P15: One Thing first, four buttons per decision, one card at a time on the phone, progress bar in Triage, Up next peek.
• P16 (bent, with reasons): sidebar replaced by a three-item nav because the lens is desktop-first and eight destinations diffuse attention (P10). Desktop FAB removed because the bar carries the mic (P7). One Thing moved above Goals because it is the next action (P15). Light theme, 4-tab shell, section slots otherwise kept.
• P17: calm sans base, one serif hero per screen (One Thing, the card title, the recording prompt).
• P18: rows open in the pane or a sheet, never navigate away. Entity links are icon plus title.
• P19: day chat opens beside the day with C, is one tap on the phone, general sessions sit behind a menu.
• P20: Inbox lane lists every unaccepted memo and note with date and generated title; each is checked or dismissed with one key.
• P21: habit tiles and the bar's Log rows show the running total today, read live.
• P22: every control is a labeled button with its key. No bare glyph rows. "Triage 54" counts exactly the undecided items (47 tasks plus 7 captures).

What this breaks in the current app

• The left sidebar and the Voice, Journal, Docs, Change history, Insights top-level pages as navigation targets (they remain as Library pages).
• The Tasks page with per-row icon actions and its four tabs; replaced by Triage lanes and one-item-at-a-time decisions.
• The desktop mic FAB; the mic moves into the bar and the day chat composer.
• The full-height hero painting with greeting and quote; replaced by a 132px band with the weather conclusion. The quote is dropped from the day.
• Voice page as a recording surface; recording is the Capture tab on the phone and hold-space in the bar on desktop.
• Chat as a single long thread; the day chat is per day, general sessions are separate.

Stolen from

• Linear Triage: single-key accept, snooze, decline on a queue, J/K movement. https://linear.app/docs/triage and https://linear.app/changelog/2021-06-29-linear-release-and-issue-triage
• Superhuman: Cmd-K palette that teaches the shortcut on every row, split inboxes as lanes. https://blog.superhuman.com/how-to-build-a-remarkable-command-palette/ and https://help.superhuman.com/hc/en-us/articles/45191759067411-Speed-Up-With-Shortcuts
• Raycast: one field that both searches and acts, natural language first. https://manual.raycast.com/quicklinks
• Things 3 Quick Entry: capture from anywhere with natural language dates. https://culturedcode.com/things/support/articles/2249437/ and https://culturedcode.com/things/support/articles/9780167/
• Sunsama: morning plan and evening shutdown as the two bookends of the day. https://efficient.app/apps/sunsama
• Notion Q&A: answers sourced from his own objects with links back, the shape of the ask-about-this-task composer. https://theaipicker.com/notion-ai-review/
• Mobbin could not be used (paid plan required on the MCP).

Open questions

• Does the bar parse locally (fast, deterministic verbs) or through the agent? The mock assumes local parsing with the agent only for captures.
• Hold-space-to-talk on desktop needs a real hotkey that does not collide with typing in the bar.
• The Inbox lane merges voice memos and Signal notes. Should memos with five bullets show the bullets in the pane before he routes them?
• Merge (M) needs a rule for which title survives and where the two sources go.
• Week plan (W) opens a pane for the goal; the Saturday weekly frame is not drawn.
• The painting band is a gradient placeholder; the real watercolor needs a crop that keeps the text legible.

F5 One card at a time

The idea

• Today is a short deck, not a page: each card is one thing that needs him now with a plain answer on it, and when the last card is answered the screen is a painting and one sentence.

What is genuinely good

• One decision per screen with a visible count ("3 of 6"). For ADHD at 5 AM and at 9 PM this is the truest reading of P15 in the set.
• The morning card: his own three plan items as choices, Set it, "Or say your own". Nothing seeded (P2).
• The memo card: "From your memo, 11:02, 4 min", four bullets he said, one proposal boxed with "Held until you say. Nothing was filed.", Accept, Edit, Dismiss. This is P20 as an object.
• The end card: "That is it for today. Four done, two moved to tomorrow. Nothing else needs you tonight." No grade, no streak (P13).
• "Nothing new to route" as a card: suppression is loud (P8).
• The reflect card with a real Skip tonight, and the Saturday card with Leave it empty.
• The fan (Done, Now, Later tonight) as the overview: progress without a score.

What is wrong

• The day page is gone. News, portfolio, habits and nutrition leave Today for Library. The section order approved on 2026-08-10 is replaced wholesale. That is P16 broken at the root with only P10 as the reason. He wants to see his day, not be walked through it.
• A deck can become a queue. Six cards at 5 AM is fine; the model has no fold, so a bad day is twelve cards and a count that reads as a to-do list with a progress bar.
• The count pill and card-stack edges are game chrome. "2 of 6 left" is the streak shape in a different coat (P13 borderline).
• Desktop is a phone card in the middle of a 1440 screen with a rail of rows on the left. Two thirds of the screen is empty; it is a mobile pattern stretched, not a desk (P14 in reverse).
• Task titles truncate with an ellipsis in the Tasks list ("Merge Talk to My Agent investor inte..."), the exact thing P14 forbids.
• "Did the AI-bubble piece go out at 22:00?" is asked at 10:15 PM on a card that also says "Move it to tomorrow 22:00". Good. But the calendar card before it ("Cancel the block") writes to Google Calendar from a swipe; the README flags it, the mock does not.
• Habits and nutrition are "logged in Library". Logging happiness by voice should be one sentence in the reply strip; the deck makes the most frequent input the least reachable (P21).

Storyboard

• A stranger understands it instantly. Eight frames, each a real phone, captions short and in his voice. The clearest storyboard of the ten.

Would he use it

• 5 AM: yes, one question on top.
• 2 PM on a walk: yes, the memo card is the best thumb interaction here.
• 9 PM tired: yes, one question, one optional line, end card.
• 2 PM at the desk wanting to see the whole day: no. He taps Day, sees a list, taps back.

Scores

• Clarity 8: each card is unambiguous; the day as a whole is not visible.
• Restraint 9: one card, one accent, four words per screen.
• Delight 8: the end card and the memo card are objects.
• Fit 7: P2, P13, P15, P20 exemplary; P16 and P21 broken.
• Feasibility 6: a card model with kinds, order, held state, per-card threads and run-time deck assembly is a new product under the current one.
• Total 38.

• Idea: Today is a short deck where Gabriel sees one card, one decision, and one reply surface at a time.
• Good: The 390 Today card is the cleanest mobile object in the set.
• Good: The card count, visible edges, and large actions solve P10 and P15 without explanation.
• Good: Memo review as one card with bullets he said is exactly the conservative capture shape P20 wants.
• Good: Desktop fan plus card plus optional chat is simple enough to implement and use.
• Wrong: It throws too much out of Today: habits, nutrition, news, and portfolio move away, which bends P16 harder than needed.
• Wrong: "Six cards today" can become a new nag if the deck is assembled too eagerly.
• Wrong: The end state risks feeling like a game loop rather than a day if the card stack becomes the only home.
• Wrong: It needs a stronger receipt layer. A deck can hide what changed if receipts are just replies.
• Wrong: The visual system is very close, but the phone frame and giant typography need a little more calm.
• Stranger: Very high. One card, one action, next card is obvious.
• 5 AM: Excellent. No scan required.
• 2 PM walking: Excellent. Capture and review are thumb-first.
• 9 PM tired: Excellent if the deck is capped and Skip is first-class.
• Clarity: 9 - the core interaction is obvious.
• Restraint: 9 - least surface area and least scanning.
• Delight: 8 - the best object quality, especially mobile.
• Principles: 7 - nails P10/P15/P20, bends P16 and needs stronger P8.
• Feasibility: 6 - card ordering and per-card threads are real work but bounded.

F5: One card at a time

Concept

• Today is not a page. It is a short deck: each card is one thing that needs Gabriel now, full bleed, with a plain answer on it, and he moves through them in order.
• Cards come only from explicit slots (his One Thing, his committed plan, the next calendar block, a memo he recorded, a note he sent himself, the one evening question, an optional reflection). Nothing inferred ever becomes a card without a Held label and his tap.
• When the last card is answered the screen is a painting and one line. Quiet days are short decks; an empty deck is a finished day, not a failure.

Who it is for

• Him at 5 AM: one push ("Six cards today"), one question on top. No scroll, no scan, one decision.
• Him at 2 PM on the phone: the memo he recorded on the walk is back as four bullets he said and one held proposal. Accept, Edit, Dismiss. Thumb-sized.
• Him at 9 PM tired: one yes/no question, one optional line for the journal with a real Skip, then the end card. Nothing else is allowed to appear.

Information architecture

• Today (deck): the primary surface. Deck bar with Day, a count, the date. One card. Reply strip with mic.
• Day (the fan): the deck laid flat, grouped Done / Now / Later / Tomorrow. Reached by tapping Day or the count. Tap a row to jump the deck to that card. This is the whole-day overview; it never replaces the card.
• Chat: a reply thread that lives on the card it was about. The general Chat tab stays for anything not about a card and never receives check-in traffic (P19).
• Capture: unchanged tab, full-screen recorder, one Stop and keep button.
• More: Tasks (one level down, capped list), Journal, Library (docs, voice memos, lists), Changes. The old Triage tab is gone; held items arrive as cards, a few per day.
• Desktop: the fan is the left rail, the card is center, chat opens on the right only when opened, pinned per card. Rail nav underneath.
• Runs and the deck: the 5 AM run builds the deck; 2 PM inserts memo and held-note cards behind the current card; 7 PM appends one question, one held note and the reflect card. Nothing is inserted at other times, so the deck cannot nag.
• What moved: plan, calendar, memo review, proposals, evening triage and reflection all moved out of sections and lists into one ordered stream. News, portfolio, habits and nutrition moved off Today entirely and live in Library; a portfolio item reaches the deck only as a chip on a card it is relevant to (Tax loss harvesting).

Component inventory

• Deck bar: Day button (44pt), count pill ("2 of 6", tap opens the fan), date.
• Card: kind label with dot, serif title, note, meta chips, action rows. Two card edges peek above it to show there is more.
• Morning card: the only card with the painting; weather as one sentence; his own plan items as choices; Set it.
• Plan card: one committed item, goal chip, size chip; Done / Later today / Drop it.
• Next-up card: one calendar block, shown only when it is next; Did it / Skip today / Cancel the block (the recurring-block triage question).
• Memo card: generated title, recording time and length, bullets in his words, one Held proposal; Accept / Edit / Dismiss.
• Held-note card: a note to self with its date, the two or three routes it could take, Drop it.
• Question card: the evening's single question; Posted / Not yet / Move it.
• Reflect card: one optional line to the journal; Save / Skip tonight.
• Change card: what a run did, why, and what it left alone; OK.
• Weekly card (Saturday): the goal and an empty plan slot; Set the week / Leave it empty.
• End card: painting, one sentence, links to Day and Library.
• Reply strip: text field plus mic, always visible under the card; on desktop the chat pane replaces it.
• Receipt in a reply: time, Undo, See the change.
• Fan row: state ring (done, now, later), title, source, time.
• Task row and opened task: tap opens in place; provenance is an icon plus a title; three word buttons.
• Recorder: mic, timer, waveform, one sentence about where it lands, Stop and keep.
• Lock-screen push: count plus the first card's ask, never the list.

Principles

• P1: cards carry his words and his items; no ids, paths, counts of misses. Run internals stay in the Change card as plain sentences.
• P2: the One Thing and the weekly plan are his slots with a real Leave it empty; proposals are labelled Held and file nothing until Accept.
• P3: each card is written to stand alone (dates, names, times on the card).
• P4: "Charlotte, sunny and 99. Day 4 of 9 off work." Numbers are one tap down in Library.
• P5: one painting per day on the morning and end cards; serif hero; one green.
• P6: no headline sentence, no Yesterday line, no open-question section. The question card is the only prose the agent gets, and it is a question.
• P7: one reply field per screen; Done appears once; the count means what it says.
• P8: every change is a card or a receipt with Undo; "Nothing new to route" is a card, so suppression is loud.
• P9: the push is a count and the first ask; it complements the deck, never repeats it.
• P10: a deck of six, not a list of 47; Open tasks capped at 50 and the cap is printed.
• P11: habits and nutrition are not cards; they are logged in Library and never render as prose. Goals appear as a chip on plan cards and as the Saturday card.
• P12: the recorder is one tap; a memo returns as one card with provenance; a task's From link opens the memo in place.
• P13: no scores, no streaks; Skip tonight, Later today and Drop it are first-class buttons; the end card says what was moved without judgement.
• P14: 390 frames, 48pt buttons, 44pt tab targets, mic always on screen, no horizontal scroll.
• P15: exactly one decision per screen, visible remaining count, done rows in the fan as progress.
• P16 bent: the day page's section order is replaced by an ordered deck (reason: P10 and P15). The mic FAB is folded into the reply strip because a floating mic over a card with its own mic is redundant (P7). The 4-tab shell, light theme and Today-first order stay.
• P17: calm sans body, one bold serif title per card, one painting per day.
• P18: tapping a fan row or a task row opens the card in place; links are icon plus title.
• P19: today chat is the reply strip; desktop chat opens beside the card only when opened.
• P20: every unaccepted memo and note is a card with a date and a generated title; Library holds the full list. Processing is bullets he said.
• P21: chips and the Library read the sheet and logs at load; nothing on a card is a baked count.
• P22: no bare glyphs; every control is a word; the count pill is the toggle for the fan.

What this breaks in the current app

• Removes: the day page as a scrolling document (hero, quote, Goals, One Thing, Everything Else, News, Habits, Nutrition sections all gone from Today).
• Removes: the Triage / Committed / Snoozed / Done tab bar and the five-icon action row on task rows.
• Removes: the floating mic FAB (folded into the reply strip).
• Removes: news, portfolio and the daily quote from Today; they move to Library and a card chip.
• Removes: the general chat as the place the runs talk; runs now write cards, and only the Change card carries prose.
• Changes: the morning message is one line with a count; the afternoon and evening runs insert cards rather than sending messages.
• Requires: a card model with kind, source, state and order; a per-card reply thread; a "held" state for proposals; run-time deck assembly.

What it steals

• The deck with swipe-to-plan and swipe-to-clear: To do cards by Frido, https://frido.app/apps/todocards/ and https://apps.apple.com/us/app/to-do-cards-by-frido/id6746710260
• Morning flashcard triage with a focus mode: Swipe it off, https://apps.apple.com/mx/app/swipe-it-off/id6747906845; TasksDeck, https://apps.apple.com/py/app/tasksdeck/id6581491386
• Today / another day / done as the only triage question, and one-key answers: Superhuman, https://blog.superhuman.com/email-triage/
• Optional reflection prompts with an easy skip: Apple Journal, https://www.apple.com/newsroom/2023/12/apple-launches-journal-app-a-new-app-for-reflecting-on-everyday-moments/
• Cards generated only from explicit routines, every card with a next action (the Pulse post-mortem): evidence/market-research.md, https://openai.com/index/introducing-chatgpt-pulse/
• The 2 PM and 7 PM inserts as human-in-the-loop moments (notify, question, review): https://zbrain.ai/ambient-agents/
• Mobbin search_screens was tried and returned a paid-plan error; no Mobbin references.

Open questions

• Deck order when a card is skipped: does Later today move it behind the next calendar card or to the end of the deck?
• How many held notes per day is the cap before the deck starts to feel like a queue (proposal: two, oldest first, the rest wait in Library).
• Does a recurring calendar block that he cancels from the card write to Google Calendar or only to the calendar-ignore list?
• Whether the Saturday weekly card should also carry last week's answered plan as a chip, or stay bare.
• Voice replies on a card: transcript shown before send, or sent raw with the transcript in the receipt.
• Desktop without chat open: is the reply strip under the card enough, or should the pane auto-open on the first reply.

C1 Inbox zero for a life

The idea

• Everything that arrived but was not accepted (memos, notes, proposed tasks, reminders, recurring-event questions, agent questions) waits in one Inbox; Today shows only what he chose.

What is genuinely good

• The route line under every inbox row ("Accept routes to Journal", "Answer changes the recurring item") tells him what a tap will do before he taps (P8, P22).
• The recurring calendar question as a card with Did it, Keep later, Cancel future (his 2026-07-31 words).
• The plan rows: AM, PM, 10p tiles with the title and one line. Simple and legible.
• "Clear" as the empty state, a painting and one sentence: low pressure, P13.
• Today Chat mock keeps the general chat separate with named sessions.

What is wrong

• The inbox content is the brief talking to itself. "Walking thought about conservative memo processing" with bullets like "Five useful bullets beat a document he did not ask for" is the design prompt rendered as his memo. A stranger reads it as nonsense; Gabriel reads it as the mock not having been built from his data (P1, P3).
• "Find why janitor proposals never reach you" is a task about the system's internals sitting in his inbox (P1).
• "Good morning, Gabriel" centred on the hero: the greeting he asked to tone down, in serif.
• The mobile mock is one fixed frame with the FAB covering the second plan row's status. The page at 390 is 900px tall: there is no mobile Inbox, which is the direction's whole surface (P14).
• Storyboard frames overflow the page; the 7 PM frame is cut off on the right. The frames are boxes with a tab strip, not phones.
• Inbox as a sidebar item with a red 5 is Gmail. Nothing in the visual language says a company that cares about objects made it; the cards, chips and green buttons are the default SaaS kit (P5, P17).
• Two mics on the phone (FAB plus Capture tab), and on the Inbox the mic sits in the row list.
• "Needs answer" as a chip on the 18:30 Geico event and the same event as an Inbox row: shown twice (P7).

Storyboard

• The inbox metaphor is universal, so yes, a stranger follows it. But the third frame's memo title is the prompt's own words, and the last two frames are clipped.

Would he use it

• 5 AM: yes, the day is clean.
• 2 PM on a walk: no mobile inbox was drawn, so unknown.
• 9 PM tired: the evening inbox with three left is the right shape.

Scores

• Clarity 7: the concept is legible in one glance.
• Restraint 5: chips, badges, borders, green pills; nothing removed.
• Delight 4: generic. "No soul" is the phrase he used for exactly this.
• Fit 6: P2, P8, P22 honored; P1, P3, P14 broken by the content and the missing phone.
• Feasibility 8: an inbox over existing entities with a review status is close to what exists.
• Total 30.

• Idea: Everything unaccepted goes to one Inbox, while Today stays clean and only shows accepted commitments.
• Good: The separation between committed work and arrivals is correct and needed.
• Good: The mobile Today screen is calm and readable, with One Thing and plan in the right order.
• Good: "Route label" and conservative memo card solve a lot of P12 and P20.
• Wrong: "Inbox zero" imports email psychology into a life system. It can create pressure, violating P13.
• Wrong: Today risks hiding too much. If Inbox is only a count, Gabriel may miss the very review surface he asked for.
• Wrong: The desktop mock feels generic: left nav, center cards, right detail. Competent, not premium.
• Wrong: News picks in the inbox are suspect. That puts world content into the same queue as personal commitments, weakening P10.
• Stranger: Understands the storyboard, though it reads as productivity app more than companion.
• 5 AM: Good. Today is clean.
• 2 PM walking: Good if Inbox is reachable from Capture.
• 9 PM tired: Mixed. Clearing a queue can be satisfying or stressful.
• Clarity: 8 - the model is plain.
• Restraint: 7 - one queue helps, but the queue metaphor adds pressure.
• Delight: 6 - useful but ordinary.
• Principles: 8 - strong P2, P10, P12, P20, weaker P13.
• Feasibility: 8 - mostly reorganizing existing task, voice, and proposal states.

C1 - Inbox zero for a life

Concept

• Clawsy gets one decision queue for everything that arrived but has not been accepted: voice memos, Signal notes, proposed tasks, reminders, recurring calendar questions, news picks and agent questions.
• Today stays clean: only Gabriel's commitments, calendar and accepted brief items appear there.
• The premium moment is clearing the inbox, with every item showing what it will become before Gabriel accepts it.

Who it is for

• 5 AM: Gabriel sees weather, news, portfolio, plan and the One Thing slot without a pile of raw arrivals.
• 2 PM on the phone: a walking memo can be captured quickly, then reviewed as five conservative bullets.
• 7 PM: recurring events and inferred tasks become one batched decision queue instead of plan pollution.
• 9 PM tired: the empty inbox is the reward, and recovery language stays calm.

Information Architecture

• Today: committed day page only, with a small Inbox affordance and no raw inbox rows.
• Inbox: new primary decision surface, desktop split with queue left and selected item right.
• Tasks: becomes committed work plus a someday shelf; no Triage 47 tab.
• Chat: Today chat is the primary entry for day changes; general chat stays session-scoped.
• Voice: remains the raw capture archive, but unresolved memos surface in Inbox for acceptance.
• More: unchanged mobile library shell for Docs, Journal, Voice, Insights, Settings and history.

What Moved

• Proposed tasks move out of Tasks triage and into Inbox until Gabriel accepts them.
• Recurring calendar events that need a decision move out of Today plan and into Inbox.
• Unreviewed voice memos move from a buried Voice page into Inbox with date, title and route.
• Agent questions move from scattered run messages into Inbox when they need a user decision.

Component Inventory

• Inbox split: two-pane desktop layout with queue, selected item detail and chat input.
• Route label: one-line destination promise such as Accept routes to Journal.
• Decision row: type icon, title, arrival time, destination and active state.
• Conservative memo card: generated title, five bullets, source label and accept/edit/dismiss.
• Recurring question card: explicit actions for did it, keep later or cancel future.
• Empty inbox reward: calm completion state that sends him back to Today.
• Today inbox affordance: count only, no raw items inside the day page.
• Committed list: task rows with checkbox, title, status and modal-open affordance.
• Someday shelf: passive parking area for work that is not a promise.
• Today chat rail: scoped chat that updates the day without dirtying general chat.

Principle Coverage

• P1: No ids, paths, run names, function names or column letters appear in the UI.
• P2: One Thing says Awaiting Gabriel; inferred work stays in Inbox until accepted.
• P3: Rows name the object plainly, such as Geico mileage keeps returning.
• P4: Today states conclusions first, with detail reserved for expansion.
• P5: The day retains the watercolor hero mood and gives Inbox a crafted split surface.
• P6: Agent prose is reduced to decisions, receipts and short chat turns.
• P7: Counts are not duplicated; the Inbox count is the one entry point.
• P8: Every inbox action shows destination and source before acceptance.
• P9: Run messages complement Today by saying what changed, not restating the plan.
• P10: One path: raw arrivals go to Inbox, accepted commitments go to Today or Tasks.
• P11: Habits, goals and plan stay separate; Inbox does not convert habits into plan prose.
• P12: Captures are routed once and retain source labels.
• P13: Snooze, dismiss and someday are normal actions, not failure states.
• P14: Mobile keeps the 4-tab shell, 44pt targets and always-reachable capture control.
• P15: The next decision is visually selected; only one item is open at a time.
• P16: The approved Today order, mic FAB, light theme and mobile shell remain intact.
• P17: Things 3 calm plus one bold hero moment anchors the visual system.
• P18: Items open in place as a card or split detail, never as a file route.
• P19: Today chat is the day-level chat entry.
• P20: Every unaccepted memo/note can appear in Inbox with title, date and check/dismiss.
• P21: Live-source language is assumed for habits and nutrition, not baked totals.
• P22: Actions use visible text where the consequence matters.

What This Breaks

• Existing Tasks triage would need to be split: accepted task inventory stays in Tasks, arrivals move to Inbox.
• Current Voice archive would need a review status join so every unaccepted memo appears once.
• Calendar recurrence handling needs decision states beyond a plain event list.
• Today would lose raw proposal and stale-reminder visibility, so Inbox must be hard to miss.
• The desktop app needs a right-side detail pattern that can also host Today chat.

References To Steal From

• Superhuman - fast inbox clearing, split reading pane, keyboard-feeling actions: https://superhuman.com
• Hey - screener concept and acceptance before something joins the main flow: https://www.hey.com
• Things 3 - calm task rows, today versus someday separation: https://culturedcode.com/things
• Sunsama - day-planning ritual and manual commitment boundary: https://www.sunsama.com
• Linear - crisp list density and selected-row detail: https://linear.app
• Raycast - command speed without turning every action into chat: https://www.raycast.com
• Poke - lightweight message turns for decisions: https://interaction.co
• Notion Calendar - recurring calendar questions need plain controls: https://www.notion.com/product/calendar

Open Questions

• Should Inbox be a top-level tab on mobile or live inside More with a badge?
• Does accepted memo content land in Journal immediately, or can it become a durable note when Gabriel chooses?
• What is the exact retention rule for dismissed news and agent questions?
• Should keyboard shortcuts exist on desktop for accept, dismiss, edit and snooze?
• Does clearing Inbox count dismissed items in the evening receipt?

C2 Receipts first

The idea

• Every agent action leaves a receipt with what changed, why, the source and Undo; Today shows only small marks where it was touched, and the ledger lives one tap away.

What is genuinely good

• The receipt row shape: one sentence, source, Undo. "Walking memo appended five bullets to the vision doc. Source: voice memo. No task created because it was a musing." is exactly the sentence P8 asks for.
• Failure receipts in amber, written as what could not be read ("Evening check-in did not run, so food and plan closure are unconfirmed").
• The undo-whole-run preview with "Will undo" and "Will not undo automatically" is a careful piece of thinking about external side effects.
• Tasks with a Source column and a provenance drawer that opens the memo in place (P12, P18).

What is wrong

• The receipt mark is a bare glyph beside "The One Thing", "Plan" and "Nutrition" headings, with a "3 receipts on this page" pill and a "Morning receipts" chip. P22 forbids bare glyphs, P7 forbids the same thing three ways. And why does the One Thing, which Clawsy is forbidden to touch, carry a receipt mark?
• The Receipts page is Change history renamed, and its first row is "Morning check-in wrote Today from live inputs. Why: daily routine. Source: calendar, reminders, weather, metrics, news, portfolio." That is the run describing itself (P1). "Janitor log could not be found" is a system failure surfaced to a person who should never hear the word janitor.
• "SOFT PAINTING" printed on the hero as a label. Process label on the page (P5).
• The mobile tab bar is four empty circles. The storyboard's phones have no icons at all. This is the "janky" he named.
• The storyboard overflows the page horizontally; the 2 PM frame is cut in half.
• Tasks keeps the Triage 47 / Committed 2 / Snoozed 2 / Done 18 strip as-is, and adds a Posture column that repeats the tab. Nothing was rethought (P7, the brief's "rounder corners" warning).
• The Today desktop is two columns of cards (Goal, News, One Thing, Schedule, Plan, Nutrition), a grid. That is the dashboard shape he rejected on 2026-07-19 (P17).

Storyboard

• A stranger understands "receipts", and the captions are short. The frames look unfinished, which undercuts the trust argument.

Would he use it

• 5 AM: the page is fine; the receipt marks are noise.
• 2 PM on a walk: Capture Review is a list with Accept, workable.
• 9 PM tired: a receipt summary is not what a tired person wants to read; he wants one question.

Scores

• Clarity 5: receipts are clear; the marks and pills are not.
• Restraint 4: three receipt affordances on one screen.
• Delight 4: placeholder icons, generic cards.
• Fit 5: P8 and P12 strong; P1, P7, P17, P22 broken.
• Feasibility 8: it is the current app plus a receipts model, which git already holds.
• Total 26.

• Idea: Trust is the primary layer: every agent action leaves a receipt with what changed, why, source, and undo.
• Good: This is the strongest answer to P8.
• Good: Receipt marks beside touched Today rows are elegant if they stay tiny.
• Good: Failure receipts are honest without leaking ids or logs.
• Wrong: Receipts are necessary infrastructure, not a full product direction.
• Wrong: The mocks still feel like current Today plus a ledger feature, not a new premium operating system.
• Wrong: The storyboard cards are narrow and repetitive, and some text is too small to read comfortably.
• Wrong: "Undo whole run" is scary language and risks exposing system mechanics, even if simplified.
• Wrong: It does not solve the 5 AM, 2 PM, 9 PM primary interaction as strongly as F5, F2, or C5.
• Stranger: Understands receipts, but not why this is the core product.
• 5 AM: Fine, but receipts are not the first need.
• 2 PM walking: Good for source trust.
• 9 PM tired: Useful for review, not enough for action.
• Clarity: 7 - trust model is clear.
• Restraint: 8 - keeps Today quiet.
• Delight: 5 - responsible, not lovely.
• Principles: 8 - excellent P8, decent P1/P12, weak as a P15 answer.
• Feasibility: 6 - user-facing undo and source chains are hard but required anyway.

C2 Receipts First

Concept

• Trust is the interface: every agent action leaves a plain receipt with what changed, why, source, and Undo.
• Today stays calm: it shows small receipt marks only where the day was touched, while the full ledger lives one tap away.
• The evening message becomes the day's receipt summary, not another plan or recap.

Who It Is For

• 5 AM: Gabriel sees Charlotte weather, real calendar pressure, his empty One Thing slot, and what Clawsy could not read.
• 2 PM on the phone: he sees every unreviewed capture, accepts or dismisses each, and every routed outcome links back to the memo.
• 9 PM tired: he sees a short receipt rollup, one batched question, and a normal recovery path for skipped or stale items.

Information Architecture

• Today remains the home surface and keeps the approved section order: weather, news, portfolio, plan, schedule, review, habits, nutrition.
• Change history becomes Receipts and moves from utility navigation to a first-class Library item.
• Tasks stays Tasks, but every row can open a provenance drawer with source, last touch, and Undo.
• Voice becomes Capture Review: unreviewed voice memos and notes-to-self live together until accepted or dismissed.
• Chat stays available from Today; desktop opens it beside the day, mobile keeps it one tap away in the settled 4-tab shell.
• More keeps Journal, Docs, Insights, Settings, and lower-frequency surfaces.

Component Inventory

• Receipt mark: tiny folded-paper glyph beside any Today row touched by an agent action.
• Receipt row: one sentence, source link, affected entity, and Undo button.
• Run bundle: grouped set of receipts with an Undo whole run action and a clear preview count.
• Source chain: task or note opens with the originating memo, the routed bullets, and the resulting entity link.
• Quiet summary: compact evening message with changed, failed, and needs-decision rows.
• Failure receipt: amber row for unread inputs or suppressed work, written as what could not be read.
• Capture card: generated title, date, route choice, Accept, Dismiss, and Open memo.
• Task provenance drawer: in-place task detail that shows source and last receipt without navigating to a file.
• Receipt filters: entity type, source type, day, and action result.

Principles

• P1: Honors it by hiding ids, paths, run names, and commits from the UI.
• P2: Honors it by keeping One Thing and weekly plan as Awaiting Gabriel until he acts.
• P3: Honors it by writing receipt rows as standalone sentences.
• P4: Honors it by showing conclusions first and moving inputs into details.
• P5: Honors it with a light editorial surface, watercolor placeholder, logos as text marks, and one green accent.
• P6: Honors it by cutting AI narration from Today and keeping receipts sentence-length.
• P7: Honors it by making receipt marks open history instead of duplicating receipt text on Today.
• P8: Honors it directly: visible change, source, reason, and Undo.
• P9: Honors it by making normal days show a small "3 receipts" link, not a feed.
• P10: Honors it by keeping Tasks bounded and ideas off Today.
• P11: Honors it by separating Goal, Plan, Habits, and Nutrition sections.
• P12: Honors it with source chains from task back to voice memo or note-to-self.
• P13: Honors it by treating overdue, failed, and unconfirmed items as state, not shame.
• P14: Honors it with 390 px mobile screens, 44 px targets, sticky bottom shell, and persistent capture.
• P15: Honors it by leading with One Thing, then a short plan, then expandable detail.
• P16: Honors it by preserving the settled Today order, light theme, mic affordance, and mobile tabs.

Breakage Risk

• Requires a product-facing receipts model, not just raw git log text.
• Undo whole run needs a preview modal and guardrails for calendar or notification changes.
• Existing Change history would need renaming and filtering, which may break saved links.
• Tasks must expose source provenance consistently, so old tasks without from need a clear "source unavailable" state.
• Today generation must emit receipt anchors per section without leaking internal ids.

References

• Linear activity feed and agent receipts: https://linear.app/
• Things 3 calm list density: https://culturedcode.com/things/
• Sunsama morning and shutdown ritual: https://www.sunsama.com/
• Notion Calendar compact schedule language: https://www.notion.com/product/calendar
• Apple Journal low-pressure reflection: https://www.apple.com/ios/journal/

Open Questions

• Is Undo whole run allowed when one receipt touched an external system, or should that split into Clawsy Undo plus external repair?
• Should receipt marks persist forever on Today, or disappear after Gabriel opens the day's receipts once?
• What is the exact fallback copy when a legacy task has no source capture?
• Should the evening receipt summary live in Today chat only, or also pin to the bottom of the day page?

C3 Daily note

The idea

• The day is a notebook page: Clawsy owns structured blocks, Gabriel owns paragraphs between them, journal and docs fold into the same calendar, and chat attaches to a block.

What is genuinely good

• The One Thing block: serif question, dashed "Tap to set it" field, "Awaiting Gabriel" in the header. Quiet and correct (P2).
• The day strip above the note (Mon 31 Travel, Tue 1 Work logged, Wed 2 Unclosed, Thu 3 Today) tells him where he is in the week without a calendar.
• Capture review as one list: generated title, date, "Five bullets kept. No task created.", Accept, Dismiss, Transcript (P20).
• The evening question with Posted, Keep unconfirmed, Snooze as words (P22).
• The reflection frame: one serif line, Save. The right size for 9 PM.

What is wrong

• The owner rail: "CLAWSY", "GABRIEL", "SHARED" printed beside every block. That is the write contract, an internal, on the page (P1). He should feel that a block is his; he should not be told who owns it in caps.
• "Done" and "Card" buttons on every plan row. "Card" is a word from the codebase, not from his day (P22); Done on an unstarted row at 5 AM is redundant with the check circle (P7).
• "SOFT WATERCOLOR PAINTING" as a kicker on the hero (P5, process label).
• Gabriel's block is an empty serif "LinkedIn post" with nothing under it: a heading with no content, twice (desktop and phone). Either he wrote something or the block should not exist.
• "Day 3 of no coffee." in the 9 PM reflection is invented content that appears nowhere in his data (P2 applies to the mock too).
• The notebook is a fine idea for durable notes; as the daily surface it makes Today an editor. He asked for structure on 2026-08-04 and 08-05 ("more structured", "not just a long text thing"), not a document to write in.
• Desktop and phone are the same cards in one column. The phone has no bottom bar in the mock crop, and the desktop hero is a banner with a label.

Storyboard

• A stranger understands it. Six clean phone frames, short captions. The best-executed storyboard among the C set.

Would he use it

• 5 AM: yes, the note opens on one question.
• 2 PM on a walk: the recording frame is fine; review is a list.
• 9 PM tired: yes, one question and one line.

Scores

• Clarity 6: the blocks are clear; the owner rail and "Card" muddy it.
• Restraint 6: calm cards, but every row carries two buttons.
• Delight 5: paper-coloured, but nothing on the page is an object he would want to look at.
• Fit 6: P2, P20, P22 mostly honored; P1 and P7 broken by the rail and the buttons.
• Feasibility 5: one notebook model spanning day, journal and docs with block ownership is a data-model rewrite.
• Total 28.

• Idea: Today, Journal, Docs, tasks, and chat collapse into one daily notebook with structured blocks.
• Good: The ownership rail, with Gabriel blocks and Clawsy blocks, is a useful guard against agent overreach.
• Good: The capture review block keeps memos visible with accept and dismiss.
• Good: It fits the file-based soul of Clawsy better than most directions.
• Wrong: It risks becoming a Notion clone. The app starts to feel like document management rather than a companion.
• Wrong: The notebook screen is dense and small, especially on desktop with rail, note, and chat all visible.
• Wrong: It blurs Today, Journal, and Docs, which may wreck surfaces that currently have different emotional jobs.
• Wrong: Tasks as embedded blocks are likely to become brittle and hard to query.
• Stranger: Understands daily note, but the product promise is less immediate.
• 5 AM: Good enough.
• 2 PM walking: Good for capture, but not as fast as F5 or C5.
• 9 PM tired: Good for reflection, weak for triage.
• Clarity: 7 - familiar notebook metaphor.
• Restraint: 6 - too many block types on one page.
• Delight: 6 - warm, but not as considered as F1 or F5.
• Principles: 7 - strong P1/P2/P12, risky P7/P15/P16.
• Feasibility: 5 - block ownership and task indexing are a lot of new machinery.

C3 Daily Note

Concept

• The day is the app: one calendar notebook where Today, Journal and Docs meet.
• Clawsy owns structured blocks; Gabriel owns paragraphs between them.
• Chat attaches to the day, a block, a task or a memo without dirtying the general chat.

Who It Is For

• 5 AM: Gabriel opens one note, sees weather, news, plan, schedule, habits and one question.
• 2 PM on the phone: a walking memo lands in review with a title, date, transcript and conservative routing.
• 9 PM tired: he answers one evening question, marks what happened, and writes a few lines.

Information Architecture

• Today becomes Notebook, centered on the current daily note.
• Journal collapses into the calendar notebook as dated writing blocks.
• Docs become the Library rail: durable notes, people, ideas, goals and references.
• Tasks become a filtered view over task blocks embedded in days and docs.
• Voice becomes Capture Review, focused on unaccepted memos and notes-to-self.
• Chat stays in the main nav, but its primary entry is inline beside the note.
• Change history becomes Receipts, opened from any block that changed.

Navigation

• Desktop: left library rail, center note, optional right chat panel.
• Mobile: settled four-tab shell: Today, Chat, Capture, More.
• Calendar strip sits above the note for yesterday, today, tomorrow and weekly review.
• In-place modals handle task cards, memo transcripts, nutrition detail and receipts.

Component Inventory

• Daily note shell: paper-like center column with live block slots and editable paragraphs.
• Block owner rail: small labels for Gabriel-owned writing, Clawsy-owned blocks and shared blocks.
• One Thing block: empty state says Awaiting Gabriel, with one Set action.
• Task block row: task title, source date, visible status, and labeled actions.
• Inline task modal: opens on row tap, never routes to a file path.
• Capture review block: every unaccepted memo with title, date, transcript and accept or dismiss.
• Nutrition label block: FDA-style summary with tabs and a failure state for missing logs.
• Habit input strip: sheet-backed inputs with today totals before the Log action.
• Schedule timeline: calendar events in the note, not a separate calendar clone.
• Receipt drawer: what changed, why, source and undo.
• Block chat: side panel on desktop, one-tap sheet on mobile.
• Library rail: notes, journal, goals, people and ideas as notebook facets.
• Task index: filtered task list over embedded blocks, capped and grouped.

Principles

• P1: No ids, paths, run names or file internals appear in the UI.
• P2: One Thing and weekly plan stay empty until Gabriel sets them.
• P3: Task rows use standalone titles like Finish the vision doc.
• P4: Weather and portfolio lead with conclusions; numbers sit in details.
• P5: The note uses a warm paper surface, a hero painting band, icons and color.
• P6: Agent prose is reduced to block conclusions, not narrative paragraphs.
• P7: Repeated counts and duplicate controls are removed.
• P8: Every changed block has a Receipt action and an undo affordance.
• P9: Run messages live beside the note and do not restate the whole screen.
• P10: The task index caps visible open work and keeps ideas out of Today.
• P11: Goals, habits and plan are separate blocks.
• P12: Captures appear once in Capture Review with provenance retained behind the modal.
• P13: Empty and stale states are neutral: Awaiting Gabriel, Unconfirmed, Paused.
• P14: Mobile controls are 44pt targets with reserved bottom-bar space.
• P15: The next action appears first, lists are short, details expand in place.
• P16: The approved day order, light theme, mic affordance and 4-tab shell remain.

Known Breakage

• Requires Today, Journal and Docs routes to share one notebook model.
• Requires task rows to render both inside notes and inside the task index.
• Requires block-level ownership so the agent cannot edit Gabriel paragraphs.
• Requires Capture Review to replace the current mostly-empty Voice page.
• Requires receipts to be queryable per block, not only in global history.

Steals

• Reflect: daily note as the default capture destination - https://reflect.app
• Logseq: blocks as addressable units inside a daily note - https://logseq.com
• Obsidian: local files, backlinks and calendar-navigation mental model - https://obsidian.md
• Things 3: calm task rows and low-pressure completion - https://culturedcode.com/things
• Apple Journal: private, warm, daily writing surface - https://www.apple.com/ios/journal
• Sunsama: day-planning ritual, but without auto-committing for him - https://www.sunsama.com
• Linear: tight issue-row density and clear action states - https://linear.app
• Notion Calendar: calendar context without rebuilding the whole calendar - https://www.notion.com/product/calendar

Open Questions

• Does Gabriel want Notebook as the nav label, or should Today remain the label?
• Should Capture Review live as a block on Today, a tab under Capture, or both?
• How much of a task's source transcript should be visible before opening the modal?
• Should weekly review be a dated notebook page or its own pinned notebook view?

C4 Goals down to today

The idea

• A goal spine runs through the day: live goal, this week's plan, today's linked task; every task carries a goal-fit label; Saturday gets a Weekly Focus page.

What is genuinely good

• The three-cell goal band (Live goal, This week, Today helps if) is a compact way to say P11 without prose.
• "Progress is shown as named evidence, not a percentage" is the right rule (P13), even if the page then breaks it.
• The evening question drawn as its own quiet card in the chat rail.
• "Ideas: browsed, not daily work. Promoting one means naming what it replaces." is a good sentence and a good rule (P10).

What is wrong

• Weekly Focus is a dark green banner with three rings labelled "Launch active", "Health steady", "Boundary watch". Those are invented statuses for goals he never defined (the README's own open question asks what milestones he wants). Rings, a status per lane, a colour-coded card grid under it: this is the scoreboard, the dashboard, the thing he said had no soul (P13, P17, P2).
• Every task row wears two chips ("Launch goal", "Milestone not named", "Serves none", "Errand") plus a third goal button on the right ("Launch", "None", "Boundary") plus Open plus Done. Five controls per row, and the chip repeats the button (P7, P22).
• "Good morning, Gabriel" and a lone italic "Find balance" under the weather. The greeting he asked to drop and a quote nobody asked for (P6).
• The page scrolls horizontally at 1440 (the document is 1472px wide). At 390 the FAB is the word "mic" in a circle. P14 twice.
• "Milestone not named" and "Serves none" as labels on his own tasks are quiet lectures (P13).
• "Charlotte heat painting" printed in the hero corner (P5, process label).
• Tasks keeps Triage 47 / Committed 2 / Snoozed 2 / Done 18 exactly as it is today, plus more chips. Rounder corners.

Storyboard

• A stranger understands the goal thread, but the frames are cut off on the right and the mic is a labelled circle. It looks unfinished.

Would he use it

• 5 AM: the goal band above the One Thing pushes the next action down (P15).
• 2 PM on a walk: a capture with a "Launch goal" chip and Accept, fine.
• Saturday: he would look at the rings once and close it.

Scores

• Clarity 5: legible rows, but the rings mean nothing.
• Restraint 3: chips on chips, a dark banner, three rings.
• Delight 4: the banner is bold in the wrong way.
• Fit 4: P2, P7, P13, P14, P17 all broken.
• Feasibility 7: mostly the current app with a goal-fit join; the rings need data that does not exist.
• Total 23.

• Idea: Today gets a strategic spine from live goal to week plan to today's committed work.
• Good: It correctly separates live goal, week plan, plan items, and habits.
• Good: The Weekly Focus surface is a useful place to move strategic thinking out of Today.
• Good: The mock shows Gabriel's launch goal in plain language.
• Wrong: "Scoreboard" is the wrong emotional model. Even softened, it pulls toward grading, violating P13.
• Wrong: Goal chips on many task rows can become another taxonomy burden.
• Wrong: "Today helps if" is close to Clawsy judging the day for him.
• Wrong: The visual design is ordinary dashboard UI with green cards and small icons.
• Wrong: It makes goals louder than the 5 AM One Thing, weakening P15.
• Stranger: Understands the goal hierarchy, but it feels like a work management dashboard.
• 5 AM: Mixed. Goal context may help, but it is not the next action.
• 2 PM walking: Weak unless capture stays separate.
• 9 PM tired: Risky. Goal framing can feel like pressure.
• Clarity: 7 - hierarchy is clear.
• Restraint: 6 - goal metadata spreads everywhere.
• Delight: 5 - functional, not premium.
• Principles: 6 - strong P11, weak P13, P15, P17.
• Feasibility: 6 - goal joins and weekly planning are manageable but not central.

C4 Goals Down To Today

Concept

• A calm day page with one strategic spine: live goal, current milestone state, this week's plan, then today's committed work.
• Today stays Gabriel's day by showing goal context as orientation, not a score, grade, or lecture.
• The full hierarchy moves to Weekly Focus, where Saturday asks "what are we doing this week?" against launch, health consistency, and day-job boundary.

For

• 5 AM: Gabriel sees weather, news, the launch goal, whether the week has a plan, and the question waiting for him.
• 2 PM on the phone: he sees unreviewed captures as conservative proposals tied to goals only when the link is explicit.
• 9 PM tired: he sees one evening question, a small reflection surface, and recovery controls without shame.

Information Architecture

• Today remains the home surface: weather, news, portfolio, goal orientation, One Thing, plan, schedule, review questions, habits, nutrition.
• Chat stays attached to Today: desktop opens beside the day; mobile remains one tap away.
• Tasks becomes Goal Tasks: the same list, but each row carries goal fit, milestone fit, or "serves none".
• Weekly Focus is new: a Saturday planning surface for launch, health consistency, and day-job boundary.
• Ideas stay out of Today: they live in Ideas and surface only in Weekly Focus as a small parked count with browse-only affordance.
• Habits stay separate from goals and plan: calm bars show consistency, not streaks.
• Change history remains the receipt layer, not a daily content layer.

Component Inventory

• Goal orientation band: compact Today module with live goal, milestone state, week plan state, and one linked task.
• Goal hero: bold Weekly Focus header for "Launch one new product by January 2027".
• Week-plan slot: empty state says "Awaiting Gabriel" with no seeded suggestion.
• Milestone lane: named or empty milestone rows under the live goal.
• Goal-fit chip: task row metadata for Launch, Health, Boundary, or Serves none.
• Conservative proposal row: capture-derived item with Accept, Dismiss, and Ask in Today chat.
• Habit consistency bars: low-pressure weekly bars, no scores and no miss counts.
• Receipt strip: "Changed because..." row with source title and undo action.
• Today chat rail: desktop split panel that complements Today instead of restating it.
• Goal task modal: in-place detail card with goal fit, provenance, reminders, and recovery actions.

Principles

• P1 honored: no ids, paths, run names, columns, or internal counts in visible UI.
• P2 honored: One Thing and week plan stay empty until Gabriel fills them.
• P3 honored: task rows include enough title and goal fit to stand alone.
• P4 honored: weather, nutrition, and portfolio show conclusions first, data behind expansion.
• P5 honored: the screen uses a warm light canvas, a Charlotte heat painting, icons, and one green accent.
• P6 honored: Today uses labels and receipts, not generated narration.
• P7 honored: task actions are not duplicated beside identical text commands.
• P8 honored: changed items show a receipt strip and undo.
• P9 honored: the storyboard shows one short message per pass, separate from Today content.
• P10 honored: ideas are parked outside Today and reviewed weekly only.
• P11 honored: goals, habits, and plan are visually separate.
• P12 honored: captures route once into explicit review rows with source titles.
• P13 honored: no grades, streak shame, or failure tallies; recovery is normal.
• P14 honored: mobile uses true 390px screens, 44px targets, and the mic remains reachable.
• P15 honored: the next action is visible before long evidence blocks.
• P16 bent slightly: goals appear higher than the approved day order, but only as a compact orientation band because this lens is explicitly goal-led.

Breakage Risk

• Today needs a goal-fit join across tasks, goals, milestones, and captures.
• Existing task rows need a second line on mobile, which changes list density.
• Weekly Focus needs first-class routing and cannot be a static report if it asks Gabriel to set the week plan.
• Goal progress cannot be a percentage unless Gabriel defines a measurable milestone.
• Ideas need a parked weekly view so they stop leaking into daily surfaces.

References

• Things 3: calm row density, deferment, and low-drama task surfaces - https://www.culturedcode.com/
• Apple Fitness+: one bold ring-like hero moment without turning the whole app loud - https://www.apple.com/apple-fitness-plus/
• Apple Health: gentle activity context and trend framing - https://www.apple.com/health/
• Sunsama: morning and evening planning rituals, manual commitment, overload restraint - https://www.sunsama.com/
• Gentler Streak: recovery-friendly consistency language - https://gentlerstories.com/
• Linear: crisp issue rows and status metadata without visual clutter - https://linear.app/
• Notion Calendar: quiet calendar density and clear day boundaries - https://www.notion.com/product/calendar

Open Questions

• What milestone names does Gabriel actually want under the launch goal?
• Should "serves none" be neutral, or should it trigger weekly cleanup when too many active tasks carry it?
• Should Weekly Focus write directly to the week plan, or open Today chat with the proposed wording?
• What is the canonical store for day-job boundary so it is not another invented tracker?

C5 Voice first, review second

The idea

• The mic is the fastest way in, and a dedicated Capture Review queue (backlog rail, one memo at a time, typed route chips, receipts) is where every capture is accepted or dismissed.

What is genuinely good

• The review card's route list: each proposed write is a checkbox with what it will do ("Metric log. Total today becomes 5 min.") and a type; "Inferred from a musing, so it waits for the evening question" is P2 as a row (P8, P20, P21).
• The conversation rule ("If another person speaks, their commitments never become Gabriel's tasks") is a real product rule drawn on the page.
• The backlog rail grouped Today 3, This week 12, Earlier 134, Conversations 25, Ambient 4 is the first honest picture of the 149-memo pile.
• The recording state with elapsed time and Finish is simple.

What is wrong

• The Commitments list has "S", "D", "R" as its row actions. Single bare letters. P22 was written about a glyph that silently snoozed a task; this is that glyph with less information.
• "Voice lane" on Today: "3 captures today, 149 waiting" with a "Latest receipt" and a "Review next" card and a "Conversation guard" card. The queue has moved onto the day (P10, P15) and "149 waiting" is a shame count in the corner of every morning (P13).
• The memo content is the brief again: "Do not turn the marketplace musing into ten tasks", "Happiness 7.2 and meditated 5 minutes" as bullets of what he said. Nobody says that on a walk (P3).
• Chip soup: "transcribed", "3 routes waiting", "metric", "journal", "proposal", "listening", "keeps going", "NEEDS YOU". Every state is a coloured pill (P17, P22).
• "Good morning, Gabriel" in serif on the hero, with the mic floating over the painting.
• The mobile tab bar is four rounded squares with no icons, and a black plus for Capture. Placeholder shell (P14, janky).
• The Commitments page keeps Triage 47 / Committed 2 / Snoozed 2 / Done 18 as-is.
• Desktop Capture Review is a three-pane workbench (rail, card, receipt column) that reads like a support tool.

Storyboard

• A stranger follows it: record, review, accept. The 9 AM frame's "Set One Thing?" card with Accept and Edit is odd (he typed it, why confirm it?).

Would he use it

• 5 AM: the day is there but the voice lane sits above the plan.
• 2 PM on a walk: the route checklist is good on the desk, dense on a phone.
• 9 PM tired: "One decision" with Make task and Dismiss is right.

Scores

• Clarity 5: the review card is clear; the chips and letters are not.
• Restraint 4: eight pill colours, a queue on the day.
• Delight 4: generic kit, placeholder tab bar.
• Fit 5: P8, P20, P21 good; P10, P13, P22 broken.
• Feasibility 7: a review status on memos and a queue page are close to what exists.
• Total 25.

• Idea: Voice is the primary input, but Capture Review is the trust surface before anything becomes work.
• Good: This is the clearest answer to Gabriel's memo-review complaint.
• Good: The review card with kind, title, date, bullets, routes, transcript, and conversation guard is strong.
• Good: Today remains calm while Capture owns processing state.
• Good: The storyboard correctly distinguishes live voice commands from raw memos.
• Wrong: The desktop Capture Review view is busy and looks more like an admin console than a personal companion.
• Wrong: "3 captures today, 149 waiting" is honest but heavy; it risks pressure and backlog dread, hurting P13.
• Wrong: The global mic dock is visually loud and competes with the settled Today page.
• Wrong: It is an input strategy more than a full Today system. It needs F5 or F1 to carry the daily object.
• Stranger: Understands the voice and review flow clearly.
• 5 AM: Good, but not meaningfully better than current Today.
• 2 PM walking: Excellent. This is its strongest moment.
• 9 PM tired: Good if it asks one decision and hides backlog.
• Clarity: 8 - voice first, review second is plain.
• Restraint: 7 - concept is restrained, UI has too many queue numbers.
• Delight: 7 - the voice moment has life, the review desk is utilitarian.
• Principles: 8 - strong P12/P20/P21, weaker P13/P17.
• Feasibility: 7 - routing review is required anyway, though transcript states need care.

C5 - Voice First, Review Second

Concept

• The mic is the fastest way into Clawsy, but Capture Review is where trust is earned.
• Today stays a calm day page; voice adds receipts beside the day instead of turning the day into a transcript feed.
• Chat is for live commands and questions; memos are source material that must be reviewed, routed once, and accepted or dismissed.

Who It Is For

• 5 AM: Gabriel sees the day page, the one morning ask, and a quiet capture status line.
• 2 PM on the phone: he sees exactly what the afternoon run heard, what it routed, and what still waits.
• 9 PM tired: he gets one batched decision, plus a reflection slot that can be spoken without becoming ten tasks.
• Walking: recording starts from any screen, shows an immediate receipt, and keeps moving if processing takes time.

Information Architecture

• Today remains the first tab with the approved section order: weather, news, portfolio, plan, schedule, review questions, habits, nutrition.
• Capture replaces Voice as the primary capture surface: record, processing, review queue, accepted history.
• Capture Review becomes a dedicated queue on desktop: left rail for backlog batches, center active memo, right routing receipts.
• Tasks remains Commitments: active promises only, with proposed tasks held inside Capture Review until accepted.
• Chat splits into Today Chat and General Chat: Today Chat can update the day; General Chat is for broader work and saved sessions.
• Mobile keeps the four-tab shell: Today, Chat, Capture, More.
• Docs, Journal, Insights and Change History stay in More or desktop sidebar; nothing moves into Today unless it changes the day.

Component Inventory

• Global mic dock: one primary mic control on every screen with idle, recording and processing states.
• Voice receipt card: immediate confirmation for spoken logs such as happiness 7.2 and meditated 5 min.
• Capture queue rail: backlog grouped into Today, This week and Earlier, with a real active count.
• Review card: generated title, date, kind, summary bullets, typed route chips, Accept, Edit and Dismiss.
• Transcript drawer: opens in place under the review card, never navigates to a file.
• Conversation guard: participant labels and a "Gabriel only" routing rule visible on conversation memos.
• Route chip: task, proposal, idea, list, journal, metric or unresolved, each editable before acceptance.
• Processing strip: visible status for syncing, transcription and routing without exposing run names or file paths.
• Today capture lane: compact "Review captures" and latest receipt beside the day page.
• Desktop review mode: one focused memo at a time with queue controls for the 149 memo backlog.
• Commitments table: Tasks renamed in the direction to emphasize promises, not ideas.

Principles

• P1: No ids, file paths, run names or column letters appear in the UI.
• P2: The One Thing and weekly plan say Awaiting Gabriel until he sets them.
• P3: Each plan item and capture title stands alone.
• P4: Day conclusions are visible first; sources, transcripts and numbers are behind expansion.
• P5: Light editorial base, painting-like hero, strong green mic moment and typed chips keep the product from feeling blank.
• P6: AI prose is limited to titles, five bullets and receipts.
• P7: Voice count appears once as a queue control, not as duplicate headings.
• P8: Every accepted route shows what changed and offers undo via receipt.
• P9: Morning, afternoon and evening each produce at most one visible message.
• P10: Capture Review handles one memo at a time and does not promote ideas into daily work.
• P11: Goals, plan, habits and voice logs are visually separate.
• P12: Every capture has a date, source kind, status and route outcome.
• P13: Dismiss and snooze are normal actions; no grades, scores or streak shame.
• P14: Mobile uses 44px controls, reachable mic, no horizontal scroll.
• P15: The main decision is always clear: set One Thing, review this memo, answer the evening question.
• P16: The four-tab shell, mic FAB, light theme and day-page order are preserved.

What This Breaks

• The existing Voice page cannot stay as an empty recorder card.
• The current Tasks tab cannot show proposed tasks beside committed tasks without stronger labels.
• The general Chat timeline can no longer absorb daily check-in traffic.
• The current day page needs a capture lane and modal expansion model.
• The backlog of 149 memos needs real grouping and keyboardable review controls.

Product References

• Wispr Flow, for system-wide low-latency dictation: https://wisprflow.ai/
• Monologue, for voice memo capture as raw material: https://monologueapp.com/
• Things 3, for calm commitment lists: https://culturedcode.com/things/
• Apple Journal, for low-pressure reflection: https://www.apple.com/ios/journal/
• Reflect, for voice capture into a daily note: https://reflect.app/
• Tana, for typed extraction from messy notes: https://tana.inc/
• Linear, for dense queues that still feel navigable: https://linear.app/
• Superhuman, for fast review triage and keyboardable decisions: https://superhuman.com/
• Notion Calendar, for restrained schedule presentation: https://www.notion.com/product/calendar
• Poke, for short agent turns inside a messaging habit: https://interaction.co/

Open Questions

• Should accepted capture routes be reversible one by one inside the review card, or only through the change receipt?
• Does Capture Review live under the Capture tab on mobile, or should Today show a persistent "Review captures" button when anything is waiting?
• What threshold makes a conversation memo safe to auto-title with participant names?
• Should ambient recordings be auto-dismissed after review, or kept until explicitly accepted or dismissed?
• Which voice logs should bypass review: metrics only, nutrition only, or anything with a direct spoken verb?