[swarm][punkrockai] Turn Punk Rock AI and cut-up generator search traction into durable project pages

[WalksWithASwagger]

Swarm packet — search opportunity + agent-domain infrastructure

Repo: WalksWithASwagger/cmvan-keynote
Suggested owner lane: Hanuman / Punk Rock AI worker
Source/evidence: Fresh Search Console opportunity pull, 90-day range ending 2026-07-16, plus Kris request to double down on surprising working terms and encode domain knowledge as automation/docs/agent rules.

Why this exists

Punk Rock AI is getting search traction for “punk ai” and the cut-up generator. That deserves a small authority loop around creative AI, keynote artifacts, and tools.

Keywords / entities to care about

• punk ai
• cut up generator

Goal

Improve discoverability and interlinks for Punk Rock AI keynote/tool pages.

Scope

• Audit punkrockai.com/current repo deployment path and confirm whether this repo owns it.
• Improve metadata/schema for Punk Rock AI homepage and cut-up generator page where applicable.
• Add links to Kris profile, Creative Mornings/keynote context, BC AI creative AI ecosystem, and FutureProof if relevant.
• Add agent docs if missing so future agents understand the content/voice.

Acceptance criteria

• Repo ownership is confirmed or redirected to correct repo.
• punk ai and cut up generator have target page actions.
• Relevant pages link into Kris/BC AI network without feeling spammy.
• Agent docs encode content style and verification commands.

Interlinking targets

• kriskrug.co Punk Rock AI posts/profile
• bc-ai.ca creative AI ecosystem
• futureproof.website if programming overlap exists

Boris doctrine / agent infra requirement

Do not leave domain knowledge in someone's head. Encode the repo-specific patterns in durable infrastructure:

• AGENTS.md or CLAUDE.md tells agents the site purpose, key entities, allowed actions, content model, style/schema conventions, and verification commands.
• Add or update REVIEW.md if the repo has repeat review failures agents should catch.
• Add tests/lints/scripts/checklists for repeatable SEO/schema/internal-link/metadata validation where practical.
• Keep public publishing, DNS, account changes, sends/posts, deletes, and production credential changes owner-gated unless Kris explicitly approves.

Verification

• Repo-specific lint/test/build command passes, or issue documents the honest unavailable command.
• New/updated pages include title/meta/H1/canonical/OG basics.
• Relevant schema is present where appropriate: Person, Organization, Event, Article, FAQPage, BreadcrumbList.
• Internal links are added in both directions where useful.
• No duplicate/inflated analytics claim is used as evidence without canonicalization.

PR boundary instruction

Open one focused PR with evidence and stop at PR boundary. If this reveals missing analytics/property setup, link back to Mission Control issues #71/#72/#76 rather than expanding scope silently.

[AlexandrStarDev]

Hi @WalksWithASwagger, Just interesting. Please assign me and let's connect. Thanks