Skip to content

Start here

Welcome to SCAILE. This playbook is the operating manual for the whole team — the shared context every new joiner needs, plus a guide for each role. Whatever seat you're in, start here instead of pinging the team.

How to read this

Two layers:

  • Durable (the shared sections + your role guide). SCAILE context, how we work, tools, where things live, decision rules, the team, and glossary — plus the guide for your role. Read these once; they change rarely.
  • Living (living layer). Current ventures, clients, and priorities. These go stale fast. Never trust a figure older than the page's last-reviewed line.

Everything points to where knowledge actually lives — when a page links out, follow the link rather than expecting the answer copied here. The canonical company write-up of most things is the internal knowledge base on GitHub: scaile-knowledge-base (needs scailetech org access). Where each kind of knowledge lives is mapped in knowledge-map.md, and the repos themselves in the GitHub map.

Find your role

Go to Roles and open the guide for your seat. The Founder's Associate guide is fully written; the Engineering, GTM, Product, and Operations guides are stubs their functions are filling in. The shared sections already apply to everyone, so you can be productive on day one whatever your role.

Day 0, whatever your seat

  1. Get every access provisioned — work the Day 0 checklist. Anything under scailetech (GitHub, Vercel, Supabase) that's missing is a day-1 request, before any code — never a personal account.
  2. Learn where things live — knowledge-map.md for knowledge by type, and the GitHub map for the scailetech repos.
  3. Set up the stack — tools overview, including Claude Code + MCPs.

You can also query this playbook in Claude Code instead of reading — ask in plain language and it answers from the source.

If you're joining as a Founder's Associate

You shadow one co-founder and run his operating backbone: you prepare, he cross-checks. Start with the onboarding guide — one self-contained page with a Day 0 checklist, the briefing/naming/language rules, and how to install and run Claude Code. Then read the rest in this order:

  1. 01-role/what-is-the-fa.md — the definition.
  2. 01-role/ownership-and-limits.md — what you own, support, and stay out of.
  3. 01-role/30-60-90.md — the benchmark you're measured against.
  4. 02-scaile-context/what-is-scaile.md — what SCAILE is and why it wins.
  5. 04-fa-operating-loop/the-core-loop.md — the atomic motion you repeat all day.
  6. 06-where-things-live/knowledge-map.md — where to look for anything.
  7. 05-tools-and-workflows/overview.md — the stack; set up Claude Code + MCPs.
  8. 08-setup-and-access/day-zero-checklist.md — confirm every access is provisioned.

Week-one task: map the account and access chaos and propose a consolidation — see 06-where-things-live/account-and-access-map.md.

The one rule for the FA: the FA prepares, the founder cross-checks. You hand him a draft, never a blank page.

Owner: Current FA Last reviewed: 2026-07-03