Copy the published post text
Field Notes
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
thread-field-notes-W37-Sat
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 | Field note: marketing asks where a lead came from and everyone shrugs. The old chaos was facebook, FB, and Facebook-Ad, all different, all unmatchable. The fix is boring: build one sheet that spits out tagged links, and ban hand-typed UTMs. Boring wins here. (AI-assisted) |
| Field note. Marketing: where did this lead come from? Everyone: shrug. The old chaos: facebook, FB, Facebook-Ad. All different. All unmatchable. The fix: Build one sheet that spits out tagged links Ban hand-typed UTMs Boring, yes. It also works. #marketingops #utm #attribution #buildinpublic #datahygiene | |
| Field note from the trenches. Marketing asks where a lead came from, and everyone shrugs. The reason is usually the same: facebook, FB, and Facebook-Ad all logged as different sources, none of them matchable. The fix is boring, and that is the point. Build one sheet that spits out tagged links in a single fixed format, and ban hand-typed UTMs entirely. No more guessing in the source field. Attribution does not fail because the tools are weak. It fails because three people tagged the same channel three different ways. Standardize the input and the report fixes itself. | |
| X | Field note: marketing asks where a lead came from and everyone shrugs. The chaos: facebook, FB, Facebook-Ad, all unmatchable. Fix: one sheet that spits out tagged links, and ban hand-typed UTMs. Boring works. |
| Field note. Marketing asks where a lead came from, and everyone shrugs. The old chaos: facebook, FB, and Facebook-Ad, all different, all unmatchable. The fix is boring on purpose. Build one sheet that spits out tagged links in a single format, and ban hand-typed UTMs. Attribution does not fail because the tools are weak. It fails because people tag the same channel three ways. Standardize the input. | |
| Threads | Field note: marketing asks where a lead came from and everyone shrugs. The old chaos: facebook, FB, Facebook-Ad, all different, all unmatchable. Fix: build one sheet that spits out tagged links, and ban hand-typed UTMs. Boring, yes. It also works. |
| Field note on marketing attribution: leads go untracked because the same channel gets tagged as facebook, FB, and Facebook-Ad, all unmatchable. The fix is to build one sheet that generates tagged links in a single fixed format and to ban hand-typed UTMs. Standardize the input and your source reports fix themselves. UTM hygiene tips for marketers. | |
| Bluesky | Field note: marketing asks where a lead came from and everyone shrugs. Chaos: facebook, FB, Facebook-Ad, all unmatchable. Fix: one sheet that spits out tagged links, ban hand-typed UTMs. |
| Youtube | Title: Field Notes: Why Nobody Knows Where Your Leads Come From Marketing asks where a lead came from, and everyone shrugs. The reason is usually that facebook, FB, and Facebook-Ad all got logged as different, unmatchable sources. The fix is boring, and that is the point: build one sheet that spits out tagged links in a single fixed format, and ban hand-typed UTMs. Attribution does not fail because the tools are weak. It fails because people tag the same channel three ways. The Big T-M, temerarii.xyz. |
Composition layer × scene 5 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 | hook | 0–5.0s | kinetic-build | icon·liquid-chrome | ♪ node_lock | Field note. Marketing asks where a lead came from and everyone shrugs. on-screen: Where did this lead come from? |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · mark · kinetic-build · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape tetraground redtreatment liquid-chromemotion kinetic-buildpower laser-lockinstrument laser-trace→Where did this lead come from? | |||||||
| 2 |  matches intent NumberedList template | teach | 5.0–11.0s | kinetic-build | icon·white-knockout | ♪ node_lock | Old chaos: facebook, FB, Facebook-Ad, all different, all unmatchable. on-screen: Tag every link, same way |
expected on screen: red ground · a NumberedList panel over a dimmed Signal Field · Nexus leads · node-graph · kinetic-build · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape tetraground redtreatment white-knockoutmotion kinetic-buildpower morphinstrument morph+laser→Tag every link, same waycurate items, nodes | |||||||
| 3 |  matches intent CodeWindow template | diff | 11.0–16.7s | crossfade-8f | icon·liquid-chrome | ♪ node_lock | Build one sheet that spits out tagged links and ban hand-typed UTMs. Boring, yes. on-screen: Make a UTM sheet |
expected on screen: red ground · a CodeWindow panel over a dimmed Signal Field · Nexus leads · code · crossfade-8f · icon·liquid-chrome logo · caption bottom-left spec (the prompt): comp_id CodeWindowvisual codeshape tetraground redtreatment liquid-chromemotion crossfade-8fpower morphinstrument morph→Make a UTM sheetcurate codeLines, windowTitle | |||||||
| 4 |  first render · fix pending CheatSheet templatedead_airgeneric_scene | proof | 16.7–21.7s | receipts-count | icon·white-knockout | ♪ node_lock | Field Notes |
expected on screen: red ground · a CheatSheet panel over a dimmed Signal Field · Nexus leads · receipts · receipts-count · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id CheatSheetvisual receiptsshape tetraground redtreatment white-knockoutmotion receipts-countpower receiptsinstrument spotlight→Field Notescurate points, statsLabels, uses | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 21.7–26.7s | coalescence | icon·white-knockout | ♪ bed_out | Field Notes |
expected on screen: red ground · tetra hero in the shared Signal Field · Nexus leads · coalescence · coalescence · icon·white-knockout logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape tetraground redtreatment white-knockoutmotion coalescencepower coalescenceinstrument coalescence→Field Notes | |||||||