Legba Sign in
Philosophy

AI as Labor.
Engineering as a System.

Not a chatbot that writes code. A system that organizes intelligence into productive labor.

  1. I. AI as labor
  2. II. Neurosymbolic governance
  3. III. Human authority
  4. IV. The orchestration layer
  5. V. The future of software engineering
I

AI is not a tool you talk to. It is labor you organize.

Most AI coding tools still behave as individual assistants: they execute instructions, produce outputs, and depend on a human to coordinate everything around them. That model stops scaling the moment you have more than one agent.

Legba starts from a different premise. Agents are specialized workers operating inside a shared engineering system. Like any workforce, they need objectives, assignments, environments, review and memory. The interesting problem is no longer whether an agent can write the code. It is how the work gets organized.

The bottleneck is no longer code generation. It is orchestration.
II

Neurosymbolic governance: probabilistic intelligence inside deterministic control.

Language models are probabilistic. They are creative, adaptive and occasionally wrong. Software systems are deterministic. They follow rules, enforce states and behave the same way every time. Legba puts the first inside the second: the neural part does the work, the symbolic part decides what counts as done.

NEURAL · PROBABILISTIC
The agents
  • Interpret objectives and context
  • Write, refactor and test code
  • Diagnose infrastructure
  • Propose solutions and produce evidence
SYMBOLIC · DETERMINISTIC
The system
  • Task states and dependencies
  • Execution policies, permissions, approvals
  • Lane routing and isolated environments
  • Verification against explicit outcomes

Autonomy is not the absence of governance.

III

Autonomy without losing control.

Legba is designed around a clear division of responsibility. The point is not to remove humans from the loop. It is to put human attention exactly where judgment matters most, and nowhere it is wasted.

AGENTS
Execute
Perform work, propose solutions, generate evidence.
THE SYSTEM
Verifies
Manages policies, dependencies, task states and verification procedures.
HUMANS
Govern
Set objectives, approve important decisions, resolve escalations, retain authority.
IV

The orchestration layer is the product.

Legba is not built on the assumption that any single AI model or coding agent will stay dominant. Models will improve. Coding harnesses will evolve. New tools will appear.

Legba operates above these components. Its value lies in the system that connects planning, specialized labor, isolated execution, evaluation and persistent knowledge. That makes it possible to improve or replace individual agents without rebuilding the entire engineering workflow.

models · harnesses · toolschange
plan · route · isolate · verify · rememberpersists
Better models make agents more capable. Better orchestration makes the entire workforce more effective.
V

Toward autonomous software production.

The next evolution of software engineering is not simply faster code generation. It is the emergence of systems capable of organizing and performing substantial engineering work with progressively less direct human intervention.

In this model, engineers increasingly become architects, supervisors and decision-makers. They define intent, establish constraints, evaluate outcomes, and guide the evolution of software systems.

THE ENGINEER, BEFORE
Writes the code, coordinates every session, rebuilds context by hand.
THE ENGINEER, WITH LEGBA
Defines intent, sets constraints, evaluates outcomes, decides.

Legba is an exploration of that future: an engineering operating system where human judgment, machine intelligence, and deterministic execution work together.

Not a chatbot that writes code.

A system that organizes intelligence into productive labor.

Request a demo See how it works →