42 Quantum
In development

AI Orchestration Engine

Project name: The Conductor

01The research goal

The research goal: can a piece of work be split across many AI models, local and cloud, without the context dying every time the work moves between them? Losing context on a model swap is the failure that makes most multi model setups unusable, and this project exists to solve it.

It is internal infrastructure. It is not a product and it is not sold separately. It exists because building the rest of the lab's projects at this pace is not possible by hand, and everything learned here feeds the production suite.

02How it works

Work is dispatched across three role slots rather than thrown at one general model. An Architect plans, reviews, and verifies meaning. An Implementer makes the bulk code changes and runs the tools. An Adaptive role scans, lints, and classifies, and is deliberately read only so it can never make broad changes on its own. Each role maps to the class of model that is good at it, which is also what keeps the cost down.

A shared context store keeps the thread intact when a task moves between models. A code knowledge graph built on Neo4j and Tree-sitter gives the roles structural understanding of a repository instead of whatever fits in a prompt window. Local models run through Ollama, so the free tier costs nothing to operate.

It runs as a local first system: a Python backend, a React frontend, and a native desktop shell, all on the user's own machine.

What the lab built

  • Four-role dispatch model routing each task to the right class of model
  • Shared context store so context survives a model swap mid-task
  • Code knowledge graph built on Neo4j and Tree-sitter for repo-aware reasoning
  • Local-model execution through Ollama, so the free tier costs nothing to run
Lines of code
679,999Lines of code
Commits
1,154Commits
Files
2,336Files
Building since
Mar 2026Building since
  • Python
  • TypeScript
  • Neo4j
  • Tree-sitter
  • Redis
  • Ollama

At a glance

How the system flows

  1. 01

    Task in

    A piece of work arrives with its context

  2. 02

    Architect

    Plans, reviews, verifies meaning

  3. 03

    Implementer

    Makes the changes, runs the tools

  4. 04

    Adaptive

    Scans and classifies, read only

  5. 05

    Context out

    The thread survives every model swap