JS.

You're in · save this page

The Clone System.

One recording became a machine that writes, films, edits and posts every day. Five stages, each one boring on its own, brutal in combination. Here is exactly how it runs.

01The recording

Film yourself once. Twenty minutes of talking to camera in good light with clean audio. That footage trains a HeyGen clone of your face and a clone of your voice.

That was the last day I was required on camera. Everything you have seen since is the clone reading scripts it was handed that morning.

02The brain

Every morning the system scans Hacker News, TechCrunch, The Verge and GitHub and pulls what actually moved in AI overnight. Every two hours it runs a breakout check, so a story that explodes at 2pm does not wait until tomorrow.

It keeps a ledger of every topic already covered. Before anything gets written, the candidate is checked against the ledger. The machine never repeats itself, which is more than most humans posting daily can say.

03The writer

The scripts follow a craft playbook, not vibes. Every hook must be a hard fact plus one bold claim. Every beat of the script needs one line worth screenshotting, or the beat gets cut.

Then a second AI reads the first draft like a ruthless editor: it attacks the weak lines, kills the filler and sends it back. The script that survives both passes is the one that gets filmed.

04The studio and the cop

The studio renders the video: word level captions, the text hook on frame one, and real screenshots of the actual story with motion on them instead of stock footage.

Then the cop runs automated QA on every render: loudness levels, a scan for frozen frames, and face detection that self corrects the crop when the clone drifts out of frame. Anything that fails gets rebuilt before a human ever sees it.

05The kill switch

Nothing posts without human approval. Every video waits in a queue until I say yes, and scheduling has a one hour minimum so nothing can sneak out behind me.

My entire job in this system is ten minutes of judgment a day. The machine does the labor. I keep the taste and the veto.

Build your own

This page is the map. The community has the machine.

Inside AI Operators I walk through the actual build: the code, the prompts, the QA thresholds, and weekly calls where we debug what you are making.

Want a clone plus content machine built for your business? cyndra.ai