Time + Mind Navigation

Do the right thing in the right moment for the right reasons in the right spirit.

That's the job. And nobody has a tool for it.

The Job​

INTENTION without ATTENTION = Dreams that never ship. ATTENTION without INTENTION = Building the wrong thing.

The gap between IDEAL and REALITY is where value leaks. Every week. Every person. Every venture. You plan on Sunday with clarity. By Wednesday, reactive noise has eaten the plan. By Friday, you can't remember what you intended — only what happened.

The job: "I need to align what I dream with what I do — and close the gap weekly."

The hidden objection: "What if seeing the gap just makes me feel bad?" The dual-layer answers that — the gap isn't judgment, it's signal. Signal compounds. Judgment decays.

Demand-Side Jobs​

Every feature exists because someone is struggling to make progress. No struggle, no feature. These are the jobs — derived from how builders actually lose weeks, not how productivity gurus say they should spend them.

Job 1: Align Dreams with Reality Weekly​

Situation: Sunday evening. A founder sits down to plan the week. They have three ventures, a content pipeline, deep work that keeps getting displaced, and a nagging sense that last week was busy but not productive.

Job 2: Track and Close Daily Loops​

Situation: End of the day. A builder finishes a block of time. They need to log what actually happened — fast enough that they don't skip it, detailed enough that Friday review has something to work with.

Job 3: Review and Compound Progress​

Situation: Friday afternoon. The week is over. A builder needs to see: did reality match intention? Where did the gap appear? What pattern keeps repeating? What should change next week?

Job 4: Track Dreamineering Yield​

Situation: A builder invests 40 hours a week. How many artifacts shipped? What's the ratio? Is it improving?

Job 5: Enable Like Minds to Collide​

Situation: Two builders are working on overlapping intentions — but neither knows the other exists. Their calendars are private. Their dreams are invisible. The collision that would accelerate both of them never happens.

Personas​

Solo Dreamineer (Primary)​

25-45, tech-savvy, building something they believe in. Could be a founder, a creator, or a senior engineer with side ventures. They manage their own time. Nobody tells them what to do — which is both the freedom and the problem.

"I need to turn my dreams into artifacts without losing my soul to reactive noise."

They don't lack ambition. They lack a feedback loop between intention and attention.

Collaborative Builder (Secondary)​

Teams or co-founders who need shared intention alignment. Not just "who's doing what" (project management) but "are we pointed at the same dream and is reality converging?"

"The journey is better with people who resonate."

This persona emerges naturally once the solo tool earns trust. You don't build social features before the individual loop works.

Core Duality​

The instrument has two layers on one weekly calendar:

┌──────────────────────────────────────────┐
│           IDEAL LAYER (Sunday)           │
│  What you INTEND to do this week         │
│  Dream/Intention ←→ Build/Attention      │
│  Time categories: PROACTIVE / PASSIVE /  │
│    REACTIVE                              │
│  Strategic bet tags                      │
│  Daily themes (AIM Framework)            │
├──────────────────────────────────────────┤
│          REALITY LAYER (Daily)           │
│  What ACTUALLY happened                  │
│  Quick log: <30s per block               │
│  One-click "Same as planned"             │
│  Deviation capture                       │
├──────────────────────────────────────────┤
│         GAP VISUALISATION (Friday)       │
│  IDEAL vs REALITY overlay                │
│  Alignment score                         │
│  Pattern detection                       │
│  Dreamineering Yield metric              │
└──────────────────────────────────────────┘

Time Categories​

Every block is tagged:

Mindset Tags​

Each block carries a mindset flag:

The weekly rhythm alternates between modes. Too much dreaming without building = nothing ships. Too much building without dreaming = the wrong thing ships.

Feature / Function / Outcome​

Every row maps a feature to the function it performs, the outcome the user experiences, and delivery state.

North Star Metric​

Dreamineering Yield: > 0.5 artifacts/hour shipped.

Not hours logged. Not tasks completed. Artifacts shipped per hour invested. Because the world doesn't reward effort — it rewards what you put into it that others can use.

Success Metrics​

Awareness Levels​

Where the buyer sits determines what we build next.

Validation Stack​

Business Dev​

The capability only matters if it closes the loop from personal pain to recurring value.

Commissioning​

All components are pre-build. This is the specification layer — engineering builds against it.

Risks + Kill Signal​

Kill criteria:

1. Quick log > 30s average → KILL. The feedback loop dies if logging is friction.
2. No behaviour change — alignment flat for 4 weeks → PIVOT. If the score doesn't move, the tool isn't working.
3. Gap doesn't close — IDEAL/REALITY drift for 6 weeks → KILL. The instrument isn't producing adaptation.
4. Feels like a chore — user stops using → KILL. If they don't return for the Sunday plan, nothing else matters.

Shape Up​

Following the stage progression:

Appetite: 6-week cycle. Fixed time, variable scope. The solo Plan → Log → Review loop ships first. Social features, collision matching, and team views follow only if solo retention proves the core loop works.

V1 Philosophy​

Ship solo-first so the tool earns trust through personal transformation. No social features, no team views, no collision matching in v1. One person, one week, one calendar, one gap score. If that doesn't change behaviour, adding social won't save it.

The collision mechanics (Job 5) are the multiplier — but multiplying zero is still zero.

Currently Growing In​

This is a Mycelium capability, not a product for one venture. Any mushroom cap that needs intention/attention alignment can compose from this primitive. A betterpractice daily practice tracker, a stackmates team planning view, a touchforfun creative session planner — all instances of the same dual-layer pattern.

Next Steps​

1. Validate the Sunday planning ritual with 5 builders — does the IDEAL layer get filled?
2. Build the minimum quick-logger — can reality be captured in under 30 seconds?
3. Ship Friday review with alignment score — does seeing the gap change next week's plan?
4. Measure: do users return for week 2? Week 3? Week 4?
5. Only then: explore intention overlap discovery (Job 5)

Smallest move: One person. One Sunday plan. One week of reality logging. One Friday review. Does the alignment score change how they plan week two? That's the signal.

Context​

• Prompt Deck — The complementary instrument: Prompt Deck aligns WHAT matters, Time+Mind closes the gap between WHAT and DID
• Players — The ecosystem of beings who use the instrument — biological and phygital, each wearing different hats
• Situational Wisdom — What the closed gap produces: knowing which principles apply to THIS moment
• Culture — Connection and Resonance scores measure culture; culture builds community
• Jobs To Be Done — Demand-side thinking: what progress, not what features
• Validate Demand — Awareness levels and kill signals
• JTBD Interviews — Extract real jobs from real people
• Shape Up — Fixed time, variable scope
• VVFL Loop — The core feedback loop this instrument serves
• Time Management — Domain context for temporal alignment
• Energy Management — Peak hours and energy allocation patterns
• Meetings — Where time alignment meets collaboration
• Phygital Mycelium — The capability network this PRD belongs to
• Mushroom Caps — The ventures growing from this network
• Live Exploration — Current design explorations