Examples

Sample .krs projects and the diagrams karasu renders from them. examples/ is the single source of truth; the diagrams are rendered at build time.

Getting started

Getting started — EC platform — The full drill-down: system → service → domain → usecase → resource.
EC platform — staged tutorial — The language taught one construct at a time, in seven self-contained files. Shown here at stage 3 (domain / usecase / resource); the rest are in the repository.
Splitting a system across files — One system block reopened across files via whole-file import, with deploy / organization propagation.

Payment platform — A payment system with external providers and cross-service flows.
HR tool — A human-resources tool modeled end to end.
Migration coexistence — Old and new domains side by side with @deprecated / @migration_target.
Logical + physical (deploy) — Deployment units linked to logical services via realizes.
Organization & ownership — Teams owning services, with members and contact links.
Deploy + org together — A project carrying both the physical (deploy) and organizational views.
Deploy-only file — A file whose only meaningful content is a deploy block.
Org-only file — A file whose only meaningful content is an organization block.
Styling by facet membership — [facets=<id>] in a .krs.style sheet — style by what a set an element belongs to, not by what it is.
Clients & capabilities (MCP) — client nodes with resource and capability, including an MCP client.
Multi-hub system (hato) — A real running system: two front doors and a core API fanning out to SaaS integrations, laid out with [external] nodes on the sides.

Feature samples — Small single-purpose snippets, each demonstrating one feature.