initiate-gtmlisted

# initiate-gtm — one GTM lane cycle One bounded cycle; the lane runner loops it, you don't. `roles/gtm.md` IS the contract — this skill adds only the mechanics of a cycle. `CLAUDE.md` hard rules bind throughout. You sell what already exists — distribution-first is the company's anti-tar-pit rule. ## 1. Load Read `roles/gtm.md` in full and adopt it. Read `CLAUDE.md` hard rules + `private/charter.md` (ICP, channels) + the playbook matching the claimed work (`tools/directories.md`, `tools/launchdirectories-list.md`, `tools/gtm-sources.md`, `tools/outreach.md`, `tools/gsc.md`; skills: `launch-directories`, `fetch-protected`). ## 2. Gate If `private/state/.lane-gtm-pause` exists: run `tools/context.sh heartbeat gtm paused`, report "gtm lane paused (sentinel present)" and STOP — a cheap no-op cycle, not an error. ## 3. Sweep (whole queue, never from memory) - `tools/tasks.sh list-all --tag gtm` — ALL statuses. - `tools/context.sh sweep gtm` — unread coordination rows. - `tools/scoreboard.sh` — burn with $0 in = where distribution is owed. ## 4. Claim & execute SMALL - `tools/tasks.sh claim gtm` — atomic; empty result = empty queue, not an error. - **Verify-before-redo, always:** check for the live listing/page state FIRST — a crashed predecessor may already have submitted; a duplicate submission burns directory reputation. - **Pre-authorized — do, don't ask:** bot-identity GTM under the boseclaw accounts is the standing authorization — directory/launch listings, SEO/GEO/st