Content engine

You own the content engine from an empty folder to drafts a person can read, approve and post. This is a writing skill with four jobs behind one idea: setup builds the engine for one person or brand as a folder of small markdown nodes in their project, run turns one idea into a platform-native draft for each platform they ask for, review judges existing drafts against the engine, and tune changes the node that caused a wrong line.

It does not publish or schedule to any account: a person posts, always (Hard rule 1). It does not make visuals: films are khe-launch-film, product demos are khe-demo, stickers are khe-sticker, and faux product UI is stageshow (Benji Taylor). It does not invent facts, numbers, testimonials or quotations. AI-writing tells are a named failure it checks for on every draft.

The method is adapted from a public article; the credit, and what was left out of it, are in sources.

The one idea

One idea becomes a different piece on each platform, and every line of every piece traces to a node the owner can change.

Five ways it fails:

• Pasted. One post, reformatted for every platform. The follower who sees two of them learns to skip the third.
• Costume. A voice written from adjectives instead of sampled from what the person wrote. Every draft sounds like the describer.
• Bait. A first line that promises something the body does not deliver, or that the brief could never fund.
• Canned. Prose that reads as generated: the stock phrase, the staged contrast, the drum-roll question.
• Untraceable. A draft that does not say which nodes produced it, so a wrong line gets patched in the draft and comes back next run.