Flow Diagrams
Seven maps. Each one answers a question. Each answer feeds the next question. By the end, the archetype calendar is named as an instrument in the system language.
What does success look like?
Four outcomes. Each proves a different layer of the thesis.
OUTCOME MAP — Time + Mind
═══════════════════════
┌─────────────────────────────────────────────┐
│ ALIGNMENT SCORE TRENDS UP OVER 4 WEEKS │
│ (The instrument changes behavior, not just │
│ shows data) │
└────────────────────┬────────────────────────┘
│
┌──────────────┴──────────────┐
│ │
┌──────────▼──────────┐ ┌──────────▼──────────┐
│ REALITY CAPTURED │ │ PLANNING RETAINED │
│ WITHOUT FRICTION │ │ PAST WEEK 3 │
│ │ │ │
│ Auto from plan-cli │ │ Template import + │
│ + commit history │ │ carry-forward = │
│ Zero manual log │ │ <10 min Sundays │
└──────────┬──────────┘ └──────────┬──────────┘
│ │
└──────────────┬──────────────┘
│
┌────────────────────▼────────────────────────┐
│ MORNING DECISIONS ELIMINATED │
│ Agent loads context in <90s. Human shows │
│ up and executes. 45 min/day recovered. │
└─────────────────────────────────────────────┘Outcomes defined. Where does time actually die today?
Where does time die?
The current flow. Every box is a decision that costs minutes. The gap between DREAM and REALITY is where value leaks.
VALUE STREAM — Current State (no instrument)
═════════════════════════════════════════════
WAKE UP DECIDE WHAT LOAD CONTEXT DO THE WORK END OF DAY
──────── ──────────── ──────────── ──────────── ──────────
┌────────────┐ ┌────────────┐ ┌────────────┐
??? ──────▶│ What to │───▶│ Open files │───▶│ Actual work │───▶ No record
│ work on? │ │ Read state │ │ (unknown │ of what
│ │ │ Remember │ │ mode) │ happened
│ 15-30 min │ │ context │ │ │
└────────────┘ │ 15-30 min │ └────────────┘
└────────────┘
WASTE: 30-60 min/day on decisions that repeat identically
LEAK: No record of mode, no comparison to plan, same pattern next week
VALUE STREAM — Target State (with instrument)
═════════════════════════════════════════════
WAKE UP MORNING AGENT EXECUTE REALITY LOGGED FRIDAY REVIEW
──────── ───────────── ─────── ────────────── ─────────────
┌────────────┐ ┌────────────┐ ┌────────────┐ ┌────────────┐
Prime ──────▶│ Task + │───▶│ Work in │───▶│ Auto from │───▶│ Alignment │
loaded │ files + │ │ named mode │ │ plan-cli + │ │ score + │
overnight │ first action│ │ (archetype) │ │ commits │ │ patterns │
│ <90 sec │ │ │ │ <30s/block │ │ <15 min │
└────────────┘ └────────────┘ └────────────┘ └────────────┘
RECOVERED: 30-60 min/day from eliminated decisions
GAINED: Mode awareness, pattern data, compounding alignmentValue stream mapped. How do archetypes become the unit of planning?
How do archetypes become calendar blocks?
The archetype stays pure. The skill blends. The calendar tracks. The gap teaches.
ARCHETYPE (pure ingredient) SKILL (recipe) TIME BLOCK (calendar)
───────────────────────── ────────────── ──────────────────────
Dreamer: divergent, expansive ──┐
├── Copywriting: [Mon 9-11am]
Engineer: convergent, focused ──┘ Dreamer 70% + Eng 30% Mode: Dreamer (planned)
Mode: Engineer (actual)
Realist: evaluative, sharp ───┐ Gap: mode mismatch
├── Score PRDs:
Philosopher: reflective, deep ──┘ Realist 60% + Phil 40%
Coach: facilitative, warm ───── Meeting Chair: [Wed 2-3pm]
Coach 70% + Dreamer 30% Mode: Coach (planned)
Mode: Coach (actual)
Gap: none ✓The archetype names the mode. But how does it flow through a week?
What does the weekly loop look like?
Plan Sunday. Live Monday-Friday. Score Friday. The review feeds the next plan.
SUNDAY EVENING MON─FRI FRIDAY AFTERNOON
────────────── ─────── ─────────────────
┌─────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ Set intention │ │ REALITY layer │ │ Alignment score │
│ Name 3 bets │──────────▶ │ Auto-captured │────────▶│ Dimension split │
│ Assign modes │ │ from plan-cli │ │ Pattern detection│
│ Prime tomorrow │ │ + commit history │ │ Yield metric │
└─────────────────┘ └──────────────────┘ └────────┬─────────┘
▲ │
│ │
└────────────────────── FEEDBACK ───────────────────────────────┘
(template carry-forward)The loop runs weekly. But where does data flow between human and agent?
How do five agents eliminate morning decisions?
Five agents. One job: the human shows up and executes.
┌─────────────────┐
│ SUNDAY AGENT │
│ Philosopher → │
│ Dreamer │
│ Pre-build IDEAL │
└────────┬────────┘
│
┌──────────────────┼──────────────────┐
│ │ │
▼ ▼ ▼
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ MORNING AGENT │ │ HEALTH AGENT │ │ FLOW GUARD │
│ Engineer │ │ Realist │ │ Realist │
│ 08:00 trigger │ │ Wed 09:00 │ │ Real-time │
│ Task + files + │ │ Traffic light + │ │ Drift alert on │
│ first action │ │ 3 top issues │ │ mode mismatch │
└──────────────────┘ └──────────────────┘ └──────────────────┘
│ │ │
└──────────────────┼──────────────────┘
│
▼
┌─────────────────┐
│ FRIDAY AGENT │
│ Philosopher │
│ Alignment + 3 │
│ insights │
└─────────────────┘Agents coordinate. But what does the user actually see?
How does the user move from pain to performance?
Two sites, one bridge. The planning docs teach. The product measures.
PAIN-TO-PERFORM JOURNEY
──────────────────────
Pain │ "Where did the week go?"
│ Planning docs teach why cadences matter
▼
Awareness │ Reads planning docs, sees cadence table
│ Docs link to /calendar/week (not prototype)
▼
First Value │ Signs in, imports template
│ First IDEAL week in <5 min (not blank grid)
▼
Habit │ Returns Sunday evening
│ Dashboard surfaces "Plan next week" as primary CTA
▼
Mastery │ Uses review + yield weekly
│ CLI access: plan-cli time-mind today/score
▼
Effortless │ Sunday Agent pre-fills from template + patterns
│ Adjust 2-3 blocks, not build from zero
TWO-SITE BRIDGE
───────────────
mm.dreamineering.com (Docusaurus) dreamineering.com (Next.js)
Teach the pattern Use the instrument
│ │
├── Planning index ──────────▶ /calendar/week
│ │
└── "Learn the method" ◀────── Dashboard cardNavigation connects the screens. But what's the build sequence?
What gets built in what order?
S0 proves the solo loop. S1 adds feedback. S2 adds depth. Connection is parked.
S0 (10 days) S1 (5 days) S2 (8 days) Park
──────────── ─────────── ─────────── ────
#1 Alignment score ◀─────── #8 Friday review
#2 Dual-layer calendar #6 Morning handoff #9 Skill blends #13 Connection
#3 Template import #7 Time categories #10 Yield metric
#4 Archetype tags #11 Flow Guard
#5 Reality capture #12 Peak hours
PROVES: Solo loop works PROVES: Feedback PROVES: Depth PROVES: Solo
changes behavior compounds firstQuestions
Does each diagram answer the question that feeds the next one — or does it answer a question nobody asked?
- If the archetype architecture is sound, why is every feature still Gap?
- Which agent in the team diagram is most likely to be wrong about its trigger?
- Does the two-site bridge create more navigation or less?