Architecture

Kun is a configuration engine — not a server. It sits as the configuration layer on top of Anthropic's product suite, running both technical and business sides of Databayt.

5-Layer Architecture

Layer 5: Company Operations
  Cowork | Claude Apps | Enterprise Connectors
  Business (Aseel, Moutaz, Moed) | Content (Samia) | Ops (Sedon)

Layer 4: Coordination & Automation
  Agent Teams | Scheduled Tasks | CI/CD | Channels

Layer 3: KUN CONFIGURATION ENGINE (core value)
  CLAUDE.md | Agents | Skills | MCP Servers
  Rules | Hooks | Memory | Keywords
  (live counts: .claude/engine.json — /health flags drift)

Layer 2: Developer Surfaces (Anthropic-provided)
  CLI | VS Code | JetBrains | Desktop | Web | iOS

Layer 1: Foundation (Anthropic-provided)
  Opus 5.5 | Fable 5.1 | Sonnet 5 | Haiku 4.5 | 1M Context | Subscription

Team Roles

Layer 3: The Engine (Kun's Core)

CLAUDE.md Hierarchy

Priority (High → Low):
1. Project-level  ~/project/CLAUDE.md         — Project context
2. Repo-level     ~/project/.claude/CLAUDE.md  — Keywords, workflows
3. User-level     ~/.claude/CLAUDE.md          — Stack, preferences
4. Pattern library /Users/abdout/codebase/     — Core patterns

Agent Fleet (53 agents, two plugins)

captain (company brain — allocates, decides, never writes code)
├── Business:   revenue, growth, support, analyst, lead, funnel
├── Delivery:   product, tech-lead, ops, guardian, cloudflare, pwa
├── Engine:     quality, record, report, analyze, learn, package, clone
├── Content:    transcribe, adjudicate
└── Reference:  hogwarts, souq, mkan, shifa
        └── kun-stack → 27 specialist agents

Full breakdown: Agents.

MCP Ecosystem (20 live)

Plus the claude.ai connectors (Gmail, Calendar, Drive, PlanetScale, Vercel). Registration lives in ~/.claude.json — not ~/.claude/mcp.json, which is only a catalog. See MCP.

Rules Engine (38 domain rules + 5 cross-cutting)

Domain rules auto-load via a paths glob: react-perf (8), next-16 (6), react-19 (5), prisma-6 (4), tailwind-v4 (4), typescript-strict (4), authjs (3), neon (2), s3 (2). Five more load unconditionally: github-workflow, block-protocol, patterns, cowork-bridge, engine-parity.

Hook Automation (10 hooks)

Layer 4: Coordination

Agent Teams (Experimental)

Lead agent coordinates teammate agents, each in isolated git worktrees. No merge conflicts. Consolidated PR.

Cross-Device Flow

Phone (iOS) ──Dispatch──▶ Desktop App ──/teleport──▶ Terminal (CLI)
     ◀──────── Remote Control ──────────────────────────────┘

Scheduled Tasks

3-Channel Communication

Cowork ↔ Code Bridge

Cowork (think): plan → create issues → append to ~/.claude/bridge.md
Code (do):      read bridge.md → pick up issues → execute → write results back to bridge.md

Shared state: ~/.claude/ (agents, memory, settings, rules). Same brain, two modes.

Layer 5: Business Operations

Team Workflows

Hogwarts Pilot (King Fahad Schools)

Developer: handover admission → 5-pass QA → deploy to ed.databayt.org
Business:  Cowork → onboarding plan → Arabic welcome email → training agenda
Content:   Cowork → Arabic user guide → screenshots → voiceover

Repository Map

databayt/ (17 repos)
├── Products
│   ├── hogwarts     — Education SaaS (FLAGSHIP, daily commits)
│   ├── mkan         — Rental marketplace (Phase 1 done)
│   ├── souq         — E-commerce (MVP, paused)
│   └── shifa        — Medical platform (early, paused)
├── Libraries
│   ├── codebase     — Pattern library (54 ui + 62 atoms + 31 templates)
│   ├── shadcn       — UI components (shadcn/ui fork)
│   └── radix        — UI primitives (Radix fork)
├── Engine
│   └── kun          — Configuration engine (this repo)
├── Mobile & Marketing
│   ├── ios-app      — iOS app (Swift/SwiftUI)
│   ├── android-app  — Android app (Kotlin)
│   └── marketing    — Landing pages
└── Other
    ├── crm          — Self-hosted CRM (4 workspaces on *.crm.databayt.org)
    ├── spma         — Internal tool
    ├── apple        — Design R&D
    ├── lab          — Experiments
    ├── distributed-computer — Rust/blockchain concept
    └── .github      — Org profile

Security

Architecture Decision Records

ADR-001: Configuration Over Infrastructure

Decision: Use Anthropic's products as-is, configure don't build. Rationale: 7-person team can't maintain custom infrastructure alongside 5+ products.

ADR-002: Opus Default

Decision: Use Opus (currently 4.8) for all agents, Haiku only for explore subagents. Rationale: Quality over speed for a small team where every output matters.

ADR-003: Single Subscription Model

Decision: One Max 5x ($100/month) shared via Desktop/Web — subscription-only, no API-key spend. Rationale: $500/month burn with $5K capital = 10 months runway. Add Pro seats ($20) when revenue grows.

ADR-004: Hogwarts-First Development

Decision: All engine features validated through Hogwarts pilot first. Rationale: King Fahad Schools is the revenue pipeline. Ship what pays.

ADR-005: Shared Component Library

Decision: All products pull from databayt/codebase. Rationale: 54 UI + 62 atoms + 31 templates = don't rebuild across 5 products.

Architecture Principles

1. Configuration over infrastructure — Don't build what Anthropic ships
2. Architecture-first — Humans design, AI generates within constraints
3. Guardrails as training data — CLAUDE.md, agents, rules shape output
4. Full spectrum — Technical AND business operations
5. Anthropic-native — Use products as designed