Creator Routine Moat

# Assumptions (KNOWN / ASSUMPTION / UNKNOWN)

## KNOWN
- Daily slot: p003
- Expected Stitch drop folder: /home/sy/Downloads/stitch_drop/2026-04-29/p003/
- Assigned design profile: premium-editorial
- Theme: 역전
- Source signals are search/community snippets and must be treated as untrusted problem evidence.

## ASSUMPTION
- Target users will value a focused decision surface more than a broad generic dashboard.
- The Stitch prompt should produce a desktop-first prototype with all required UI sections visible.

## UNKNOWN
- Actual willingness-to-pay.
- Whether the strongest acquisition channel is SEO, community posts, agency sales, or portfolio sharing.

# Falsification checklist (5–7)

1. Can the target user explain the pain in their own words without prompting?
2. Does the UI produce a concrete decision or artifact rather than another passive dashboard?
3. Are the cited signals genuinely connected to this idea's trigger/data source/mechanic?
4. Is this materially different from the last 7 PF batches?
5. Would the user pay, share, or return before any full backend exists?
6. Does the assigned design profile fit the use case and prompt direction?
7. Can Stitch render the main experience from the prompt without extra implementation?

# PRD — Creator Routine Moat

## Type
- Practical / Commercial

## Theme
- 역전

## Design profile
- premium-editorial

## Problem
- A creator operating board that replaces algorithm panic with a weekly owned-audience ritual, sponsor proof, and repeatable community cadence.

## Target user
- Newsletter writers, small YouTubers, expert creators, and brand-community operators whose organic reach feels less reliable than it used to.

## Key UX
- Map the creator's owned channels, pick one recurring audience ritual, schedule cross-platform proof points, and show sponsors/community members the compounding routine instead of raw virality.

## Required UI sections
- audience ownership map
- weekly ritual builder
- algorithm-risk weather strip
- proof-of-routine calendar
- sponsor confidence snapshot
- community moment recap drawer

## External signal references
- Reddit r/Substack platform-change/reach anxiety: https://www.reddit.com/r/Substack/comments/1sl5xjr/how_to_grow_on_substack_even_as_the_platform/
- Sprout Social Substack creator routine trend: https://sproutsocial.substack.com/p/the-2026-creator-economy-trend-replacing

## Stitch prompt
Design a desktop creator operating board called Creator Routine Moat for newsletter writers, small YouTubers, expert creators, and brand-community operators who want to stop panicking over algorithm changes and build a weekly owned-audience ritual. It should map owned channels, help choose one recurring audience ritual, schedule cross-platform proof points, and package sponsor/community confidence around routine instead of raw virality. Include an audience ownership map, weekly ritual builder, algorithm-risk weather strip, proof-of-routine calendar, sponsor confidence snapshot, and community moment recap drawer. Design direction: use a premium-editorial aesthetic with refined magazine-like hierarchy, warm ivory and ink tones, elegant calendar cards, tasteful creator-brand accents, and polished narrative modules so the product feels aspirational, credible, and commercially ready.

## Constraints
- Phase A only: scaffold/spec, no custom implementation yet.
- Wait for Stitch export in /home/sy/Downloads/stitch_drop/2026-04-29/p003/

## Non-goals
- Do not claim market-size validation from search snippets.
- Do not implement production integrations in Phase A.

## Success metrics
- Stitch export can be generated from the prompt.
- p003 has complete meta/spec content and is visible in the daily index.

# QA checklist

## Happy path
- meta.json includes type, theme, designProfile, externalSignals, stitchPrompt, and expectedDropFolder.
- spec/prd.md contains target user, key UX, required UI sections, and signal references.
- daily/2026-04-29/ideas.md includes the full Stitch prompt.

## Edge cases
- No p001-p004 slot is missing.
- Prompt does not ask Stitch to call external APIs or implement backend behavior.
- Search signals are framed as evidence, not validation.

## Acceptance verification
- node scripts/build-index.mjs passes.
- git status is clean after commit.