Remarkable asset idea — c021
Campaign: meta
Execution task: prepare-remarkable-asset-idea
Prospect / signal ID: c021
Segment name: X — AI sludge personal brand as company red flag
Date: 2026-07-21
Task id: t_5c9b0bef
Status: idea package (not ship-authorized; not outreach-authorized; not send-authorized)
Contact? remains research-only. Warm path remains unknown - human to validate.
Stage after this package: scored_permission_fit (SVM + permission ladder scored; fit clear)
Source type: AI rediscovery public-signal post (research-only) — not a named buyer list.
Signal ground (from discovery)
| Field | Value |
|---|---|
| Source | X discourse (@Rayen_Dhifi and related) on AI sludge personal brands |
| Channel / connector | x / hermes_x_search |
| Evidence URL | https://x.com/Rayen_Dhifi/status/2047617643813704140 |
| Public language (excerpt) | Low-effort AI personal-brand posts framed as a red flag for the company behind the founder; personal brand treated as core distribution while sludge damages trust |
| Signal strength | med-high |
| Fit score (1–5) | 5 |
| Status sensitivity | high (founder name-as-channel; company reputation rides the feed) |
| Mapping status | research-only discourse language; not CRM; not outreach-ready |
Not demoted: This is a high-fit public-signal row for founders/expert-creators whose name is the channel and whose company or offer is judged by that feed — not landscape-only competitor map (those carry skip_asset_prep / language_only). Card instructions authorize asset prep for c021. “Research-only” means Contact? and warm path stay unknown until the human maps real people — not “skip the contribution object.”
Hard rule: Do not invent person names or X handles as contacts. Do not reply, quote-tweet pitch, follow, or DM anyone from the evidence URL. Do not re-hero Interrogation vs Invitation Still, Dual Key, Silence Credit, Zero-Person Trophy, c005 sludge detector, c015 badge, c017 sameness, c018 positioning, or c019 Voice Is the Product as this package’s public face (L-003 / L-007). Pair language only.
SVM score (final-launch-packet)
| Criterion | Score / note |
|---|---|
| Own-name expert-creator fit | Strong — founders and consultants whose personal brand is core distribution match name-as-channel SVM |
| Craft / reputation priority (not GRQ) | Strong — sludge on the founder feed is framed as trust damage to the company behind the name, not a growth-hack volume problem |
| Distrust of autopilot / AI under byline | Exact match — low-effort AI personal-brand posts as a red flag for who stands behind the founder |
| Need for prep that still ships under human voice | Strong — contribution is a five-post feed audit (prepared vs sludge) so they catch red-flag posts before they train the market |
| Warm-path / permission readiness | Unknown — public thought-leader post, not a named warm contact; human maps any real founders they already know |
| Overall fit | 5 / clear scored_permission_fit |
Hard exclusions respected: no GRQ primary targeting; no cold list from X; no invented relationships; Contact? stays research-only; agents never post/DM/comment/follow/reply on X; no outcome numbers invented from the post; thought-leader ≠ buyer filter stays on.
Qualification-policy note: ops/qualification-policy.yaml may still hold template SVM from another campaign. Scoring for this package uses final-launch-packet.md SVM only.
Permission ladder fit (packet written path)
| Rung | How this asset earns it (when live work is later allowed) |
|---|---|
| Attention (stranger value) | Remarkable Founder Feed Audit card — contribution first: audit five live posts as prepared vs sludge / company red flag; no capture form |
| Public sample | Aligns with Warmer Path “prepared · you still send” language; does not replace human posts of current content-ready winners |
| Hand-raise | Only if human later invites one named next item after value — never forced by this file |
| Requested notes | Notes only after they ask |
| One-piece review | Audit teaches keep / change / skip / send when a founder post would read as sludge under the company name |
| Paid | Only after useful review; no price in this package |
| Peer share | Ask-first only after lived value; share sample + “It prepares the work; I still send under my name.” |
Live outreach / collection / DMs / comments / follows / X replies: still blocked unless human expands scope. Evidence URL: never agent-comment, quote-tweet pitch, DM, or follow.
Asset name
Founder Feed Audit (Five Posts · Prepared vs Sludge · Company Red Flag)
One-line promise: A one-page peer card that audits five recent founder-feed posts as prepared under your name vs AI sludge — because low-effort personal-brand cadence is now read as a red flag for the company behind the founder.
Godin job: Earn attention with a contribution, not a pitch. Remarkable because it treats the founder feed as company due diligence surface — not abstract cadence smell tests alone, not spoken-voice custody, not badge theater, not sameness volume.
Discovery seed (preserved): “Peer gift: Founder feed audit (5 posts: prepared vs sludge)” — refined here into a full object that pairs company-behind-name language with other private assets without re-heroing retired public faces or c005 / c015 / c017 / c018 / c019 as this package’s public face.
Differentiation from prior packages:
- c002–c004 / c006 — community do-not-ship, creator surface, byline contrast, taste.
- c005 — LLM cadence smell tests (rhythm under name; abstract detector).
- c007 — personal trust / warm-path inventory.
- c014 — named friend Ho Tai restart boost (pending-human).
- c015 — authenticity / human-created badge.
- c017 — sea of sameness / voice vs volume.
- c018 — positioning before prompts.
- c019 — spoken / brand-voice delivery custody (TTS vs human narration).
- c021 — founder feed as company red-flag surface: five-post prepared-vs-sludge audit worksheet for name-as-channel founders — external judgment of the company rides the feed, not just internal cadence taste.
Align with current public work — deliberate pair, not a second cow
| Surface | Role |
|---|---|
| Public heroes (human-posted) | Finished chapters include Dual Key, Silence Credit, Zero-Person Trophy / Bind Wall, Interrogation vs Invitation Still (Meet ≠ Record, posted on X per gate #37). Do not re-hero those objects as this segment’s public face or as a later cycle primary. Agents never post. |
| Related private assets | c005 = abstract cadence sludge detector; c015 = badge; c017 = sameness; c018 = positioning; c019 = voice-as-product. This card = five-post founder feed audit / company red flag. Shared chrome OK; do not ship them as competing public cows. |
| This signal asset | Private / warm-path / peer contribution or internal language bank — feed audit card for founders under own name. Not a public Purple Cow this cycle. Not a signup form. Not an X reply template. Not a re-hero of retired public faces. |
How they work together
- Public feed stays the human’s content lane with new singular objects when the cycle runs again.
- Warm path (only after human names a real person they know): optional 1:1 gift of this card — contribution, not a pitch.
- Research-only use now: phrase bank and object brief for internal drafts; never cold outreach from the X URL.
- “Prepared under my name · sludge is a company red flag” language may echo without reprinting trophy, Meet≠Record stills, badges, cadence detectors, or voice cards as the hero.
Human-post / human-send constraint (must stay visible):
Agents must never post, schedule, comment, DM, email, follow, or claim that any pack or gift was published or sent by the machine. Human posts and sends under their own name only.
What the contribution is (object + words)
One-page Founder Feed Audit card (print/PDF twin; peer gift or internal language)
- Title:
Founder feed audit
Sub-line:Five posts · Prepared vs sludge · Company red flag · I still send - Opening strip (peer gift, not product):
- Your personal brand is core distribution.
- Low-effort AI posts under your name are now read as a red flag for the company behind you.
- This card audits five real posts before the next one ships as you. - Five-post audit grid (the core object):
For each of posts 1–5 (paste link or one-line topic):
- Post:
- Verdict: PREPARED under my name · SLUDGE (company red flag) · HOLD / silence
- Why (one line):
- Next: keep · change · skip · send - Five company-red-flag checks (paired with the grid):
- Would a careful buyer judge my company from this post alone? (if yes and it smells AI-average → red flag)
- Does this post exist because I had something to say, or because the calendar demanded a drop?
- Would I defend this post in a diligence call about the business behind my name?
- Is the cadence interchangeable with a dozen other founder feeds this week?
- Is deliberate silence better than another sludge post that taxes trust in the company? (if yes → completed professional work, not failure)
- Two columns (the core object):
- SLUDGE (company red flag) — low-effort AI personal-brand drops, calendar filler, interchangeable founder insight, trust damage rides to the company
- PREPARED (name-as-channel) — tools may draft; human keep · change · skip · send; you still send; incomplete until you decide; silence allowed when average would ship - Feed freeze block (the remarkable object):
- Posts I will not ship this cycle (sludge / red flag):
- Posts that stay PREPARED until I choose send:
- One line the company must not be judged by: ___
- Reason I would hold a founder-feed drop: ___ - Operating strip (shared chrome with packet language):
- Prepared work stays incomplete until I choose: keep · change · skip · send.
- Do not publish or contact under my name this cycle unless I choose send.
- Reason I held publish: ___ (process language only — e.g. “founder feed would read as company red flag”)
- Preparer: ___ · Date: ___
- Completed prep · counts toward draft floor (not FAIL) - Audience filter callout (explicit):
- In: founders, consultants, expert-creators under own name where personal brand is core distribution; craft and reputation; company or offer judged through the founder feed
- Out: get-rich-quick / pure volume personal-brand farms; “AI fill my founder calendar forever” primary buyers; scraping X posters as a cold list; thought-leaders who only comment on sludge discourse and are not in-market for prep help - Banned as hero: growth guarantees · engagement stats from the post · capture QR · X reply/quote/DM/follow scripts · Interrogation vs Invitation Still / Zero-Person Trophy / Dual Key / Silence Credit / c005 / c015 / c017 / c018 / c019 re-hero · product carousel · inventing intros to people named only in the evidence thread
Permission-safe one-pager outline (draft shape only — human rewrites before any external use)
Founder feed audit
Five posts.
Prepared vs sludge.
Company red flag.
You still send.
Audit five recent founder-feed posts:
Post 1: _______________ Verdict: PREPARED / SLUDGE / HOLD Next: keep·change·skip·send
Post 2: _______________ Verdict: PREPARED / SLUDGE / HOLD Next: keep·change·skip·send
Post 3: _______________ Verdict: PREPARED / SLUDGE / HOLD Next: keep·change·skip·send
Post 4: _______________ Verdict: PREPARED / SLUDGE / HOLD Next: keep·change·skip·send
Post 5: _______________ Verdict: PREPARED / SLUDGE / HOLD Next: keep·change·skip·send
Five checks before the next drop ships as you:
1. Would a careful buyer judge my company from this post alone?
2. Did I post because I had something to say — or because the calendar demanded it?
3. Would I defend this post in a diligence call about the business behind my name?
4. Is this cadence interchangeable with a dozen other founder feeds this week?
5. Is deliberate silence better than another sludge post?
LEFT — SLUDGE (company red flag)
(low-effort AI brand drops · calendar filler · trust taxes the company)
RIGHT — PREPARED (name-as-channel)
(tools may draft · keep · change · skip · send
you still send · incomplete until you decide · silence allowed)
Freeze the feed:
Will not ship this cycle: _______________
Stays PREPARED until send: _______________
Line the company must not be judged by: _______________
Do not publish under my name this cycle unless I choose send.
Reason: _______________
Preparer: _______________ Date: _______________
Completed prep · counts toward the draft floor.
Who this is for: founders whose name is the channel.
Who this is not for: GRQ volume personal-brand farms.
No signup. No product tour. No X reply script.
It prepares the work; I still send under my name.
Do not add: invented opt-in counts, “AI write my founder calendar” tour, guaranteed pipeline, claims that AI posted any content-ready pack, or any instruction to cold-message @Rayen_Dhifi or related X accounts.
Permission-safe next steps (machine vs human)
| Actor | Allowed | Forbidden |
|---|---|---|
| Agent | Keep this file; score stage; reference in later handoffs; standing funnel / daily ops when bridge routes | Send, post, DM, X reply/quote/follow, invent warm paths, mark Contact?=approved, re-hero retired public objects or c005/c015/c017/c018/c019 as this cycle’s face |
| Human (content) | Post new singular objects from content-ready packs when cycle runs | Letting agents post; re-heroing Interrogation vs Invitation Still / Zero-Person Trophy / related private cards as primary face |
| Human (prospects) | Skim language; map only real founders you know; optional future 1:1 gift of this card | Invent intros; treat X posters as a list; outreach without approved contacts + scope |
| After real warm paths + scope expansion | Contact review / handoff may use this audit card as 1:1 contribution | Outreach batch without approved contacts |
Risks and ethics
- X post ≠ buyer list — c021 is discourse language, not a CRM person with a warm path.
- Thought-leader ≠ buyer — many voices name the red flag without wanting prep help; map people, not the whole discourse.
- Anonymous scrape risk — do not invent relationships to posters or treat handles as contacts.
- Overlap with c005 — intentional family (abstract cadence detector vs five-post feed audit / company red flag); do not ship as competing public cows; object job here is external company judgment of the founder feed, not smell tests alone.
- Status sensitivity high — founder identity and company reputation; never shame people who used AI drafts while learning.
- Modest claims only — process language; no outcome proof until live evidence exists.
- Live scope blocked — warm paths and final scope still gate collection, invites, contacts, and sends.
- Qualification policy template may still carry another campaign’s SVM — retune before live scoring; this package uses
final-launch-packet.md.
Score decision (advance)
| Field | Value |
|---|---|
| Advance stage? | Yes → scored_permission_fit |
| Reason | Fit clear (5/5) to own-name / name-as-channel / anti-sludge SVM with company red-flag angle; permission ladder maps to stranger value first via contribution; not demoted language-only landscape; card authorized asset prep for c021 |
| Warm path | unchanged: unknown - human to validate |
| Contact? | unchanged: research-only |
| Asset path | ops/asset-ideas/c021.md |
| Related public packs | retired faces only for non-reuse: Zero-Person Trophy, Interrogation vs Invitation Still, Dual Key, Silence Credit; related private peers: c005 / c015 / c017 / c018 / c019 (do not re-hero as public face) |
Assumptions
- Public language summarized from
ops/prospect-research-20260721.mdrediscovery row for c021; human should verify the X URL if quoting externally. - No named warm path exists for this post; Contact? stays research-only.
- Differentiated from c005 by five-post founder feed audit / company-behind-name red flag vs abstract LLM cadence smell tests; from c019 by written founder-feed surface vs spoken voice custody.
- Asset is prepared-only peer/language contribution; not send-authorized.
- Acting on learnings L-001, L-002, L-003, L-006, L-007 (agents never post; warm paths only; do not re-hero retired objects including Interrogation vs Invitation Still).