Launch Playbook

The 5-year launch calendar. Three loud-launch moments; everything else is quiet ship. Each launch has a checklist + a 4-week prep window + a production plan for the cinematic launch video + multi-platform repurposing across LinkedIn / YouTube / Instagram / Facebook.

This playbook is the event layer of the brand. Content Playbook covers the weekly cadence — what to publish every week for five years. This doc covers the rare moments when the cadence breaks pattern: the loud launches that anchor the program, that justify a Show HN, that go on the conference highlight reel, that the brand is remembered by.

The architecture is simple: most ROOT projects ship quiet — push to GitHub, no announcement, no production effort. The cadence keeps turning. Three to four times in 60 months, a launch goes loud — full production cycle, multi-platform distribution, blog post, video, the whole stack. That ratio of quiet-to-loud is the brand’s calmness signal. Engineers who launch every release tire their audience; engineers who launch only when the artifact deserves a launch get attention when they do.

Why ≤2 loud launches per year is the cadence

The audience-attention math is unforgiving: every loud launch costs the audience some attention budget. Loud launches every quarter exhaust trust (“another one already?”). Loud launches every two years risk being forgotten. The ROOT calendar lands on ~2/year averaged across 60 months — terralabs (Y2), basecamp (Y3), Studio + platform-ctl + aiops triple-stack (Y5), mlship + pattern paper (Y5 capstone). Y1 and Y4 deliberately have zero loud launches because the work that year doesn’t deserve them yet. Calm-but-real beats frequent-and-mid every time.

---

The launch calendar

Y1 (Months 1-12)
  No loud launches. 4 quiet ships (rxp, konfig, pulse, triage) — push to GitHub, no announcement.
  Discipline this year: shipping (PR review + CI + release). Build the multi-platform content
  cadence quietly so by Y2 you have follower base + production muscle memory.

Y2 (Months 13-24)
  Month 14 (P9):   terralabs PUBLIC LAUNCH        ← LOUD #1

Y3 (Months 25-36)
  Month 36 (P19):  basecamp PUBLIC LAUNCH         ← LOUD #2

Y4 (Months 37-48)
  No loud launches. Quiet build year. llm-gateway grows in basecamp's repo (already public).

Y5 (Months 49-60)
  Month 56 (P29):  Abukix Studio + platform-ctl + aiops marketing  ← LOUD #3 (triple-stack)
  Month 60 (P30):  mlship v2 + pattern paper                       ← LOUD #4 (capstone)

Loud launches per year averages ≤2. That’s the sustainable cadence.

---

Multi-platform launch distribution

Every loud launch hits all four content platforms — repurposed from one experience, not created four ways.

Platform        Format              Timing                        Effort
─────────────────────────────────────────────────────────────────────────────
YouTube         Long-form launch    Launch day morning            Already shot + edited
                video (3-10 min)                                  in T-2 weeks (see prep)

LinkedIn        Launch post         Launch day morning            30 min from script
                + embed video

Instagram       60-90s Reel +       Day BEFORE launch (trailer)   1 hr — cut from launch video
                Carousel             + launch day                   + carousel from blog post

Facebook        Cross-post the      Launch day evening            15 min — adapt from LinkedIn
                LinkedIn update +
                photo

Blog            Long-form launch    Launch day morning            2-4 hrs in T-1 week
                post (1500-3000w)

Show HN         (For OSS launches)  Early Pacific morning         15 min, draft from blog
                                    on launch day

Reddit          /r/kubernetes       Launch day                    cross-post relevant subs
                /r/devops

---

Generic launch checklist (4 weeks before launch day)

T-4 weeks

[ ] Define the launch artifact (what's launching) + the value prop in 1 sentence
[ ] Audit the artifact: gitleaks scan, README polish, examples runnable, CI clean
[ ] Schedule launch day (avoid major news / holidays)
[ ] Draft the blog post (1500-3000 words; based on meta/blog-template.md)
[ ] Send blog draft to 1-2 trusted readers for feedback
[ ] Plan the launch video shoot — shot list + storyboard + B-roll inventory
    (see "Production planning per launch video" below)
[ ] Plan the multi-platform repurposing — what gets cut for IG carousel?
    What's the IG Reel trailer? What's the LinkedIn lessons-learned post?

T-2 weeks

[ ] SHOOT the launch video (multi-day if needed) — see production plan
[ ] EDIT the launch video (Final Cut / DaVinci on MacBook)
[ ] Polish the README (the most-read artifact post-launch)
[ ] LinkedIn post drafted
[ ] Show HN post drafted (if applicable; Y2/Y5 launches yes, Y3 maybe)
[ ] Verify all internal cross-references work (basecamp → terralabs links, etc.)
[ ] Test installation / quick-start path on a fresh machine
[ ] Cut a 60-90s short-form trailer from the launch video for IG Reels / YouTube Shorts
[ ] Cut a carousel for IG (5-10 slides — what is it / why / how / lessons / next)

T-1 week

[ ] Post-launch monitoring plan (cost dashboard; demo cluster cost cap)
[ ] Support channel decided (GitHub issues only; no Discord/Slack until Y5+)
[ ] Pin the launch tweet/post draft in 1Password for launch-day execution
[ ] Final dry-run of launch video to verify accuracy
[ ] Schedule the IG Reel trailer to drop the day BEFORE launch (build anticipation)

Launch day

[ ] Push the tagged release
[ ] Publish blog post on abukix.dev/blog
[ ] Post launch video on YouTube + embed in blog
[ ] Post on LinkedIn (with link to blog + GitHub + video)
[ ] Post on Show HN (early Pacific morning is canonical)
[ ] Cross-post to /r/kubernetes, /r/devops, /r/MachineLearning (where relevant)
[ ] Instagram: post the carousel + the 60-90s Reel
[ ] Facebook: cross-post the LinkedIn update with the photo
[ ] Update program/story.md with the launch paragraph
[ ] Update README badges if any (build status, latest release, etc.)

T+1 day

[ ] Triage all GitHub issues opened in launch window
[ ] Respond to top Show HN comments (calm, specific; no defensive tone)
[ ] Add any "where's the docs for X?" links into the README
[ ] Note in ops-handbook/contributions/ what worked and didn't for next launch

T+1 week

[ ] Post a "what happened in launch week" tweet/LinkedIn (numbers + lessons)
[ ] Triage any backlog of issues
[ ] If applicable: ship the first post-launch patch (small, visible, builds trust)
[ ] Cut a second short-form (a "1 week later" reflection) for IG Reels / YouTube Shorts

---

Production planning per launch video

The launch video is the highest-leverage artifact of each loud launch. Apple product film aesthetic — system as protagonist, voice-over narration, intentional pacing, optional subtle music. Voice-over only — no face on camera (see Content Playbook).

Why the video is load-bearing — the 5-year math

A loud launch produces five distribution surfaces (blog, YouTube, LinkedIn, Show HN, Instagram). Of those, the launch video has the longest discoverable lifespan: a YouTube video keeps showing in search and recommendations for years; a blog post does too but lower-ranked; a LinkedIn post peaks in 48 hours and decays; a Show HN front-page moment is hours long. Investing 8-15 hours into a launch video that lands ~50% of long-tail discovery is structurally correct. Investing 15 hours into a LinkedIn post that decays in 2 days is not. The launch video is the artifact that keeps paying back compound interest after launch week ends.

Pre-shoot (T-4 to T-3 weeks)

[ ] Shot list — every scene, every B-roll piece, every UI overlay
[ ] Storyboard — rough sketches or screencap mockups
[ ] Voice-over script — written + read aloud + revised; 200-400 words for 3 min
[ ] B-roll inventory:
    - Tech B-roll: hands on keyboard, terminal output, dashboards, ArgoCD UI,
      the homelab on a shelf, the M70q's status LED
    - Lifestyle B-roll (light, supporting): morning run, sunrise, Sunday weekly log
      being written, plant-filled apartment shots — used SPARINGLY for warmth, not as
      the headline
    - The launch artifact in action: terraform plan running, mlship deploying, etc.
[ ] Audio plan: lavalier or shotgun mic for voice-over; ambient music if used
[ ] Repurposing plan: which 60-90s clip becomes the IG Reel trailer? Which 5 slides
    become the IG carousel?

Shoot day(s) (T-3 to T-2 weeks)

Block 2-4 hours of dedicated shoot time per video. Can split across multiple sessions:
  Session 1: tech B-roll (desk + hands + screens) — the bulk of the footage
  Session 2: lifestyle B-roll (morning + run + sunset) — light, supporting
  Session 3: voice-over recording (separate, in quiet room)
  Session 4: pickups for anything missed

Tools:
  Camera:    iPhone (latest) on tripod / gimbal
  Lighting:  natural light + 1 soft key light for desk shots
  Audio:     lavalier mic for VO; clean recording in a quiet room

Edit (T-2 to T-1 weeks)

8-12 hours of editing per launch video.
  Final Cut Pro OR DaVinci Resolve on the MacBook (homelab/macbook-setup.md).
  Floating UI overlays: motion graphics from After Effects OR built in Final Cut.
  Subtitles: auto-generated then hand-corrected; muted color (NOT Tulio's amber).
  Music: subtle if used; royalty-free or sourced cleanly.
  Color grading: cool-toned, system-focused — not warm-lifestyle-influencer.

Multi-platform cuts (additional 2-3 hrs):
  - 60-90s IG Reel / YouTube Short: punchiest 60-90s of the launch video
  - IG carousel (5-10 slides): screenshots + key insights from the video + blog post

---

Per-launch specifics

Loud #1: terralabs (Y2 P9)

Artifact:        github.com/abukix/terralabs
Value prop:      Multi-cloud Terraform + Crossplane Compositions side-by-side as a teaching artifact
Audience:        Homelabbers, platform engineers learning IaC
Channels:        Blog post + YouTube + LinkedIn + Show HN + /r/kubernetes
                 + 60-90s IG Reel + IG carousel + Facebook cross-post
Demo video:      "terralabs in 3 minutes — TF + Crossplane for the same shape" (3 min)
                 Hero shots: terraform plan/apply running across AWS + GCP + Proxmox;
                 floating UI overlays of the same Crossplane Composition.
                 Lifestyle B-roll: minimal (this is the first launch — keep tight).
Success metric:  50+ stars in launch month; 1+ inbound conversation

This is the FIRST launch — be more conservative on production scope. Launch video can
be slightly less cinematic than later ones; keep it under 8 hours of edit time. Show HN
can be brutal on first launches with rough edges.

Loud #2: basecamp (Y3 P19)

Artifact:        github.com/abukix/basecamp (private → PUBLIC at this launch)
Value prop:      Clone-and-bootstrap a 9-tier AI/data platform on K3s in <4 hours
Audience:        Homelabbers + small platform teams + curious senior engineers
Channels:        Blog post + YouTube + LinkedIn + Show HN + /r/kubernetes + /r/devops + Hacker News
                 + IG Reel + IG carousel + Facebook + KubeCon submission
Demo video:      "basecamp tour at end of Year 3 — what 3 years built" (5 min)
                 Hero shots: ArgoCD UI scrolling through the 9 tiers; Backstage catalog;
                 kubectl tours; the homelab on a shelf with M70q's LED blinking.
                 Lifestyle B-roll: more visible — sunrise, the morning run before the
                 shoot day, the Sunday weekly log that's been kept for 36 months.
Success metric:  200+ stars in launch month; 5+ active issues from real users

This is the BIG one. basecamp is the platform; this launch establishes the brand.
Pre-flight: gitleaks scan TWICE. Sanitize internal IPs. README is the most-read artifact.
Production: 12-15 hours of edit time on the launch video.

Loud #3: Abukix Studio + platform-ctl + aiops (Y5 P29)

The triple-stack is the riskiest launch in the program

Three simultaneous loud launches in ~10 weeks is the boundary case. The risk: launches start to bleed into each other, audience fatigue sets in by launch #2, the third one underperforms. The mitigation: stagger ~3-4 weeks apart so each gets its own discovery window, write each blog post to be readable independently, and give each its own launch video (no “combined” cinematic — the system-as-protagonist framing requires one system per video). If you can only ship two of the three on full production scope, pick Studio and platform-ctl; aiops can ship quieter as a deep blog post + a short demo video.

Artifact:        studio.abukix.dev (live demo) + github.com/abukix/platform-ctl (public)
                 + services/aiops/ marketing push
Value prop:      The unified developer surface on top of basecamp — built in public over 5 years
Audience:        Engineers + platform teams + AWS Community Builder / CNCF Ambassador reviewers
Channels:        Blog post + YouTube + LinkedIn + Show HN + KubeCon submission
                 + IG Reels (×3 trailers) + IG carousels (×3) + Facebook cross-post
Demo videos:     THREE separate launch videos — one per artifact:
  Week 1:  platform-ctl public release         (3-min demo: CLI workflows)
  Week 4:  services/aiops/ marketing push      (3-min demo: agent triages a real alert)
  Week 8:  Abukix Studio public launch         (5-min cinematic Studio tour)

THREE simultaneous launches in 10 weeks (P29 = ~2.5 months). Stagger by ~3-4 weeks each.
Don't collide. Each gets its own launch day; each gets its own blog post; each gets its own
launch video + IG Reel + IG carousel.

Production budget: ~40-50 hours total across the 3 videos + repurposing.

Loud #4: mlship v2 + pattern paper (Y5 P30 capstone)

Artifact:        github.com/abukix/mlship (capstone OSS launch)
                 + pattern paper published (blog at minimum; conference if accepted)
Value prop:      One command to deploy any ML model to production. sklearn → Llama 70B. Zero config.
Audience:        ML engineers + DevOps engineers + AI platform engineers
Channels:        Show HN front page (the goal) + blog post + YouTube + LinkedIn
                 + IG Reel + IG carousel + Facebook + KubeCon / SREcon submission
                 + a separate "5-year graduation" video
Demo video:      "mlship v2 — from .pkl to URL in 60 seconds" (3 min)
                 Hero shot: the command running, the URL appearing, curl request returning JSON.
                 The reveal IS the punchline. Punchy edit. Music optional.
                 Lifestyle B-roll: minimal in this video — let the system be the protagonist.

Graduation video: "5 years in — what I built" (5-10 min, separate)
                  Werner Herzog documentary aesthetic. Voice-over over montage.
                  Imagery from the full 60 months: weekly logs, code commits, homelab
                  evolution, run/sunrise/Sunday shots. The rhythm rendered visible.
                  This is the most personal video of the program.

THE launch. Aim: 200+ stars launch week, 5+ real users, inbound conversations.
Production budget: ~25 hours on mlship demo + ~35 hours on graduation video + repurposing.
The pattern paper publishes within 2 weeks of mlship launch (Year 5 graduation gate).

---

When NOT to launch

• Same week as a major industry event (KubeCon, AWS re:Invent, etc.) — you’ll be drowned out
• During known industry slowdowns (mid-December, mid-July first week) — half audience is off
• During your own heavy phase work (Y4 P25 GPU spot has $$ stakes; don’t launch in P25)
• When the artifact isn’t ready — better to slip 4 weeks than launch broken
• When the launch video isn’t shoot-ready — better to slip 2 weeks than ship a rough video

---

What “ready” looks like (gate before launch day)

[ ] README answers: what is it? why exists? quick start? next steps?
[ ] gitleaks scan green
[ ] CI green on the launch tag
[ ] Examples runnable on a fresh machine (test on a colleague's setup if possible)
[ ] Launch video recorded + edited + uploaded (private) to YouTube
[ ] 60-90s short-form trailer cut + scheduled
[ ] IG carousel (5-10 slides) ready
[ ] Blog post in draft, reviewed by 1-2 readers
[ ] LinkedIn post drafted
[ ] Cost monitoring (for hosted demos): budget alert + auto-shutdown configured

If any of these are NO, slip the launch. Calm specific launches > rushed half-baked launches.

The slip cost is always lower than the rough-launch cost

A slip costs you four weeks of waiting. A rough launch costs you the launch — Show HN front-page is a one-shot, harsh first comments cement first impressions, and the launch video can’t be recorded again with the same energy once the artifact is publicly live. The math always favors slipping. The only exception is if the slip would push past a hard external deadline (KubeCon CFP closing, conference talk recorded, etc.). Otherwise: slip without guilt. The brand’s permanence depends on every launch being calm-and-specific.

---

Cross-references

• Identity — the brand the launches serve
• Content Playbook — the channels + production aesthetic + multi-platform repurposing
• Hosting Plan — the technical surfaces being launched
• Accounts Setup — handles + domains for launch posts
• The Story — the rhythm the launches sit inside
• Master Plan — the curriculum the launches anchor
• Studio composition recipes — the demos that anchor each launch
• terralabs PLAN — Loud #1 (Y2 P9)
• basecamp PLAN — Loud #2 (Y3 P19)
• Studio PLAN — Loud #3 (Y5 P29)
• mlship PLAN — Loud #4 (Y5 P30 capstone)