A four-layer operating system where Claude serves as the central intelligence layer. A personal infrastructure for thinking, building, and knowledge management.
Canonical Architecture (Vertical Layers)
| Layer | Name | What It Does | Status |
|---|---|---|---|
| L1 | Data Layer | Automated intelligence from bookmarks and knowledge sources | Operational |
| L2 | Configuration Engine | Global Claude configuration across devices and projects | Operational |
| L3 | Project Work | Career, Seka Works, ONC, Finance -- the work that ships | Operational |
| L4 | Autonomous Operations | Agentic infrastructure for persistent automated tasks | Blueprint delivered, not yet executed |
Horizontal Planes (Control Systems)
Three planes cut across all vertical layers:
Context Plane
Pre-loaded domain knowledge. Design principle: "context is always pre-loaded, never reconstructed mid-session." Lives in project instructions, knowledge files, and memory edits.
Governance Plane
Safety, approval gates, audit trails. Key primitives:
- Approval gates: any action above cost/risk threshold requires human approval
- Budget scoping: per-agent spend tracking
- Audit logging: append-only logs per agent per day
- Rollback: Git-versioned config changes, revert to last known good state
Orchestration Plane
Agent coordination and state management. Key primitives:
- Goal ancestry: every task traces to a stated objective
- Agent state persistence: machine-readable YAML/JSON
- Heartbeat protocol: cron-based check-ins (read state, execute, write state, log)
- Cross-domain signal routing (future): signals from one agent domain route to another
Agent Household
SekaOS includes a multi-agent architecture with named agents, each with a C-suite role:
| Agent | Role | Domain |
|---|---|---|
| Njiaro | Chief of Staff | Routing, coordination, unified audit |
| Akili | CSO | Research, knowledge synthesis, strategic analysis |
| Mali | CFO | Investment, expenses, cash flow, wealth generation |
| Jenga | CTO | Technical infrastructure, repo health, system deployment |
Akili and Mali are identical twins. Named after halves of the Swahili proverb "Akili ni mali" (wisdom is wealth). The rivalry is generative, not destructive.
Njiaro is the elder figure -- threshold guardian who keeps the household coherent. All agents report to Njiaro for routing and to the human for decisions.
Design Principles
- Chat produces, Code executes -- clear separation of concerns
- Obsidian is the unified knowledge surface
- Raw sources are immutable; wiki is the living compilation
- One agent, many skills (no standalone agents)
- File-format-function mapping: JSONL for logs, YAML for config, MD for instructions
- Governance is not optional and not layer-specific
Upgrade Path
- Current (2 agents): Lightweight governance, cron heartbeats, sequential tasks
- Growth (4+ agents): Formal orchestration layer. Agents become "employees" within a company model
- Constraint: "Do not adopt orchestration frameworks until manual primitives have been tested and proven insufficient"
Related
- seka.works -- Layer 3 made visible
- Blacksky Algorithms -- first paid engagement through SekaOS infrastructure