95 OPS
Campaign ledger

Remarkable asset idea — c015

Campaign: meta
Execution task: prepare-remarkable-asset-idea
Prospect / signal ID: c015
Segment name: Forbes authenticity / AI pushback (segment)
Date: 2026-07-21
Task id: t_1b7894dc
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 segment (research-only) — not a named buyer list.


Signal ground (from discovery)

Field Value
Source Forbes — William Arruda: the pushback against AI and personal brand
Channel / connector web / hermes_web_search
Evidence URL https://www.forbes.com/sites/williamarruda/2026/05/31/the-pushback-against-ai-is-real-what-it-means-for-your-personal-brand/
Public language (excerpt) AI slop entered mainstream conversation for low-quality repetitive AI content flooding feeds; creators, writers, artists, and consultants increasingly highlight that their work is human-created; people pay more for access to humans than information alone; LinkedIn engagement shifting under AI flood
Signal strength high
Fit score (1–5) 5
Status sensitivity med-high (personal brand authenticity claims under real names)
Mapping status research-only segment language; not CRM; not outreach-ready

Not demoted: This is a high-fit segment language row for own-name experts under authenticity / AI-slop trust pressure — not landscape-only competitor map (those carry skip_asset_prep / language_only). Card instructions authorize asset prep for c015. “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 from the Forbes article. Do not treat Arruda’s audience or LinkedIn “everyone” as a cold list. Do not re-hero Interrogation vs Invitation Still, Zero-Person Trophy, Dual Key, or Silence Credit as this package’s public face (L-003 / L-007).


SVM score (final-launch-packet)

Criterion Score / note
Own-name expert-creator fit Excellent — mainstream personal-brand discourse about human-created work under reputation; consultants and creators under own name are core SVM
Craft / reputation priority (not GRQ) Strong — authenticity / trust edge, not growth-hack volume or “AI that posts for me”
Distrust of autopilot / AI under byline Exact match — AI slop trust risk + pushback language pairs packet “you still send under your name”
Need for prep that still ships under human voice Strong — contribution teaches what stays human-signed vs what tools may mark PREPARED; custody without surrendering judgment
Warm-path / permission readiness Unknown — media segment, not a named warm contact; human maps any known personal-brand coaches / experts they already know
Overall fit 5 / clear scored_permission_fit

Hard exclusions respected: no GRQ primary targeting; no cold list from article readers; no invented relationships; Contact? stays research-only; agents never post/DM/comment/follow; no outcome or engagement numbers invented from Forbes.

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 Human-created badge card — contribution first: what stays human-signed vs what tools may prepare; 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 Badge teaches which line items stay under human signature before any one-piece review
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: still blocked unless human expands scope. Media articles: never agent-comment, DM, or pitch from the evidence URL.


Asset name

Human-Created Badge Card (Signed vs Prepared)

One-line promise: A one-page peer badge card for independent experts under authenticity pressure: what must stay human-signed on the public face vs what tools may mark PREPARED — so trust survives the AI-slop flood without a growth calendar.

Godin job: Earn attention with a contribution, not a pitch. Remarkable because it treats human-created as a custody boundary the expert can defend — the opposite of “add a generic ‘human-made’ sticker and post more.”

Discovery seed (preserved): “Human-created badge card (one page): what stays human-signed vs what tools may prepare — pairs Zero-Person Trophy / Bind Wall language without re-heroing Dual Key” — refined here into a full badge + custody object that pairs Bind Wall / trophy language only and does not re-hero those public chapters or Interrogation vs Invitation Still.

Differentiation from c002–c007 / c014:
- c002–c006 — community do-not-ship, creator surface, byline contrast, sludge, taste.
- c007 — personal trust / warm-path inventory (who already knows your name).
- c014 — named friend Ho Tai restart boost (pending-human).
- c015authenticity / AI-pushback badge: mainstream personal-brand trust language → one signed-vs-prepared badge card for reputation under own name.


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.
This signal asset Private / warm-path / peer contribution or internal language bank — human-created badge for experts under AI-slop trust pressure. Not a public Purple Cow this cycle. Not a signup form. Not a product tour. Not Interrogation vs Invitation Still recycled.

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 badge card — contribution, not a pitch.
  • Research-only use now: phrase bank and object brief for internal drafts; never cold outreach from the Forbes URL.
  • Bind Wall / “tools prepare · human owns identity” language may echo without reprinting trophy or Meet≠Record stills as the hero.

Human-post / human-send constraint (must stay visible):
Agents must never post, schedule, comment, DM, email, 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 Human-Created Badge Card (print/PDF twin; peer gift or internal language)

  1. Title: Human-created badge
    Sub-line: Signed by me · Prepared is not posted · Silence beats average
  2. Opening strip (peer gift, not product):
    - Feeds are full of AI slop; trust lands on your name, not the model.
    - People still pay more for access to humans than for more generated text.
    - This card is a custody boundary — not a content calendar.
  3. Two columns (the core object):
    - Human-signed (public face) — byline, claims about clients or outcomes you will defend, personal messages, final publish/send, apologies and corrections
    - Tools may prepare (PREPARED only) — research notes, draft angles, outline options, fact lists marked PREPARED — incomplete until keep · change · skip · send
  4. Five authenticity checks (before any “human-made” claim):
  5. Would I put my full name on this exact sentence in public? (if no → not human-signed yet)
  6. Did a human choose send — or did a tool schedule under my face?
  7. If this were called slop in a reply, could I defend the craft choices?
  8. Am I using “human-created” as a sticker on volume work? (if yes → stop; badge without custody is marketing theater)
  9. Is deliberate silence the honest move this week? (if yes → completed professional work, not failure)
  10. 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)
    - Preparer: ___ · Date: ___
    - Completed prep · counts toward draft floor (not FAIL)
  11. Audience filter callout (explicit):
    - In: independent expert-creators, coaches, consultants, writers under own name; craft and reputation; authenticity under AI flood
    - Out: get-rich-quick / pure volume seekers; “AI that posts for me” primary buyers; scraping Forbes/LinkedIn audiences as a cold list; media authors treated as CRM rows without a real relationship
  12. Banned as hero: growth guarantees · engagement-rate claims from Forbes · capture QR · Interrogation vs Invitation Still / Zero-Person Trophy / Dual Key / Silence Credit re-hero · product carousel · inventing intros to people named only in articles

Permission-safe one-pager outline (draft shape only — human rewrites before any external use)

Human-created badge

Signed by me.
Prepared is not posted.
Silence beats average.

COLUMN A — Human-signed (public face)
(byline · claims I will defend · personal messages
 final publish/send · corrections)

COLUMN B — Tools may prepare (PREPARED only)
(research notes · draft angles · outlines · fact lists
 marked PREPARED · incomplete until I decide)

Five checks before any “human-made” claim:
1. Would I put my full name on this exact sentence?
2. Did a human choose send — or did a tool ship under my face?
3. If called slop, can I defend the craft choices?
4. Am I using “human-created” as a sticker on volume work?
5. Is deliberate silence the honest move this week?

Prepared work is incomplete until I decide:
keep · change · skip · send under my name.

Do not publish under my name this cycle unless I choose send.
Reason I held publish: _______________
Preparer: _______________  Date: _______________
Completed prep · counts toward the draft floor.

Who this is for: experts whose name is the product.
Who this is not for: volume / cold-list / get-rich-quick seekers.

No signup. No product tour. No article-comment pitch.
It prepares the work; I still send under my name.

Do not add: invented opt-in counts, LinkedIn engagement stats as proof of product-market fit, “join now,” guaranteed pipeline, claims that AI posted any content-ready pack, or any instruction to cold-message people found via the Forbes evidence URL.


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, article comment/pitch, invent warm paths, mark Contact?=approved, re-hero retired public objects
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 as primary face
Human (prospects) Skim language; map only real experts / coaches you know; optional future asset-prep language use Invent intros; treat Forbes readers as a list; outreach without approved contacts + scope
After real warm paths + scope expansion Contact review / handoff may use this badge as 1:1 contribution Outreach batch without approved contacts

Risks and ethics

  • Media segment ≠ buyer list — c015 is mainstream personal-brand discourse, not a CRM person with a warm path.
  • Author / audience scrape risk — do not invent relationships to Arruda or LinkedIn “consultants who highlight human-created work.”
  • Authenticity theater — a badge without keep/change/skip/send custody becomes empty branding; keep the two columns and five checks.
  • Status sensitivity med-high — personal brand authenticity is identity work; never shame people who used AI for prep.
  • 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.
  • Overlap with prior assets — shared custody chrome is intentional; object job is human-signed vs prepared under AI-pushback language, not trust map (c007) or friend restart (c014).
  • 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? Yesscored_permission_fit
Reason Fit clear (5/5) to own-name / authenticity / AI-slop distrust SVM; permission ladder maps to stranger value first via contribution; not demoted language-only landscape; card authorized asset prep for c015
Warm path unchanged: unknown - human to validate
Contact? unchanged: research-only
Asset path ops/asset-ideas/c015.md
Related public packs retired faces only for non-reuse: Zero-Person Trophy, Interrogation vs Invitation Still, Dual Key, Silence Credit (human post history; do not re-hero)

Assumptions

  • Public language summarized from ops/prospect-research-20260721.md rediscovery row for c015; human should verify the Forbes URL if quoting externally.
  • No named warm path exists for this segment; Contact? stays research-only.
  • Gate #20 asset-prep batch covered c002–c007; c015 is a new rediscovery package under the same research-only constraints, not an automatic outreach unlock.
  • 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).
PREVIOUS
95Remarkable asset idea — c014
NEXT
Remarkable asset idea — c01795