Knowledge map¶
Where each kind of knowledge actually lives today. Reference these — don't duplicate them.
The source of truth is increasingly a GitHub repo in the scailetech org — you can open any of them in Claude Code and ask (see Query in Claude Code). The full repo tour is the GitHub map.
| Type of knowledge | Where it lives |
|---|---|
| Company knowledge base (humans + agents) | GitHub — scaile-knowledge-base |
| Company strategy & decisions | Simon's email inbox |
| Client context & briefs | Slack + email + GitHub |
| Venture ideas & builds | Notion + email |
| Engineering docs & code | GitHub — scailetech org |
| Meeting notes | Granola + Fireflies |
| Active development tasks | Linear |
| Client / contact database | Twenty CRM |
- Company knowledge base — GitHub (
scaile-knowledge-base). SCAILE's internal knowledge base for humans and agents — company context, GTM, clients, and team, written up canonically. Reach for it when you want SCAILE's own source of truth on something rather than a live tool; needsscailetechorg access. The full repo map is the GitHub map. - Company strategy & decisions — Simon's inbox. Direction gets set in his email threads, so the inbox is the canonical record; look elsewhere only when a call settled it (check Granola) or it played out in a Slack thread.
- Client context & briefs — Slack + email + GitHub. Context lands wherever the client and team happen to talk, so it is spread across all three; start in the project's Slack channel, then go to email for a forwarded brief or the repo for a committed asset.
- Venture ideas & builds — Notion + email. Notion holds the live build because that is where you maintain it; drop back to email when you need the origin pitch or the "why we started." The venture's code build lives in its
venture-*repo in GitHub — see current ventures. - Engineering docs & code — GitHub (
scailetech). Docs live next to the code they describe, so read the repo for how something works; switch to Linear when you want status rather than implementation. See the GitHub map for the org at a glance. - Meeting notes — Granola + Fireflies. Granola is the default capture, so reconstruct any decision or action item there first; fall back to Fireflies only when a meeting was not recorded in Granola.
- Active development tasks — Linear. It is engineering's board, so it shows what is in flight; read it for context but never write to it, and go to GitHub for the actual change or Slack for the discussion around it.
- Client / contact database — Twenty CRM. It is the system of record for contacts and pipeline, so keep it current there; look at
#salesor email when you need the live conversation behind a record.
The worst silo: account and access¶
Account and access management is the worst silo, named by the co-founder. The known fragments (multiple admin inboxes, a separate tech@scaile.it domain, scattered invoices) are catalogued on the account and access map — that page is where the consolidation gets documented.
Mapping this and proposing a consolidation is your week-one task.
Owner: Current FA Last reviewed: 2026-07-03