GitHub map

All of SCAILE's code — and much of its written knowledge — lives in the scailetech GitHub org. Everything is private and needs org access: if you can't see a repo, that's a day-1 access request, never a personal account.

This page orients you to where to find what. Which repos a given role actually reads or writes in is still being mapped — see the open question below.

Start here — company knowledge

Repo	What's in it
scaile-knowledge-base	The internal company knowledge base for humans and agents — company context, GTM, clients, team. Start here for SCAILE's own canonical write-up of something.
venture_knowledge_storage	Venture knowledge store — the briefs and context behind the ventures.
venture_skill_Anton	Shareable GEO venture toolkit: Claude skills, GEO docs, and the article-generation pipeline + agent briefing.
content_intelligence	Inputs, outputs, schemas, and prompts for content work.
playbook	This playbook.

The engine

Repo	What's in it
venture-factory	Turns a venture brief into a GEO-optimized site and exports it as a standalone repo the owner deploys. See the venture factory model.
formbuilder	AI-generated multi-step lead forms; used standalone and consumed by venture-factory via API.
blog-engine · newsletter-engine	Content-generation engines (articles; multi-client newsletter).

Ventures, clients, and GTM — by naming convention

The org is large, so it leans on prefixes. Browse the org filtered to a prefix rather than hunting for a single repo:

Prefix	What it is	Browse
venture-*	One repo per venture build (e.g. venture-solardachmuenchen, venture-ledgerly), plus branded venture repos like Nextgentic, reiseinsblaue, foundercover.	venture- repos · current ventures
client-*	One repo per client engagement (~50, e.g. client-beurer, client-werob).	client- repos · current clients
gtm-*	SCAILE's own go-to-market builds, plus the marketing site (scaile-website-astro, strapi_cms_scaile_website).	gtm- repos

Platform, product & design

platform, content_intelligence, product-UI-Mock-Up, tech-design-system (colors, typography, components), scaile_video_engine, social_listening_service.

Open question — which repos matter for which role

Still being mapped

Which repos each role is expected to read or write in — and what to look for in each — is owned by August and isn't fully drafted. Until then the default holds: read for context, write only on explicitly assigned repos, never touch the rest. See when-to-involve-engineering.md.

---

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