L0product

Time + Mind

A solo founder wears every hat — Strategy, Production, Finance, Compliance, Technology — and runs the full Customer Journey. Productive CEOs theme their day around one hat to stop context-switching. Time+Mind closes the gap between WHICH hat to wear (driven by where the customer journey is weakest) and WHETHER you actually wore it.

768

Priority Score

Pain × Demand × Edge × Trend × Conversion

Customer Journey

Why should I care?

Five cards that sell the dream

1Why

The gap nobody measures.

What's your alignment score this week — and is it trending up?

The friction: Every builder makes 3 decisions before doing anything: what to work on, what context to load, what mode to be in. Costs 30-60 minutes daily. No language for cognitive modes — "busy" is the only word.

The desire: Plan in archetypes. Log reality. Close the gap. One number tells you if the week matched the plan.

The proof: The weekly review this PRD describes is the weekly review that shaped its own creation.

The stories that validate this

Picture

A split calendar — left side: clean archetype-colored blocks in a perfect week. Right side: same calendar with blocks scattered, overlapping, some missing. The gap between them glows. Cinematic, 16:9

2Evidence

One score. Four weeks. Trend.

Does seeing the gap change how you plan next week?

What we measure	Target
Alignment score (weekly)	> 70%
Dreamineering Yield	> 0.5 artifacts/hour
Sunday planning retention	> 60% at week 4

Performance thresholds

Picture

A trend line climbing over 4 weeks — 52%, 58%, 64%, 71% — each data point a Friday review. Dark background, the number glowing brighter each week. Cinematic, 16:9

3Platform

75% built. Last mile: wiring.

What's already built that you haven't wired yet?

Built	Wire	Missing
DB schema + Drizzle repo	Product page polish	CLI time-mind commands
7 server actions	Two-site bridge	Auto reality capture
26 client components	Empty states + errors	Alignment score algorithm

The maps that prove the platform

Picture

An architect's desk with 26 component cards laid out — most connected by lines, a few isolated at the edge. The missing connections glow red. Top-down, cinematic, 16:9

4Loop

Plan Sunday. Score Friday. Compound.

When your week ends, does your next week learn from it?

Without the loop	With the loop
Plan forgotten by Wednesday	Plan checked daily
No record of where time went	Reality captured automatically
Same pattern repeats	Pattern detected, plan adjusted
"Busy" is the only report	Alignment score is the report

The process that compounds

Picture

A feedback spiral — Sunday plan on the left, Friday score on the right, an arrow flowing from score back to plan. Each loop tighter than the last. Cinematic, 16:9

5People

One person. One week. One score.

What would change if you could name the mode before you start?

You're in this moment	You need
Quarter ends, can't name one artifact	Alignment score trending up
Day diverged, no record of how	Auto-captured reality blocks
Same pattern repeats every month	Friday review with pattern data

Hidden objection: "Another productivity tool I'll use for a week then abandon." The unlock: the instrument infers reality — no logging required.

Who we built this for

Picture

A solo builder at their desk on Sunday evening — calendar shows five archetype-colored blocks for the week ahead. A single number glows: their alignment score from last week. Cinematic, 16:9

1 / 5

Same five positions. Different seat.

The customer sees the dream. The builder sees the process. The DREAM layer is the plan. The REALITY layer is the proof. Both are the same loop — Time+Mind makes it visible.

Feature Dev Journey

How does this get built?

Five cards that sell the process

1Job

Close the gap between plan and did.

Can you state the struggling moment in one sentence?

Situation: Every builder makes 3 decisions before doing anything. No language for cognitive modes. "Busy" replaces "productive."

Intention: Dual-layer calendar where DREAM = plan, REALITY = actual. Archetypes name the mode. Alignment score closes the loop.

Obstacle: 75% built but not wired. CLI has no time-mind commands. If reality capture requires self-report, it fails at week 3.

Intent contract

Picture

A single card — the text reads 'When busy stops feeling like productive...' with archetypes as colored shadows behind the words. Cinematic, 16:9

2Stories

Every story validates value.

Does each outcome deliver what the customer expected?

VV Stories = Validated Value. Each story proves an outcome reduces pain, removes friction, or unlocks opportunity. Not "does code work" but "does the outcome matter."

Group	Stories	Validates
Does the plan hold?	S1-S3	Empty state, template, layers
Does reality get captured?	S4-S5	Logging, scoring
Does the loop close?	S6, S9-S10	Carry-forward, week-open, prime
Does the agent participate?	S7-S8, S11	CLI today, CLI score, mirror

Full story contracts

Picture

A test dashboard — rows of story IDs with trigger type badges (action, cron, hook), each with expected outcome vs counterfeit. Dark background. Cinematic, 16:9

3Build

13 features. 4 sprints. Solo first.

Which two features prove the thesis fastest?

Sprint	Ships	Proves
S0 (10d)	Calendar + planning + archetypes + logger	The solo loop works
S1 (5d)	Friday review + alignment score	The feedback changes behavior
S2 (8d)	Skill blends + yield + flow guard	The depth compounds
Park	Connection score	Solo proves itself first

Build order and architecture

Picture

Architecture diagram — 4 sprint blocks, features flowing between them. Built features solid, Gap features outlined. Cinematic, 16:9

4Agents

Five agents. Zero morning decisions.

What would you do with the 45 minutes you'd get back?

Agent	Trigger	Produces
Sunday Agent	Sunday evening	Pre-built IDEAL week
Morning Agent	08:00 or app open	Task + files + first action
Health Agent	Wednesday 09:00	Traffic light + 3 issues
Flow Guard	Real-time	Drift alert on mode mismatch
Friday Agent	Friday afternoon	Alignment score + 3 insights

Agent architecture

Picture

Five agent cards arranged in a circle — Sunday Agent, Morning Agent, Health Agent, Flow Guard, Friday Agent — connected by arrows showing the weekly cycle. Cinematic, 16:9

5Validation

Sunday planning dies or compounds.

What's the smallest experiment that proves behavior changes?

Kill signal: If Sunday planning stops after week 3, it's a chore. If alignment doesn't trend up over 4 weeks, seeing the gap doesn't change behavior. Stop building.

Risk	Severity	Mitigation
Manual logging kills retention	Critical	Auto-capture from plan-cli + commits
Planning becomes overhead	Critical	Template import: adjust, don't rebuild
Score is visible but behavior unchanged	High	Friday review with pattern detection

Who we test with

Picture

A kill switch on a dark panel — two numbers: '4 weeks' and '70%'. Below: 'If alignment doesn't trend up, the instrument isn't working.' Stark, minimal, cinematic, 16:9

1 / 5

The pitch is the shape. The flow diagrams prove the thinking. The VV stories validate the value.

Flow Diagrams VV Stories

Problem

Situation

A solo founder wears every business hat but has no system for theming their time. Context-switching between Strategy, Production, Finance, Compliance, and Technology costs 30-60 min daily and fragments deep work. Productive CEOs theme their day around one role — solo founders jump between all five.

Intention

A dual-layer calendar where the DREAM layer themes time blocks by business hat (driven by customer journey gaps) and the REALITY layer captures what actually happened. The evening prime asks: where are my customers stuck? The morning shows: here's your hat, here's your context.

Obstacle

S0 components built but not wired to product page. CLI has no time-mind subcommand. Human uses web, agent uses CLI — both paths must work.

Hardest Thing

If reality capture requires self-report, it will fail at week 3. The system must infer reality from plan-cli + commit timestamps.

Scorecard

Priority (5P)

4/5

Pain

4/5

Demand

4/5

Edge

4/5

Trend

3/5

Convert

Readiness (5R)

Principles4 / 5

Performance2 / 5

Platform3 / 5

Process2 / 5

Players2 / 5

What Exists

Component	State	Gap
DB schema (2 tables)	Working	agent_time_mind_optimisation_plan + agent_profile_timeblocks
Domain types/DTOs	Working	Entities, repository interface, Zod validation
Drizzle repository	Working	Full CRUD for week plans and time blocks
Server actions (7)	Working	getWeekPlan, create/update plan, get/create/update time blocks
Client components (26)	Partial	CalendarGrid, BlockEditor, AlignmentSummary, FlowStateVisualizer
Persistence hooks (2)	Partial	useWeekCalendar + useTimeMindPersistence with tests
Exploration pages (5)	Working	In design-system app, not product app
Product page (week)	Partial	WeekCalendarClient wired to server actions. Needs polish.
plan-cli time-mind	Missing	Agents need read/write blocks via terminal

Relationships

PRD	Contributes
Agent Platform	Agent identity + dispatch + session boot (Phase 0). Morning Agent depends on this.
Prompt Deck	Fractal pair: Time+Mind = WHEN to wear which hat. Prompt Deck = WHAT to hold in mind while wearing it. Same five positions (Customer Journey = Tight Five), different instrument.
Project Management	Plan-cli provides task timestamps that feed reality capture.

Kill Signal

If the user stops returning for Sunday planning after week 3, the instrument is a chore, not a tool. If alignment score doesn't trend up over 4 weeks, seeing the gap doesn't change behavior. Kill date: 2026-06-24.

Questions

If the system could eliminate the 3 morning decisions, what would you do with the 45 minutes you'd get back?

What's the difference between a tool that shows you the gap and a system that prevents the gap from forming?
If reality is captured from timestamps, what does that reveal about the weeks where plan-cli shows no advancement?
Which archetype does your actual work pattern reveal — and is it the one your role requires?
When the Flow Guard tells you you've drifted, what's the cost of ignoring it vs the cost of switching?