Skip to content
ROOT
BRAND

Overview

The public surface of ROOT. Identity, accounts, hosting, content, launch playbooks. Built incrementally across 5 years; loud-launches reserved for artifacts that earn it.

The brand directory is the outside of the program. Inside, ROOT is a 60-month curriculum of phases, runbooks, weekly logs, and pattern entries — see the Master Plan for the structural map and The Story for the narrative arc. Outside, the same work has to be legible: a name people can repeat, a domain that hosts the artifacts, a cadence that produces evidence, and a launch calendar that protects the loud moments from being burned on the wrong week.

Five docs sit underneath this index. identity.md defines what Abukix Studio is and what it deliberately doesn’t promise. accounts-setup.md is the identity layer (GitHub, domain, email, social). hosting-plan.md is where each public surface lives on Cloudflare. content-playbook.md is the four-platform repurposing system. launch-playbook.md is the 5-year launch calendar with per-launch checklists. Read them in roughly that order — identity sets the spine, the rest hang from it.

Pages

DocWhat
identity.mdAbukix Studio identity — what it is, audience, what NOT to promise
accounts-setup.mdGitHub, domain, email, social handles
hosting-plan.mdCloudflare Pages + Access setup; the preview-deployment-access gotcha
content-playbook.mdWhat to publish, where, cadence (blog + cinematic + LinkedIn)
launch-playbook.mdWhen to launch what; the 5-year launch calendar

The 5-year brand arc

Y1: invisible          all 4 quiet ships (rxp, konfig, pulse, triage); no launches
Y2: first launch       terralabs (P9) — first time you let the world see you ship
Y3: brand rises        basecamp goes public (P19); 1 blog post / month from here
Y4: build credibility  llm-gateway in prod, notes-rag dogfoods; quiet posts about platform depth
Y5: launches stack     Abukix Studio (P29) + mlship v2 (P30) = the year that puts the abukix
                       name on the map; pattern paper publishes

The arc is deliberately back-loaded. Year 1 is invisible because the artifacts aren’t ready to defend in public. Year 2 introduces the brand to a small audience around terralabs. Year 3 is the inflection — basecamp going public flips the program from a private journey into a public surface anyone can clone. Year 4 is a quiet year by design; the work is too deep to interrupt with launches. Year 5 stacks the loud moments into a single arc: Studio, mlship, the pattern paper, graduation.

Brand discipline

Three rules:

  1. Don’t launch what isn’t ready. Year 1 ships exist (publishing builds the discipline) but launches are deferred until they earn the energy.
  2. Patterns from public sources only. Avoid internal-employer-isms or any employer-confidential framing in public content. Stick to KubeCon talks, OSS code, public papers.
  3. One sentence positioning. “AI platform engineering, in public, from kernel to LLM.” That’s the brand line. Everything else hangs from it.

What NOT to do

  • Don’t post on LinkedIn just because it’s been a week
  • Don’t ship “thoughts on $TOPIC” hot takes — engineering writing has cold-take energy
  • Don’t recreate work-confidential internal tools as public OSS (legal + brand risk)
  • Don’t promise hosted compute at scale — “free for community” doesn’t mean “free hosted” (see identity.md 3-tier model)
  • Don’t burn yourself out producing content during heavy phases (Y4 P25 / Y5 P30 capstone — give yourself permission to skip)

Cross-references