The cosmic harness for agentic engineering

Govern your agents,not their creativity.

In Greek myth, Ananke is Necessity: the primordial force that encircles the cosmos and keeps it in order while it expands. Ananke Plexus does the same for AI coding agents, giving them architectural context, deterministic guardrails, security gates and verifiable evidence. They stay free to create, and they stay in orbit. Local-first and open source.

Get started →GitHub

$ pip install ananke-plexus

PyPIv0.3.45

Specify
Build
Verify
Evolve

23Docs pages

6Agent backends

7Registry importers

970Dex Trove skills & agents

The harness, not the cage

Ἀνάγκη · Necessity

In the Orphic stories, Ananke coils around the cosmos with Chronos; in Plato's Myth of Er, the heavens turn on her spindle.

She doesn't build the stars. She keeps them in order while the universe expands and expresses itself. Ananke Plexus takes the same role for AI agents. It doesn't write the code. It sets the few things that must always hold, such as the spec, the architecture contract, the policy and the evidence, and leaves everything else to the agent.

Why Ananke Plexus →

Necessity at the core

A small, non-negotiable centre: specs, CALM architecture contracts, policy gates, secret scanning and signed evidence. Every run passes through it.

Freedom at the edge

Agents choose their own path through the code, using whichever backend, skills and tools fit the task. Ananke checks the outcome, not each step.

Orbits, not cages

Guidance comes as context: the code graph, the spec and the constitution. When an agent drifts, it gets a clear signal back rather than a hard stop.