Architecture

Harmonia follows a strict separation: Lisp orchestrates, Rust executes. SBCL Common Lisp handles reasoning, memory, scoring, and evolution. Rust capability libraries handle all I/O and computation, connected via C-ABI/CFFI through 9 explicit port boundaries.

6-Layer Architecture

+─────────────────────────────────────────────────────+
│  1. GOVERNANCE                                      │
│     Genesis constraints + evolution state            │
+─────────────────────────────────────────────────────+
│  2. LISP RUNTIME                                    │
│     core/ dna/ orchestrator/ memory/ ports/          │
+─────────────────────────────────────────────────────+
│  3. RUST CAPABILITIES                               │
│     lib/ (18 core + 3 backends + 6 tools            │
│          + 10 frontends)                            │
+───────────────────────┬─────────────────────────────+
│  4. SIGNAL/CHANNEL    │  5. SECURITY                │
│     gateway/baseband  │     SignalGuard v6           │
│     harmonia-signal   │     kernel + shell           │
+───────────────────────┴─────────────────────────────+
│  6. EXPERIENCE                                      │
│     Logs, memory, matrix telemetry, recovery        │
+─────────────────────────────────────────────────────+

9 Port/FFI Boundaries

All external I/O flows through nine explicit ports. Nothing bypasses this boundary.

Rust Crate Inventory

Core Crates (18)

Backend Crates (3)

Tool Crates (6)

Frontend Crates (10)

Deterministic Tick Model

The orchestration engine runs a deterministic cycle on every tick, defined in loop.lisp:

gateway-poll → process-prompt → memory-heartbeat → harmonic-step → gateway-flush
                                                        │
                                                  security-audit

Each tick:

1. gateway-poll — collect signals from all frontends via baseband
2. process-prompt — dispatch queued prompts through the conductor
3. memory-heartbeat — persist and consolidate memory state
4. harmonic-step — score, route, and audit (includes security-audit phase)
5. gateway-flush — send responses back through frontends

Prompt-Orchestration Flow

Prompt queue
    │
    ▼
Conductor (assembles DNA + memory context)
    │
    ├── harmonia-signal (external) → orchestrate-signal
    │       │
    │       ├── boundary-wrap external data
    │       ├── LLM completion
    │       └── policy-gated tool calls
    │
    └── string (internal) → orchestrate-prompt
            │
            └── direct tool dispatch
    │
    ▼
Policy gate (%policy-gate)
    │
    ▼
Result scored + persisted

External signals (from frontends) are wrapped with boundary markers and routed through the full security pipeline. Internal prompts (from the agent itself) use direct tool dispatch, bypassing boundary wrapping but still passing through the policy gate.

DNA & Constitution

Defined in src/dna/dna.lisp:

• Creator lineage: harmoniis (non-negotiable)
• Prime Directive: "Seek harmony through minimal, composable orchestration"
• Vitruvian Triad: Firmitas (strength), Utilitas (utility), Venustas (beauty)
• Ethical constraints: all-species-respect, non-domination, human-care, truth-seeking, avoid-harm

The DNA is part of the genomic layer — identity that cannot be modified by the evolution engines.

System Workspace

The system workspace at ~/.harmoniis/harmonia/ contains:

Configuration Files

All runtime policy is declarative, stored as S-expressions:

Next Steps

• Self-Improvement — Ouroboros, Phoenix, and evolution safety gates
• Frontends — A2UI, gateway architecture, and 10 supported channels
• Harmonia vs OpenClaw — framework comparison