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."

Action — Human-initiatedCron — ScheduledHook — Event-triggered

Does the plan hold?

Template imports, layer separation, empty states that guide.

S1Action

When

I need to

So I get

Not

Blank 7-column grid with no guidance. User stares at empty cells.

S2Action

When

I need to

So I get

Not

Import returns 200 with empty array. Silently succeeds but creates zero blocks.

S3Action

When

I need to

So I get

Not

Toggling layers merges or overwrites blocks from the other layer.

Does reality get captured?

Logging without friction. Scoring without self-report.

S4Action

When

I need to

So I get

Not

Creating REALITY block deletes or modifies the DREAM block for that slot.

S5Action

When

I need to

So I get

Not

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.

S6Action

When

I need to

So I get

Not

'Plan next week' creates blank DREAM layer. User starts from zero.

S9Action

When

I need to

So I get

Not

Only time blocks created — no intention, no bets. Calendar without strategy.

S10Action

When

I need to

So I get

Not

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.

S7Cron

When

I need to

So I get

Not

CLI returns empty output when blocks exist. CLI throws on missing agent profile.

S8Cron

When

I need to

So I get

Not

CLI score differs from web score for same data. Different formula or data source.

S11Cron

When

I need to

So I get

Not

Only time overlap computed. Archetype quality ignored — right hours, wrong mode.

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.

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.

Overview Flow Diagrams

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?