Remarkable asset idea — c007

Campaign: meta
Execution task: prepare-remarkable-asset-idea
Prospect / signal ID: c007
Segment name: HN solo consultant / expert personal trust
Date: 2026-07-14
Task id: t_36024ffe
Status: idea package (not ship-authorized; not outreach-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 with community-thread ≠ CRM + no-cold-list filters)

Signal ground (from discovery)

Field	Value
Source	Ask HN-style thread: first projects as solo engineer / consultancy
Channel / connector	forums_events_directories / hermes_web_search
Evidence URL	https://news.ycombinator.com/item?id=47822940
Public language (excerpt)	Advice clusters: become expert in one thing; go personal — face and difference visible; network so people recommend a known expert
Signal strength	high
Fit score (1–5)	5
Status sensitivity	med
Mapping status	research-only community advice thread (not a named warm contact list)

Not demoted: Gate #20 approved c007 for asset-prep language only (with c002–c006). This is a strong personal-trust / own-name signal for independent experts and solo consultants — not landscape-only competitor map (those are c008–c012). “Language only” in gate language means harvest/prep language and no HN reply/pitch — not “skip asset prep.”

SVM score (final-launch-packet)

Criterion	Score / note
Own-name expert-creator fit	Excellent — solo consultant / independent expert under own name is the core SVM; personal face and reputation are the product
Craft / reputation priority (not GRQ)	Strong — thread advice centers expertise, visible difference, and being recommended as a known expert — not growth hacks or cold lists
Distrust of autopilot / AI under byline	Good match (implied) — marketing framed as relationship + proof of craft, not spam; pairs with packet “you still send under your name”
Need for prep that still ships under human voice	Strong — pain is who already trusts me / what helps them first, not “more automated outreach”; prep stays PREPARED until they choose keep / change / skip / send
Warm-path / permission readiness	Unknown — public community advice thread; human must know the person before any 1:1; no invented intros; no HN reply as outreach
Overall fit	5 / clear scored_permission_fit (after community-thread ≠ CRM + no-cold-list filter)

Hard exclusions respected: do not target get-rich-quick seekers; do not treat thread commenters as a cold list; do not invent relationships; Contact? stays research-only; agents never reply/DM/pitch on HN.

Permission ladder fit (packet written path)

Rung	How this asset earns it (when live work is later allowed)
Attention (stranger value)	Remarkable personal trust map peer worksheet — contribution first, no capture form, no HN pitch
Public sample	Aligns with Silence Credit / Dual Key custody language and “warm paths only”; does not replace human posts of those packs
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	Map teaches which already-trusting relationships get a prepared piece first — not cold scrape
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 by final go/no-go unless human expands scope. HN: never auto-reply, DM, or pitch from agents.

Asset name

Personal Trust Map Worksheet (Who Already Knows Your Name)

One-line promise: A one-page peer worksheet for solo consultants and independent experts: who already trusts your name, who would recommend you, and what prepared piece would help them first — so marketing stays relationship + craft, never a cold list.

Godin job: Earn attention and permission before any hand-raise or review ask. Remarkable because it treats personal trust as a map — not a do-not-ship slip, not a publish-surface boundary, not a byline contrast, not a cadence sludge detector, not a taste inventory — a relationship inventory for people whose face and expertise are the offer.

Discovery seed (preserved): “Warm-path map worksheet (who already trusts your name; what prepared piece would help them first) — no cold list” — refined here into a full personal trust map object (relationship ownership) rather than another custody or content-quality card. Process, not outcome claims.

Differentiation from c002 / c003 / c004 / c005 / c006:
- c002 — HN community do-not-ship custody checklist (conversation identity / social contract).
- c003 — Creator publish-surface boundary (captions, carousels, stories).
- c004 — Distribution post quality contrast (same facts, prepared vs autopilot bylines).
- c005 — Cadence / sludge detection for founder messaging under personal brand.
- c006 — Taste / curation as moat: which human judgments remain the competitive edge when AI speeds the grind.
- c007 — Personal trust / warm-path inventory: who already knows your name and what prepared help serves them first (anti-cold-list relationship map for solo experts).

Align with Silence Credit + Dual Key (approved human posts) — deliberate pair, not a second cow

Surface	Role this cycle
Public heroes (approved)	Silence Credit — signed do-not-ship slip + PREPARED draft never KEEP/SEND; pack: ops/content-ready/20260713-silence-credit.md. Dual Key / First Gate Edition — dual-key card + unfinished prepared sleeve; pack: ops/content-ready/20260713-dual-key-first-gate-edition.md. Human posts; agents never post.
This signal asset	Private / warm-path / peer contribution — personal trust map for solo consultants who grow by being known and recommended, not by cold spam. Useful as language for content refinements or later 1:1 gift after a real warm path. Not a third public Purple Cow this cycle. Not a product tour. Not a signup form. Not an HN reply.

How they work together

Public feed: human posts Dual Key and/or Silence Credit from content-ready packs.
Warm path (only after human names a real person they know): optional 1:1 gift of this trust map — contribution, not a pitch.
Research-only use now: phrase bank and object brief for internal drafts; never cold HN replies, DMs, or invented intros.
If human posts are not live yet, do not treat this card as the public flagship substitute.

Human-post constraint (must stay visible):
Agents must never post, schedule, comment, DM, follow, or claim that Dual Key / Silence Credit were published by the machine. Human posts from the content-ready packs only.

What the contribution is (object + words)

One-page personal trust map peer worksheet (PDF/print twin; primarily 1:1 or internal language)

Title: Personal trust map
Sub-line: Who already knows my name · What would help them first · I still send
Opening strip (peer gift, not product):
- Marketing for solo experts is relationship + proof of craft, not spam.
- Your face and difference are visible for a reason.
- Start with people who already trust your name — not a scraped list.
Three columns (the core object):
- Already trusts me — people who have hired, referred, or publicly vouched for you; past clients; peers who know your craft
- Would recommend me if asked — weaker but real: people who have seen your work, sat next to you, or know your specialty
- Not yet / do not invent — strangers, cold lists, thread lurkers you have never met; leave blank rather than invent warm paths
For each real name (human-filled only):
- Name / how they know you (one line you can defend)
- What prepared piece would help them first (not a generic pitch)
- Keep · change · skip · send under my name when that piece is ready
- Permission note: only after I choose send; never agent-send
Five trust ownership checks (before any outreach language):
Do I already have a real relationship with this person? (if no → not a warm path)
Would they recognize my name without a cold intro script?
Is the prepared piece useful to them first — or only useful to me?
Would I be proud if they forwarded this under my reputation?
Am I treating a public thread as a CRM? (if yes → stop; community advice ≠ contact list)
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 contact: ___ (process language only — e.g. “no real warm path yet”)
- Preparer: ___ · Date: ___
- Completed prep · counts toward draft floor (not FAIL)
Audience filter callout (explicit):
- In: independent experts / solo consultants / expert-creators whose name is the product; craft and personal trust; grow by being known and recommended
- Out: get-rich-quick / pure cold-list seekers; “AI that finds leads for me” primary buyers; HN thread participants treated as a scraped list; thought-leaders who only comment on advice threads and are not in-market for prep help
Banned as hero: cold email scripts · HN reply templates · capture QR · growth guarantees · “scrape my network” automation · product carousel · competing public Purple Cow this cycle · inventing intros to people named only in public threads

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

Personal trust map

Who already knows my name.
What would help them first.
I still send.

COLUMN A — Already trusts me
(past clients · referrers · public vouchers
 how they know my craft — one honest line)

COLUMN B — Would recommend me if asked
(weaker but real · saw my work · know my specialty
 still not strangers)

COLUMN C — Not yet / do not invent
(strangers · cold lists · thread lurkers I never met
 leave blank rather than invent warm paths)

For each real name I already know:
- Name / how we know each other: _______________
- Prepared piece that helps *them* first: _______________
- When ready: keep · change · skip · send under my name
- Permission: only after I choose send

Five checks before any outreach language:
1. Do I already have a real relationship?
2. Would they recognize my name without a cold script?
3. Is the piece useful to them first?
4. Would I be proud if they forwarded this as me?
5. Am I treating a public thread as a CRM? (if yes → stop)

Prepared work is incomplete until I decide.
Do not contact under my name this cycle unless I choose send.
Reason I held contact: _______________
Preparer: _______________  Date: _______________
Completed prep · counts toward the draft floor.

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

No signup. No product tour. No HN reply script.
It prepares the work; I still send under my name.

Do not add: invented opt-in counts, conversion rates, “join now,” guaranteed pipeline, claims that AI posted Dual Key or Silence Credit, or any instruction to cold-message people from the HN thread 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, HN reply/pitch, invent warm paths, mark Contact?=approved
Human (content)	Post Dual Key / Silence Credit from content-ready packs	Letting agents post
Human (prospects)	Review signal; map only real solo experts / consultants you know; optional “approved for asset-prep language” already done for gate #20	Invent intros; reply/pitch the evidence thread as outreach
After real warm paths + scope expansion	Contact review / handoff may use this trust map as 1:1 contribution	Outreach batch without approved contacts

Risks and ethics

Community advice thread — c007 is a public HN discussion pattern, not a CRM person with a warm path. Do not treat thread authors or commenters as leads unless the human already knows them.
Community-thread ≠ buyer list — many voices give “go personal / network” advice without wanting prep help; map people you know, not the whole thread.
Cold-list contamination — “network so people recommend you” can be twisted into scrape-and-spam; filter cold-list / GRQ before any future mapping; keep peer-gift language relationship-first.
Status sensitivity med — personal face and trust are identity work; never shame small networks; empty columns are honest, not failure.
Platform risk — HN reply/pitch as outreach is high-visibility and blocked by workflow policy; never agent-automate.
Modest claims only — process language; no outcome proof until live evidence exists.
Live scope blocked — final go/no-go still blocks collection, invites, contacts, and sends unless human expands.
Overlap with c002–c006 — shared custody chrome is intentional (Silence Credit / Dual Key family); object differs by job (personal trust / warm-path inventory vs community checklist vs creator surface vs distribution post contrast vs cadence sludge vs taste moat). Do not ship all six as competing public cows this cycle.
Gate #20 batch complete — c002–c007 asset-prep language packages are now on disk; next machine work is standing funnel / human Dual Key post / human warm-path mapping — not inventing contacts from threads.
Qualification policy template still carries another campaign’s SVM in ops/qualification-policy.yaml — retune before live scoring; this package uses final-launch-packet.md SVM.

Score decision (advance)

Field	Value
Advance stage?	Yes → `scored_permission_fit`
Reason	Fit clear (5/5) to own-name / solo-expert SVM after community-thread≠CRM + no-cold-list filter; permission ladder maps to stranger value first; gate #20 asset-prep approved; not demoted landscape row
Warm path	unchanged: `unknown - human to validate`
Contact?	unchanged: `research-only`
Asset path	ops/asset-ideas/c007.md
Related public packs	ops/content-ready/20260713-silence-credit.md, ops/content-ready/20260713-dual-key-first-gate-edition.md (human post only)

Assumptions

Public quotes paraphrased from discovery research; human should open the evidence URL before external reuse.
“Remarkable contribution” here is preparatory: peer gift / language brief, not authorization to ship another public hero or to contact HN thread participants.
Router may next open standing funnel / daily-prospect-ops or human mapping / Dual Key post — gate #20 asset-prep IDs c002–c007 are now packaged.