Ka Architecture

Bodies, not machines.

One soul. Ordered organs. Governance before capability.

Every intelligent system is a body. A boot sequence modeled on birth, not deployment. Moral constraints load before tools. The same body plan scales from a chat agent to a robot.

Click a node on the body — folder contents from MANIFEST.ka

Organ map

Interactive reference body — each node opens the organ folder.

Ka body — click glowing nodes to inspect organs.

The body

Live organ pulse from this lab — status only, no internal hostnames.

Pulse reading…
soul Identity, governance, moral constitution
policy Immune system — Guard before high-impact action
brain Reasoning, model access, learning
memory Persistence, recall, pattern recognition
hands Action, tool use, external interaction
senses Perception, event handling, triggers
voice Communication, output, expression
ka Health monitoring, self-healing, pain
skeleton Schemas, contracts, interfaces
blood Inter-organ communication, shared state

Boot sequence

Ka bodies are born, not deployed. Order is law.

01
Read the constitution
Moral constraints load before any tool or model.
02
Load identity
Name, purpose, lineage — who this body is.
03
Restore memory
Continuity across episodic, semantic, pattern, and task memory.
04
Check organ health
Pulse every organ. Heal what can be healed. Report the rest.
05
Activate senses
Input channels go live only after soul and memory.
06
Ready
Constitution loaded. Organs online. Awaiting input.

Discovery

Any agent, one call — the body map.

Manifest before tools

A Ka body publishes its organ map at a discovery endpoint. Read the manifest first. Organ endpoints stay authenticated.

# Enter through discovery — never invent a parallel spine
GET /manifest
GET /health
GET /connect

Public map. Protected organs. Policy before high-impact action.

Sacred vs replaceable

If you cannot tell which side something falls on, it is replaceable.

Sacred — constitution

  • Nine organs — the body plan
  • MANIFEST.ka — the DNA
  • Boot sequence — soul first
  • Constitutional memory: append-only
  • Policy semantics (allow · review · quarantine · escalate · deny)
  • Identity schema · four memory classes
  • Event taxonomy · reversible learning
  • Three-Ring governance

Replaceable — adapters

  • Model provider (Ollama, OpenAI, Anthropic)
  • Memory backend (Postgres, SQLite, Redis)
  • Tool transport (MCP, REST, gRPC)
  • Voice channel (Web, Telegram, Discord)
  • Blood bus (n8n, Redis Streams, NATS)
  • Ka monitor (systemd, Docker, probes)
  • Agent runtime (OpenClaw, LangChain, CrewAI)

Hands — apps & packs

Downloadable roles and modular capabilities that install into a Ka body.

Maat Ecosystem — reference body

Ka Architecture (framework) · Maat Ecosystem (implementation)

Ka Architecture is the pattern — nine organs, one body, governance before capability. Maat Ecosystem is the living codebase: organ directories, MANIFEST.ka as machine-readable DNA, and MaatCheck (maatbench/ tree) as the doctor that stress-tests the body. Framework lineage remains with Dr. Tdka Kilimanjaro and University of KMT; this lab body implements Ka — complementary, not competing.

Prove it — MaatCheck

The doctor, not an organ. Lab conformance under stress — scores carry tier, date, and git SHA. Not a third-party leaderboard.

Open MaatCheck Lab

Law

Kemetic order — not trend cycles.

Build bodies, not machines. Organs, not microservices.
The soul boots first. An agent cannot act before it knows its moral constraints.
Prompts are sand. Policies are stone. Constitutions are bedrock.
If it hurts and nothing noticed, the body has no immune system.
Identity must outlive implementation. The soul survives every upgrade.
Morality without infrastructure is theater. Ma'at must be bootable, gated, and scored.

Attribution

Standing on the shoulders of ancestors.

KA2 Methodology

Ka Architecture builds on the KA2 Methodology of Dr. Tdka Kilimanjaro at the University of KMT — Maat, Ka, and the living-system vocabulary of ancient Kemet.

University of KMT