Validated Value Stories
Each story validates that an outcome delivers expected customer value — pain reduced, friction removed, opportunity unlocked. Not "does code work" but "does the outcome matter." Each card is a test contract: the footer shows the test artifact that must go GREEN.
Does the plan hold?
Template imports, layer separation, empty states that guide.
First sign-in to the calendar. Zero time blocks exist. No path from blank screen to first plan — the empty grid offers no guidance.
Get to a first meaningful weekly plan within 5 minutes, guided by a template.
Onboarding to first DREAM block in <5 min vs current infinity (no path exists).
Blank 7-column grid with no guidance. User stares at empty cells.
Sunday evening planning. DREAM layer empty for the target week. Building a plan from scratch takes ~2 min per block, 15+ min total.
Populate the week's plan from a proven template in one action, not block by block.
Template import completes in <30s vs manual block creation at ~2 min per block.
Import returns 200 with empty array. Silently succeeds but creates zero blocks.
Both DREAM and REALITY layers have blocks for the current week. Toggling between plan and actual risks data cross-contamination.
Switch between plan and reality views without one layer corrupting the other.
Layer switch renders in <200ms. DREAM blocks unchanged after REALITY edit.
Toggling layers merges or overwrites blocks from the other layer.
Does reality get captured?
Logging without friction. Scoring without self-report.
Mid-day. DREAM block exists for this time slot but reality diverged. Currently no way to log what actually happened without destroying the plan.
Log what actually happened alongside the plan without overwriting it.
Reality logged in <30s per block vs not captured at all currently.
Creating REALITY block deletes or modifies the DREAM block for that slot.
Friday review. DREAM and REALITY blocks exist for the week. Comparing plan vs actual manually takes 30 min of spreadsheet reconciliation.
See a single alignment number that says whether the week matched the plan.
Score computes in <2s vs 30 min manual comparison of plan-vs-actual.
Score returns 100% when DREAM and REALITY have different archetypes for same slot. Score NaN on partial data.
Does the loop close?
Plan carries forward. Week opens with intention. Evening primes tomorrow.
Friday review complete. Current week scored. Starting next week's plan from zero takes 30 min — the momentum from review dissipates.
Carry this week's template forward into next week's plan in one click.
Next-week planning starts from template in <2 min vs 30 min from scratch.
'Plan next week' creates blank DREAM layer. User starts from zero.
Sunday evening. No structured way to set weekly intention, strategic bets, and archetype schedule together. Planning is fragmented across notes and calendar.
Set intention, 3 strategic bets, and archetype schedule in one pass.
Week planned in <10 min with template carry-forward vs 30 min from scratch.
Only time blocks created — no intention, no bets. Calendar without strategy.
Evening before bed. No mechanism to prime tomorrow's cognitive mode. The gap between evening intention and morning context is 8 hours of sleep.
Set tomorrow's archetype and prime sentence so the Morning Agent surfaces it first.
Prime saved in <30s. Morning Agent surfaces it as first context.
Prime saved but Morning Agent never reads it. Evening ritual disconnected from morning.
Does the agent participate?
CLI reads today, scores the week, runs the mirror.
Agent needs today's plan and current reality. Opening a browser and navigating the calendar UI is not an agent-compatible interface.
Read today's DREAM and REALITY blocks with gap indicators from the terminal.
Agent context loaded in <3s vs manual lookup across multiple files.
CLI returns empty output when blocks exist. CLI throws on missing agent profile.
Agent needs the weekly alignment score. Navigating to the review screen is not an agent-compatible path. Score must match the web exactly.
Compute the same alignment score via CLI that the web review shows.
Score computed in <1s via CLI vs navigating to review screen.
CLI score differs from web score for same data. Different formula or data source.
Friday. DREAM and REALITY blocks exist but only time overlap is measured. Right hours in the wrong cognitive mode looks identical to a perfect week.
Compute archetype alignment (match/shift/miss per day) alongside time overlap.
Two scores in <2s. Pattern detection surfaces structural drift vs one-off misses.
Only time overlap computed. Archetype quality ignored — right hours, wrong mode.
Can a second customer use this?
Onboarding, org isolation, data portability. The loop proves it's not a one-user instrument.
Solar365 user signs in to dreamineering.com. URLs have no org context. Every page returns Dreamineering's data or errors — the app assumes one org.
All app routes scoped to the authenticated user's org so multiple customers share the same deployment.
Solar365 user at /calendar/week sees only Solar365 time blocks. Dreamineering user sees only Dreamineering blocks. Zero cross-contamination. URL pattern carries org context (session or path).
Solar365 user sees Dreamineering's calendar. Org picker exists but /calendar/week ignores the selection. Server actions return unscoped data.
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.
Who this is for
The Misaligned Builder — solo operators who plan ambitious weeks then can't name what shipped. "Busy" replaces "productive." The gap is universal but nobody measures it.
The hidden fear: "Another productivity tool I'll use for a week then abandon." The unlock: the instrument infers reality from timestamps — no logging required. If you stop returning, the kill signal fires.
Questions
Does each story prove value in a way that compounds trust — or just in a way that ships code?
- Which story has the weakest outcome — and what would make it harder to fake?
- If Sunday planning stops at week 3, which stories were assumptions?
- S9-S11 are new (weekly cadence). Do they validate customer value or just system behavior?
- S12 (second customer) is the only L-sized story. What breaks first at org boundary?