Why it spreads

Every PR is a front door.

The cloud maintainer opens PRs on other people's repos — the one surface a stranger actually sees. It just opened its first one, end-to-end. So every PR carries a footer: a human-merge attestation, and an invite. See the fix, want one, onboard in three commands, and now your team's PRs recruit the next. The loop closes itself.

The loop, made explicit

Bot PR → landing → 3 commands → their PRs.

A benchmark reaches the people who read benchmarks. A proven PR on your own repo reaches every teammate and every drive-by who opens it. That reach is the growth engine — so the PR footer is the front door.

heimdall opened a pull request OPEN · awaiting review
Heimdall fix: flaky auth test in payments
heimdall/issue/flaky-auth-test → main
falsify · assertion oracle scored 1.0 lint · tests · green SI-2 attestation · evidence attached
Opened by Heimdall's issue-resolution loop on a gate-PASS fix. Autonomy ends here — a human reviews and merges. Heimdall does not self-merge.
Want a bot like this on your repo? → runheimdall.dev
# the footer is the front door — every PR the bot opens is a funnel entrance
The compounding part

Four edges, and the last one loops.

A dev sees the bot's proven PR on their repo. The footer invites them. They onboard in three commands with their own Claude sub and GitHub App. Now the maintainer opens PRs on their repo — each one carrying the same footer to the next team. No shared keys to hand out; the loop scales itself.

bot opens a proven PR footer → runheimdall.dev 3 commands · BYOC their team's PRs compounds
The hook · a proof you can post

The kill-cards.

Benchmarks are tired. A screenshot of a gate saying no is not. Every card below is emitted by a real Heimdall run — the moment the watchman blocks a placeholder, slams the bridge shut, kills a mutant, or trims the fat. Post the receipt, not the claim.

run receipt · one card, whole run
$ hmd --team 5 "ship the feature" heimdall · run receipt · swarm + gates, one card swarm 5 agents · architect → coder → reviewer → verifier falsify ···· 1.0 corpus ···· 13 / 13 lint · tests ···· green Δ LOC your run's net · bloat-gated cost tracked in-session verdict: PROVEN — nothing ships unproven
One card for the whole run: the swarm, every gate green, the diff bloat-gated, spend tracked. The post that says "this is what shipping with a watchman looks like."
content-gate · pre-write
$ hmd "add the retry helper" heimdall · content-gate · pre-write scan content-scan BLOCKED throw new Error('not implemented') src/net/retry.ts:14 verdict: DENIED — no placeholder ships # the agent tried to fake it. the gate said no.
Heimdall blocked a placeholder. The single most relatable dev-tool moment of 2026 — caught at the write, not in review.
pre-push · the bridge
$ git push origin main --no-verify heimdall · pre-push · 6 gates lint-clean FAILED ⛔ BIFRÖST CLOSED push rejected — the bridge stays shut until proven # --no-verify can't open the bridge.
BIFRÖST CLOSED. The gate-deny clip — the watchman shuts the rainbow bridge and --no-verify can't reopen it.
oracle · falsify · mutation kill
$ hmd falsify --assert-score 1.0 oracle · mutation kill · the check can actually fail mutant 1 killed mutant 2 killed mutant 3 killed score: 3 / 3 = 1.0 verdict: PROVEN — perfect kill, no partial credit
3 / 3 = 1.0. The falsify kill-card: an oracle that can actually go red, and did its job. Perfect score or the merge waits.
bloat-gate · debloat scorecard
$ /hmd:debloat heimdall · bloat-gate · dead-code scan dead exports pruned unreachable removed duplicate logic merged Δ LOC ↓ net negative verdict: LEANER — bloat caught before it lands
The diff that goes down. The debloat scorecard — the rare PR where AI removes more than it adds, and a gate proves it.
Screenshot-ready · every run emits one · numbers are real (falsify 1.0 · corpus 13/13)
Go-to-market

The first 100 users.

Seven plays, each mapped to a concrete Heimdall move. The through-line: Heimdall generates the shareable asset for free — every run is a receipt.

01

Launch-max

YC play: more launches = more eyeballs. Ship on every platform, at least 3×.

Launch on Product Hunt, Hacker News, Peerlist, Indie Hackers, Devhunt, BetaList — minimum 3× each. Lead every listing with the BIFRÖST CLOSED deny-clip, not a feature list.

02

Steal the backlinks

YC play: get listed everywhere your competitors are listed — then make a better listing.

Get Heimdall into every directory that lists Cursor, Copilot, and Claude Code tooling — AI-dev roundups, awesome-lists, tool comparisons. The angle they can't match: a verification layer with a published proof.

03

Warm outbound

YC play: capture the 99% who saw the content but never came inbound.

Scrape the engagers on each viral receipt post, ICP-fit check (ships AI-written code, feels the trust gap), then a personal message — reference the exact post they liked. Automate the pipeline, keep the message human.

04

Hire UGC creators

YC play: a bench of creators making native, in-feed clips.

Sign 20–30 dev-tool UGC creators on TikTok / X at $15–30 a clip plus performance incentives. The brief writes itself: dare your agent to cheat, film Heimdall catching it.

05

Videos > everything

YC play: video out-performs image and text roughly 10×.

The hero video is the kill clip: "I dared Claude to fake it → Heimdall blocked it → BIFRÖST CLOSED." Cut use-case shorts on top and post them across X and LinkedIn.

06

Show up where they are

YC play: go to the rooms your customers already sit in.

AI-coding Slack / Discord communities, dev newsletters, podcasts, r/LocalLLaMA, and paid shoutouts. Show, don't pitch — drop a receipt when it's on-topic.

07

Ride every trend

YC play: attach to whatever is already moving this week.

Track the weekly X AI-coding trend and fold Heimdall in. Quote-tweet the viral "is AI coding even real / it hallucinated again" posts with a receipt — the reply is the demo.

Framework adapted from YC's first-100 playbook — mapped to what a verification tool can uniquely do.

The second loop

And every run ships its own marketing.

The bot PR isn't the only asset. Heimdall makes one on every single run — a screenshot or clip of a gate doing its job. Post it (plays 1, 5, 7); a dev tries it; their run emits their receipt; they post that. Two loops, same engine.

run emits a receipt post it dev tries Heimdall they post their receipt compounds
Start the loop

Onboard your team, and let the first PR do the rest.

Three commands, your own credentials, MIT. The first proven PR the bot opens is the first front door you own.

Get started