harmonia

Files (3)

• SKILL.md
• interface-registry.md · references/
• specification.md · references/

SKILL.md (first lines)

# Harmonia

Harmonia is skill composition architecture — the systematic orchestration of multiple Abraxas skills into unified workflows. It solves the problem of skills operating in isolation without protocols for handoff, state transfer, or conflict detection.

Before you can compose skills effectively, you need:
- A composition schema defining the workflow
- State handoff protocols between skills
- Conflict detection for epistemic, behavioral, and resource conflicts
- Integration points with existing skills (Janus, Agon, Kairos, Krisis, Mnemosyne, Ethos)

Harmonia enables workflows like Kairos → Krisis → Agon to execute as a unified composition with proper state transfer and validation at each step.

---

## The Core Problem Harmonia Solves

Abraxas skills are designed to compose — Kairos feeds Krisis, Krisis feeds Agon, Ethos wraps any workflow — but no protocol exists for:

- **State transfer** — How does output from Skill A become input to Skill B?
- **Epistemic transitions** — How does Sol-mode content transition through Nox-aware processing?
- **Conflict detection** — What happens when two skills conflict?
- **Workflow definition** — How is a composition declared and executed?

Harmonia provides the composition layer that binds skills into executable workflows.

---

## When to Use Harmonia

**Use Harmonia when:**
- You need a multi-step workflow involving multiple skills
- You want to ensure clean handoff between skills (Kairos → Krisis)
- You're running a composition and need to check status
- You suspect conflicts between skills in a workflow

**Use direct skill invocation when:**
- Single-skill operation is sufficient
- No state transfer between skills is needed
- Quick, isolated task execution

---

## Context Envelope

The fundamental abstraction in Harmonia is the **context envelope** — a structured state object that travels between skills during composition:

```
envelope:
  id: env-{uuid}
  origin_skill: kairos
  origin_command: /kairos report
  epistemic_mode: sol  # sol | nox | mixed
  primary_output:
    artifact_id: kr-2026-03-12-abc123
    content: { ... }
  metadata:
    session_id: { ... }
    artifacts: [ ... ]
    warnings: [ ]
  handoff_history:
    - skill: kairos
      timestamp: 2026-03-12T10:00:00Z
```

Every skill in a composition receives an envelope and produces an updated envelope for the next skill.

---

## Interface Contract

Each skill declares its interface contract, which Harmonia uses to validate compositions:

```yaml
interface:
  inputs:
    - name: decision_frame
      type: object
      required: true
  outputs:
    - name: crisis_analysis
      type: object
  capabilities:
    - /krisis frame
    - /krisis frameworks
  constraints:
    - requires_sol_input
    - no_nox_processing
```

Known interface contracts:

| Skill | Inputs | Outputs | Constraints |
|-------|--------|---------|-------------|
| Janus | Any | Sol/Nox labeled | None |
| Agon | Sol only | Sol with test results | requires_sol_input |
| Kairos | None | Decision frame | None |
| Krisis | Decision frame | Ethical analysis | requires_sol_input |
| Mnemosyne | Any | Persisted | None |
| Ethos | Any | Voice-consistent output | None |

---

## The Four Commands

### `/harmonia compose` — Define a Composition

Create a named composition workflow with specified skills and handoff rules.

**Syntax:**
```
/harmonia compose {name} = {skill-a} → {skill-b} → {skill-c}
```

**Options:**
- `→` — Sequential handoff
- `∥` — Parallel execution (both receive same envelope)
- `? condition → {skill-x} | {skill-y}` — Conditional branching
- `⊳ [skills] ⊲ {aggregator}` — Fan-out/fan-in

From TylerGarlick/abraxas, MIT.

More from TylerGarlick/abraxas