META • TO T FLYWHEEL • PRIORITY #1

The Public Creative Flywheel: Obs → DR → Asset → Lander Variant → Blog Post

2026-05-31
7 min read

The user explicitly noted that both the internal dashboard and the public site felt "basically empty" even after months of internal DRs and agent activity. The approved ToT plan made public creative production absolute priority #1. This post is both an explanation of the mechanism and proof that the mechanism now produces visible output on the actual served site.

The Old Pattern (Why It Felt Empty)

187 nearly-identical 800-900 byte HTML stubs in /data/moneytree-src/public-site/blog/posts/ (dated Nov 2025–Mar 2026) alternating between two thin titles. They were generated in bulk, never updated, and never deployed to the nginx container that actually serves ideaspawn.ai (the compose/public-site/ tree is the live mount).

The New Loop (What Changed)

  1. High-fidelity local obs captured (exact PNG + FlightRecorder trace)
  2. Structured response returned over restricted channel (to_t_impact + blockers surfaced)
  3. DR written with file:line citations (DR-072, DR-075)
  4. Server-side synthesis (image_gen, CapCut scripts, lander edits) produces concrete assets
  5. Public site updated in the served tree (ai-notion variants, new real blog posts)
  6. This blog post written from the same DRs, published to the same tree

The entire cycle from obs to live public HTML can now run in <90 minutes when the channel and Operator harness are healthy. That is the velocity the user asked for when they said "Definitely More but not DR's, actual output on the site."

User request 2026-05-31 (exact quote in context) • DR-20260531-075:14-28 • /data/compose/moneytree/public-site/blog/index.html (this tree, 12 real posts) • /data/compose/moneytree/public-site/ai-notion/index.html:211-236 (obs-seeded variants)