Domain + Area + Sector Catalog
Catalog of the current Domains, Areas, and Sectors of the Koder Stack monorepo, organized per taxonomy.md. This document is a reference of what exists today; the rules that govern the structure itself live in the RFCs (rfcs/RFC-003..009).
Migration note: the paths shown here describe the target state after the RFC-003 / RFC-006 / RFC-007 / RFC-009 migrations. Until each sweep completes, the on-disk paths reflect the prior structure — see
taxonomy.md §10for migration status.
How to read this document
- Domain (L1) — top-level: how is the component consumed?
- Area (L2) — purpose/theme inside the Domain (criterion varies per Domain).
- Sector (L3) — unit of product/service identity, with proper name and lifecycle.
When you read products/horizontal/kmail/, parse it as Domain → Area → Sector.
products/ — Direct interaction (UI/DX, brand, end users)
Components consumed by direct human interaction. Have UX/DX, brand identity, and onboarding flows. L2 criterion: audience model.
products/horizontal/ — B2C horizontal (any user, any industry)
Sectors that any person can use, regardless of industry. Renamed from suite/ per RFC-007.
| Sector | Description | Engine + product pair |
|---|---|---|
kmail/ |
Email platform | Raven (B2B) + Kmail (B2C webmail) |
cal/ |
Calendar / scheduling | — |
drive/ |
File storage and sharing | — |
talk/ |
Messenger (Noise + Protobuf + Signal) | — |
play/ |
Video / music streaming | Media (B2B) + Play (B2C) |
pulse/ |
Social network | Orbit (B2B) + Pulse (B2C) |
poly/ |
Language learning | Verba (B2B) + Poly (B2C) |
beats/ |
Music platform | Cadence (B2B) + Beats (B2C) |
lingo/ |
Translation platform | Idiom (B2B) + Lingo (B2C) |
learn/ |
E-learning / LMS | Academia (B2B) + Learn (B2C) |
kampus/ |
Campus management | Campus (B2B) + Kampus (B2C) |
crew/ |
HCM / workforce management | B2B only |
take/ |
Cinephile social network (Letterboxd-style) | — |
tune/ |
Smart-TV media app | — |
products/vertical/ — B2B vertical (industry specialist)
Sectors targeting a specific industry, with regulatory exposure and specialized workflows.
| Sector | Description | Engine + product pair |
|---|---|---|
clinic/ |
Healthcare — EHR, openEHR, telemedicine | Health (B2B) + Clinic (B2C) |
home/ |
IoT / smart home | Ion (B2B) + Home (B2C) |
invest/ |
Fintech / trading | Exchange (B2B) + Invest (B2C) |
helo/ |
Service marketplace | Rova (B2B) + Helo (B2C) |
edictus/ |
Public-tender (licitação) management | — |
products/dev/ — B2D (developer / technical operator)
Sectors with technical buyer/user — developer experience is the product.
| Sector | Description | Engine + product pair |
|---|---|---|
flow/ |
Git forge | — |
kterm/ |
Terminal | — |
sky/ |
Multi-cloud management | Nimbus (B2B) + Sky (B2C) |
store/ |
App distribution — Koder Hub | Depot (B2B) + Store (B2C) |
kode/ |
IDE for the Kode language | — |
services/ — API call (network, no end-user UX)
Backend services consumed by products and other services over the network. Deployed as servers. L2 criterion: functional domain.
services/foundation/ — Cross-product primitives
Services every other component depends on.
| Sector | Description |
|---|---|
id/ |
Koder ID — identity and SSO |
billing/ |
Subscription and invoice management |
payments/ |
Payment processing |
moderation/ |
Content moderation |
ads/ |
Advertising platform |
kompass/ |
Universal organization management (paired with the Mosaic consumer app) |
reporter/ |
Backend for error reporting (consumed via KoderErrorReporter) |
keys/ |
Vault / secrets backend (paired with the Pass consumer app) |
services/ai/ — Artificial intelligence services
| Sector | Description |
|---|---|
gateway/ |
AI gateway (model routing, rate limits, billing) |
kortex/ |
DevOps AI brain |
voice/ |
Voice / TTS / STT service |
runtime/ |
Inference runtime |
recsys/ |
Recommendation system |
agents/ |
Agent platform |
rag/ |
Retrieval-Augmented Generation |
services/media/ — Audio/video processing
| Sector | Description |
|---|---|
| (under definition) | Transcoding, streaming, manifest services |
engines/ — Embedding (import + execute locally)
Reusable artifacts imported as dependencies. Stateless or nearly stateless, portable across backends, frontends, CLIs, WASM. Not network services. L2 criterion: functional domain.
engines/kodec/ — Audio/video codec
| Sector | Description |
|---|---|
kodec/ |
The codec — Rust core + C ABI + WASM + GoPythonRust bindings + CLI |
engines/lang/ — Kode language ecosystem
| Sector | Description |
|---|---|
kode/ |
Kode language — compiler, runtime, stdlib |
kmd/ |
Koder Markup Document format and tooling |
engines/sdk/ — Client libraries (external + internal)
External SDKs distributed to third parties:
| Sector | Description |
|---|---|
go/ |
Koder Go SDK |
js/ |
Koder JavaScript SDK |
python/ |
Koder Python SDK |
dart/ |
Koder Dart/Flutter SDK |
rust/ |
Koder Rust SDK |
Internal libraries shared across Koder apps:
| Sector | Description |
|---|---|
koder_kit/ |
Flutter UI kit (theme, layout, auth widgets, error widgets, settings page) |
koder_ipc/ |
IPC primitives between Koder apps |
koder_player/ |
Audio/video player widget for Flutter |
koder_web_kit/ |
Web components for landing pages and PWAs |
infra/ — Operation (deploy + configure substrate)
Infrastructure substrate that products and services depend on operationally. Not imported as libraries. L2 criterion: infrastructure function.
infra/net/ — Network, security, edge
| Sector | Description |
|---|---|
jet/ |
Web server (HTTP, TLS, vhosts) |
mesh/ |
Service mesh |
vault/ |
Secrets storage substrate |
dns/ |
Internal DNS |
infra/data/ — Storage and pipelines
| Sector | Description |
|---|---|
kdb/ |
Koder Database |
queue/ |
Message queues |
search/ |
Indexing and search |
blob/ |
Blob storage |
pipelines/ |
Data pipelines |
infra/observe/ — Observability
| Sector | Description |
|---|---|
apm/ |
APM / distributed tracing |
log/ |
Log aggregation |
wire/ |
Network diagnostics |
infra/linux/ — Operating system
| Sector | Description |
|---|---|
distro/ |
Koder Kodix distribution |
desktop/ |
Koder desktop environment |
meta/ — Reading (humans, not runtime)
Non-deployed-runtime artifacts: documentation, brand assets, landing pages, agent infrastructure configuration. L2 criterion: artifact type.
meta/brand/ — Visual identity
| Sector | Description |
|---|---|
koder/ |
Koder Stack brand assets |
crescer/ |
Crescer brand assets |
vivver/ |
Vivver brand assets |
meta/docs/ — Stack normative documentation
| Sector | Description |
|---|---|
stack/ |
The Stack documentation collection — RFCs, vocabulary, taxonomy, areas (this catalog), modules, specs, policies |
(Future siblings: legal/, research/, talks/.)
meta/sites/ — Web presence (above-Sector)
| Sector | Description |
|---|---|
stack/ |
www.koder.dev — Koder Stack home |
company/ |
company.koder.dev — institutional |
platform/ |
platform.koder.dev — product catalog |
areas/ |
Landings for each L2 Area (<area>.koder.dev) — single Sector with nine sub-trees: horizontal/, vertical/, dev/, foundation/, ai/, media/, data/, observe/, linux/ |
meta/context/ — Agent infrastructure configuration
Operational configuration of the Claude Code harness. Loaded by tooling, not by humans as reference (specs and policies — Stack normative docs — moved to meta/docs/stack/ per RFC-009).
| Sub-folder | Purpose |
|---|---|
claude/ |
settings.json, .mcp.json, hooks |
commands/ |
Slash commands (skills) |
credentials/ |
Local secrets |
infrastructure/ |
Serverserviceaccount catalog |
registries/ |
Accumulating state |
CLAUDE.md |
Harness entry point (symlinked to ~/.claude/CLAUDE.md) |
reminders.md |
Personal reminders |
The horizontal vs. vertical distinction
Within products/, the L2 split between horizontal/ and vertical/ is the most consequential one for product strategy. Visualize the Stack as a grid:
| Horizontal Sectors | Vertical Sectors | |
|---|---|---|
| Audience | Any person, any industry | Specialist in one industry |
| Product strategy | Generic UX, broad utility | Industry workflow, regulatory awareness |
| Pricing | Freemium, low ARPU, high volume | Per-seat, high ARPU, lower volume |
| Sales | Self-serve, viral growth | Direct sales, long cycles |
| Examples | kmail, cal, drive, talk |
clinic, invest, helo |
Boundary test: *"Would I pitch this product to a customer outside industry X?"* — if yes (e.g., calendar, email), it is horizontal; if no (e.g., EHR, trading), it is vertical.
The B2D Area dev/ is the third audience model: developers and technical operators who buy on technical merit, not industry fit. See RFC-007 for why audience model (rather than industry scope alone) is the L2 criterion.
Engine + product pairs
Multi-tenant SaaS Sectors typically ship as two named products: a B2B white-label engine and a B2C flagship. They share the same Sector and split at L4 via <brand>/. Full registry in engine-product-pattern.md.
Known caveats
take/(cinephile social) is in scoping — name confirmed2026-04-27, implementation pending.
services/media/is reserved but has no concrete Sectors yet;candidate names and scope under definition.
services/ai/agents/andservices/ai/rag/are anchored asSectors; concrete sub-components evolve quickly.
infra/data/queue/,search/,blob/,pipelines/are placeholder Sectors — the corresponding components currently live outside the monorepo or under legacy paths.
engines/sdk/koder_kit/is a hybrid (component library + framework+ library) — not a pure SDK, but classified under
sdk/because it is consumed by embedding inside Koder apps.