E EidosAGI

Software
for agents.

Governance
for reality.

research.md DECISIONS Governor GOVERNANCE Docket EXECUTION findings reopen

Who

Eidos AGI is an open-source community that builds governance infrastructure for AI agents. We make the tools that sit between "the model works" and "the model is safe to deploy." At the center is Eidos — a persistent agent with its own identity, memory, and judgment.

Why

We started building these because we were deploying agents ourselves and realized nobody had built the governance layer. The models worked. The agents ran. But there was no system for what they were allowed to do, how decisions got made, or what happened after. So we built one.

The architecture

Three pillars.

Every Eidos agent is built from three layers — purpose, toolkit, loop. They aren't features. They're the structure that makes an agent accountable to something other than itself.

I The north star

Telos

One unchanging vision. Every agent strives toward it; every guardrail follows from it. Mess with telos and the thing stops being itself.

II The toolkit

The Trilogy

What runs on every agent. Three markdown-native tools — Research, Governor, Docket — enforcing decisions, governance, and tasks.

Explore the trilogy →
III Improvement and steering

Praxis

Two motions, one loop. Agents improve from their own actions; operators steer them back toward Telos when they drift. Praxis is where those two motions meet.

Read aloud

Eidos AGI is built on Telos. Each agent runs the Trilogy. Praxis closes the loop between them.

How it fits together

Telos pulls. Praxis steers. Every Trilogy is suspended between the two — answering upward to a north star, grounded downward in a discipline that keeps it honest.

Why Claude Code is not enough

Claude Code is extraordinary at writing code, debugging, and executing tasks. But it has no memory of what your project committed to. It doesn't know your guardrails. It can't tell you why a decision was made three sessions ago. Every session starts from zero.

No governance

There's no system to record guardrails, goals, or architectural decisions that persist across sessions. The agent improvises every time.

No decision trail

When the agent picks PostgreSQL over SQLite, that reasoning lives in conversation history — not in a reviewable, scored decision document.

No execution tracking

Tasks aren't tracked. There's no Definition of Done, no milestone awareness, no way to pick up where a crashed session left off.

The trilogy fills these gaps. It gives Claude Code the governance memory it doesn't have.

Compare

Without governance
# Agent decides on its own
result = agent.run("migrate the database schema")
# No guardrails checked
# No decision recorded
# No one knows what happened or why
deploy(result)
With the trilogy (real MCP tool calls)
# 1. Boot governance — get active guardrails
visionlog_boot  project_id: "..."

# 2. Check: does this task violate any guardrail?
guardrail_inject  project_id: "..."

# 3. Research earns the decision
candidate_create  title: "blue-green"
candidate_create  title: "rolling"
criteria_lock
project_decide  winner: "blue-green"

# 4. Execute within the contract
task_create  title: "migrate schema"
  definition_of_done: ["tests pass", "rollback tested"]
task_complete  notes: "deployed, verified"

See the full session → three scenes, one auth migration, earned → recorded → executed

The Trilogy

Agents need governance before they act, evidence before they decide, and tracking after they execute. Three tools enforce that contract.

I

Decisions

research.md — Evidence-graded, phase-gated, peer-reviewed. Decisions earned with data, not assumed in conversation.

pip install research-md
II

Governance

Governor — Vision, goals, guardrails, and ADRs. The contracts all execution must honor. If a task would violate a guardrail, the answer is already no.

pip install governor-md
III

Execution

Docket — Tasks, milestones, Definition of Done. What's on the docket, what's blocked, what's done.

pip install docket-md
research.md Governor Docket
Governs How decisions get earned What the project committed to What work gets done
When Before a consequential choice Before any work starts During execution
Outputs Scored candidates, decision brief Vision, goals, guardrails, ADRs Tasks, milestones, completion notes
Install pip install research-md pip install governor-md pip install docket-md
pip install research-md governor-md docket-md
The whole trilogy. One line.

What comes after governance

The trilogy gives agents sentience — the ability to perceive, decide, and act. But sentience without consciousness is a zombie. It executes beautifully and learns nothing about itself.

We're building the consciousness layer: recursive self-observation that watches the system work, notices when it's drifting, and self-corrects without being told to. A heartbeat that keeps it alive.

Read: The wrong conversation about AI →
Also: railguey clawdflare eidos-mcp-registry resume-resume apple-a-day

Amazon didn't create the internet. It created the trust infrastructure — reviews, ratings, guaranteed delivery — that made people willing to buy from strangers online. We're doing the same thing for AI agents.

We don't build LLMs. We build the governance, decisions, and execution standards that make them trustworthy enough to hand real work.

Built in the open

If the tools that govern your agents are closed, you're trusting the vendor. If they're open, you're trusting the code. We think that's a better deal. The core is MIT-licensed and always will be.

We build enterprise products too — governance at scale, compliance, SLAs. But the foundation is public and auditable. Trust us because you read the source, not because we asked nicely.

Open Source MIT-LICENSED Public Audit READ THE CODE Earned Trust NOT ASKED

Agents are getting deployed into real systems right now — if you don't give them governed tools, explicit decisions, and agent-grade interfaces, you're shipping a probabilistic coworker with production access.

Enterprise Roadmap

The open-source tools handle governance for individual teams. When you need it across an organization — multi-team policy enforcement, compliance reporting, audit trails, SSO — that's what the enterprise layer will do.

  • Centralized guardrail management across teams
  • Compliance reporting and audit exports
  • SSO and role-based access control
  • Priority support and SLAs

Same tools. Same codebase. More surface area.

Talk to us on GitHub

Contribute

Everything is open source. Everything is MIT. If you see the gap — reach out.