Tool Interaction Design

Tool interaction ontologies, conductor session lifecycle, and AI agent coordination infrastructure

flagshipGRADUATEDACTIVE

what this is

The operational heart of ORGANVM's orchestration layer — a system that makes individual-to-enterprise amplification executable. Where `meta-organvm/VISION.md` declares that one person should be able to operate at institutional scale, the Conductor is **how** that actually works: routing 578 tools across 64 clusters so that a single practitioner can compose agent workflows, enforce governance, and ship across 8 organs without institutional headcount.

Concretely: a queryable taxonomy and routing system for 578 tools across Claude Code built-ins, MCP servers, macOS applications, Homebrew packages, and runtime ecosystems. The system maps tools into 64 clusters across 12 domains, defines data-flow routes between clusters, and provides a workflow DSL for composing multi-tool pipelines.

On top of this taxonomy sits the **Conductor OS** — an AI-conductor operating system that adds session lifecycle management, governance/WIP enforcement, workflow compilation and execution, observability, and a Patchbay command center.

architecture

```
ontology.yaml          ← Layer 1: Taxonomy (12 domains, 64 clusters, 578 tools)
    ↓ referenced by
routing-matrix.yaml    ← Layer 2: 32+ directed routes between clusters
    ↓ composed into
workflow-dsl.yaml      ← Layer 3: Pipeline DSL with 7 primitives
    ↓ validated/executed by
router.py              ← Layer 4a: Standalone CLI (8 commands, BFS pathfinding)
conductor/             ← Layer 4b: Full OS — sessions, governance, workflows, exports
mcp_server.py          ← Layer 4c: MCP server exposing conductor as live tools
```

Links

GitHub

Git Stats

Commits: 58
Velocity: 14.5/wk
First: 2026-03-03
Last: 2026-03-10