Copy the published post text
Our creative stack (the repos + tools we control)
copy ready · render pending
Output-policy spec format · dimensions (asset_specs.output_policy)
formatnative cut · 9:16 · 1:1 · 16:9
dims1080×1920 · 1080×1080 · 1920×1080
cadence5/day floor × 9 channels
Channels 9 destinations
TikTokInstagramLinkedInX/TwitterFacebookThreadsPinterestBlueskyYouTube
This post a distinct social asset — its own angle, storyboard, and cuts
social-W29-Wed-4
5-distinct-social/day · 9:16 master → 1:1 / 16:9 cuts per channel
Channel-cuts this asset → 9 native captions (one master · per-platform aspect+copy)
| Channel | Native caption |
|---|---|
| Tiktok | Most shops hide their method and charge for the mystery (AI-disclosed, and yes we'll tell you that too). We give it away. Why? Writing down exactly how you did a thing exposes the shaky step you were skipping. The mess you can't explain IS the bug. Open beats hidden. #openknowledge #teaching #process |
| Most shops hide the method. We give it away. Teaching forces you to be clear. The step you can't explain is the bug. Clarity is the edge nobody can copy. #openknowledge #teaching #process #buildinpublic #strategy | |
| Why we give the method away. The old rule was: keep your method secret, charge for the mystery. We do the opposite, and it's a competitive advantage. Writing down exactly how you did a thing forces you to find the shaky step you were quietly skipping; if you can't explain a step in plain words, that step is usually the bug in your process. Keep a plain runbook as you work (each step, why it exists, what breaks if skipped) and a new teammate can run the whole thing on day one. Education doesn't give away your edge; clarity is the edge nobody can copy. | |
| X | Most shops hide the method and charge for the mystery. We give it away. Writing down how you did a thing exposes the shaky step you were skipping. The mess you can't explain IS the bug. Open beats hidden. |
| For years the rule was: keep your method secret, charge for the mystery. We do the opposite and hand you the whole thing, free. Why? Writing down exactly how you did a thing forces you to find the shaky step you were quietly skipping. If you can't explain a step in plain words, that step is the bug. Education doesn't give away your edge; it sharpens it. More in the video. | |
| Threads | Most shops hide the method and charge for the mystery. We give it away. Writing down how you did a thing exposes the shaky step you were skipping. The mess you can't explain IS the bug. Open beats hidden. |
| Open knowledge as strategy: give the method away, write a runbook, document your process, teaching sharpens clarity, build in public, knowledge sharing, competitive edge through transparency. Why education doesn't give away your edge, it sharpens it. | |
| Bluesky | Most shops hide the method and charge for the mystery. We give it away. Writing down how you did a thing exposes the shaky step you were skipping. The mess you can't explain IS the bug. |
| Youtube | Open by Design: Give the Method Away (Education Levels People Up) For years the rule was: keep your method secret, charge for the mystery. We do the opposite and hand you the whole thing, free. Writing down exactly how you did a thing forces you to find the shaky step you were quietly skipping; if you can't explain a step in plain words, that step is usually the bug in your process. Keep a plain runbook as you work and a new teammate can run it on day one. Education doesn't give away your edge; clarity is the edge nobody can copy. AI-assisted, human-judged. |
Composition layer × scene 9 scenes · this post's OWN storyboard (distinct per asset)
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 | matches intent shared field signature-3d | open | 0–7.3s | spatial-parallax | icon·color | ♪ bed_in | For years the rule was simple: keep your method secret, charge for the mystery, and hope nobody asks how. on-screen: Most shops hide the method |
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · node-graph · spatial-parallax · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual node-graphshape boxground whitetreatment colormotion spatial-parallaxpower summoninstrument summon→Most shops hide the method | |||||||
| 2 |  matches intent shared field signature-3d | hook | 7.3–14.3s | kinetic-build | icon·color | ♪ node_lock | We do the opposite. We hand you the whole method, free, even the parts a competitor could copy. on-screen: We give the method away |
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape boxground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→We give the method away | |||||||
| 3 |  matches intent NumberedList template | teach | 14.3–21.6s | kinetic-build | icon·color | ♪ node_lock | Writing down exactly how you did a thing forces you to find the shaky step you were quietly skipping. on-screen: Teaching forces you to be clear |
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape boxground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Teaching forces you to be clearcurate items, nodes | |||||||
| 4 |  matches intent RankList template | proof | 21.6–29.3s | receipts-count | icon·color | ♪ node_lock | If you cannot explain a step in plain words, that step is usually the bug hiding in your own process. on-screen: The mess you can't explain is the |
expected on screen: white ground · a RankList panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id RankListvisual receiptsshape boxground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→The mess you can't explain is the bugcurate rows, statsLabels | |||||||
| 5 |  matches intent StackTrace template | diff | 29.3–37.4s | crossfade-8f | icon·color | ♪ node_lock | The Big T-M does not compete by hoarding. We compete by doing the work better than the people we just taught. on-screen: We compete on doing, not hiding |
expected on screen: white ground · a StackTrace panel over a dimmed Signal Field · Faber leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id StackTracevisual codeshape boxground whitetreatment colormotion crossfade-8fpower morphinstrument morph→We compete on doing, not hidingcurate codeLines, errMsg, errType, fix, frames | |||||||
| 6 |  matches intent ChecklistCard template | teach | 37.4–44.699999999999996s | kinetic-build | icon·color | ♪ node_lock | Keep a plain runbook as you go: each step, why it exists, and what breaks if you skip it. on-screen: Write the runbook as you work |
expected on screen: white ground · a ChecklistCard panel over a dimmed Signal Field · Faber leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id ChecklistCardvisual node-graphshape boxground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Write the runbook as you workcurate items, nodes | |||||||
| 7 |  matches intent StatScoreboard template | proof | 44.7–53.800000000000004s | receipts-count | icon·color | ♪ node_lock | Once it is written, a new teammate can run the whole thing on day one, and you stop being the only one who knows. on-screen: Your team levels up when it's written |
expected on screen: white ground · a StatScoreboard panel over a dimmed Signal Field · Faber leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id StatScoreboardvisual receiptsshape boxground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Your team levels up when it's writtencurate pillar, stats, statsLabels | |||||||
| 8 |  matches intent StepFlow template | step | 53.8–61.5s | kinetic-build | icon·color | ♪ node_lock | Try it: write down the one step you would never want shared, and watch it become your clearest, strongest step. on-screen: Do this |
expected on screen: white ground · a StepFlow panel over a dimmed Signal Field · Faber leads · pipeline · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id StepFlowvisual pipelineshape boxground whitetreatment colormotion kinetic-buildpower throwinstrument laser-trace→Do this: write the step you fear sharingcurate stages, steps | |||||||
| 9 |  matches intent shared field signature-3d | resolve | 61.5–68.5s | coalescence | icon·color | ♪ bed_out | Education does not give away your edge. It sharpens it, because clarity is the edge nobody can copy. on-screen: Open beats hidden, every time |
expected on screen: white ground · box hero in the shared Signal Field · Faber leads · coalescence · coalescence · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape boxground whitetreatment colormotion coalescencepower coalescenceinstrument coalescence→Open beats hidden, every time | |||||||