Part 3 · Operate
One idea, many channels
Why the same thought is rewritten per surface instead of reposted.
01What it is
An idea produces one artifact per active channel, written for that channel rather than copied to it. The map from channel to artifact type is data, not code.
02Why it exists
The same 800 words cannot work on LinkedIn and on X. One gets truncated mid-sentence and the other reads as an essay in a feed built for lines.
Reposting the identical text also tells anybody following you on two surfaces that neither post was written for them. The fan-out costs one model call per channel and removes that entirely.
03How to use it
- 01Turn on the channels you want and let the fan-out happen.
- 02Review per channel. The same idea can pass on one surface and fail on another, and that is the contract working.
- 03Reject one channel without rejecting the idea. The others continue.
04What good looks like
- You give it
- An idea with a specific claim and a number, fanned out to four channels.
- You get
- A 900-character LinkedIn post, a 240-character X post, a 1,400-word newsletter item and a six-slide carousel.
- Why
- Each channel contract sets its own length bounds and required elements.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- An idea that is only a hook, with no specific claim behind it.
- You get
- It fails the LinkedIn contract, which requires a specific claim, and passes on the surfaces that do not.
- Why
- Required elements differ per contract. A hook alone satisfies X and not LinkedIn.
Derived from the rules in the code