How one customized gift became the blueprint for an MVP harness that can
spin up many personalized sites and apps like this — with interactive
sequence diagrams you can play, scrub, and step through.
Lucy TV started as dials on a wooden set. It became a photoreal Christmas
living room you can walk up to — and is now treated as a
greeting-card product prototype: a personalized link,
a branded scene, a private message, optional media.
PrototypeOne hand-built giftAgents + tools craft a single site for Mom.
PlaybookCapture what repeatedSlots, pipelines, and “never do this again” rules.
Harness MVPConfig → siteA customer fills slots; the system generates, verifies, deploys a clean domain.
Play or scrub this sequence — this is the manual loop the harness must automate.
We are between Playbook and Harness MVP. Lucy TV is the reference build.
Prototype → MVP harness
An MVP is not “more Lucy TV features.” It is a system that can
create customized sites/apps like Lucy TV from a brief,
without re-deriving the architecture each time.
Harness inputs (customer brief)
Recipient, message, era/season template, street cast mood, media source or empty library, preferred clean domain name, share style (link / QR / USB).
Harness outputs
Generated plate + registered layers, walker/car packs, console skin, library.json, Pages project with a human domain, journey/readme stub, verify report.
Stages the MVP must own
Automate the middle; keep humans on taste, rights, and naming.
Interactive · Customer order → live card
The happy path for the MVP product. Use Play, scrub, or click any arrow.
Interactive · Harness build for one card
Inside the factory: what the system does for a single customized site.
Rough share of craft effort on Lucy TV — not a timesheet, a priority chart.
Outer ring = automate. Center = always ask a human.
Interactive · Recipient opens the card
What Mom (or any recipient) experiences — the product promise.
Customization slots
These are the levers a harness exposes. Lucy TV filled every slot once, by hand.
Green “Domain” is a hard product rule: ask before any random subdomain.
Depth stack
The scene architecture every template must preserve: one plate, registered layers.
Fable board · Depth as stacked planes
Hard lessons → harness rules
Fable board · Rejected left · Accepted right
Do not encode in the harness
Pose morphs between generated stills; daylight patched to night; CSS objects next to photoreal plates; random Pages hostnames; “it’s live” without fetching production files.
Bake into the harness
One-photo motion; measured perspective; night plates; verify hooks; human gate on domain + final look; ES5 gift JS for older Safari.