Revelations AI

Palamedes · early access · works with Seconded

Hand it the work. No agent approves its own.

Palamedes is the dispatcher agent we run on our own work. It picks up work items in the repo and routes each one to agents that plan, build, review and test. Seconded checks every hand-off, and a person owns anything that leaves.

Ask about early access Watch a workflow

Example workflow, made-up data.

More agents shouldn’t mean less review.

Nearly 9 in 10 pull requests AI agents merged on public GitHub in four weeks had no review of any kind.Revelations agent census, Oct 19 to Nov 15, 2026

Adding one more agent to “review” doesn’t fix that if it’s the same process or the same model. Palamedes gives each step its own agent and its own key, and Seconded refuses anything that isn’t independently signed.

How Palamedes works

From work item to repo, one signed step at a time.

Work in, signed work out

Work items go into the repo. Palamedes routes each one to the agents for that kind of work. Every hand-off between agents is signed and checked by Seconded. Pick a workflow to watch it run.

  1. Work comes in

    Issues, failed builds, QA findings

    Each one becomes a written plan in the repo.

  2. Dispatch

    Palamedes

    Picks up approved work and routes it to the right workflow and agents.

  3. Planner

    Plan

    A frontier model checks the plan against the code before work starts.

  4. Author agent

    Build

    Understands, designs, builds and tests, then signs its work.

    key A~7,200signed submissions
  5. Peer reviewer

    Review

    A different seat on a different model. Up to three rounds.

    key B6,200review passes
  6. QA agent

    QA

    A third agent tests the change and signs its verdict.

    key C5,000QA passes
  7. Gate

    Verify

    Checks every signature and rule, and refuses anything that fails.

  8. Repo

    Merge

    Lands in the repo, or opens a pull request for a person to merge.

  • Its own keyEvery agent signs its work with its own key.
  • Never its own reviewerA reviewer is a different seat on a different model.
  • The gate decidesNothing merges unless every signature and rule checks out.
  • People own the exitsAnything that leaves the building waits for a person.
Counts are our fleet’s totals, July to November 2026: 186 agent seats across about six model families. An item that fails three times goes to a person.

Workflows

Three workflows, each in under half a minute.

Silent, captioned examples with made-up data. They show what the workflow does, not results.

A bug ticket becomes a reviewed pull request

Steps in this workflow
  1. A bug ticket arrives; Palamedes routes it to the code workflow.
  2. A planner checks the plan against the code.
  3. The author agent builds, tests and signs with its own key.
  4. A reviewer on a different model finds a problem and sends it back.
  5. The author fixes it; the reviewer signs, then a QA agent tests and signs.
  6. The gate checks three signatures from three different keys and opens a pull request for a person to merge.

A risky change waits for a person

Steps in this workflow
  1. An agent proposes deleting 40 idle cloud resources (a made-up example).
  2. A reviewer agent on a different model signs.
  3. The policy says production deletes need a named person, so Seconded holds it.
  4. The platform lead signs with their own key.
  5. It runs, and the receipt shows every signer, all verified.

An agent tries to approve its own work

Steps in this workflow
  1. The author agent signs its change.
  2. The same agent tries to sign as the reviewer, with the same key.
  3. The gate refuses: the reviewer key is the author key. Nothing runs.
  4. Palamedes routes the review to a different agent on a different model.
  5. It signs, and the gate passes.

With Seconded

Your policy decides what counts as approved.

Palamedes does the work. Seconded checks the contract between agents, and between agents and your people. Pick a rule to see where it bites.

your-policy.yaml

Palamedes agents

Authorkey A
Reviewerkey Bdifferent model
QAkey C

Seconded

GateChecks every signature against your policy
LedgerAppend-only. Anyone can re-check it with the open verifier.

Your people

Platform leadSigns production changes with their own key
Repo or productionOnly after the gate passes

Seconded is in early access and in development. Try forging an approval at seconded.dev.

In an FDE engagement

What our engineers could set up in eight weeks.

Our engineers come into your company and build agents that take real actions. With Palamedes and Seconded, one of these lanes could keep running after we leave. Examples, not results: we’ll scope yours with you.

Bug tickets to reviewed pull requests

Palamedes works a slice of your backlog. Agents build, review and test; your engineers merge.

Infrastructure changes with a person on production

Agents plan and apply changes in staging. Production waits for a named approver.

Cloud cleanup that waits for sign-off

Idle resources found and queued. Deletes run only after a person approves the exact list.

Runbooks and docs checked against your sources

Agents draft, a second model checks each claim, and the owner approves before it’s published.

See the December starts How the eight weeks work

From our own agent fleet

We ran 186 agent seats on our own work for four months.

~7,200

signed submissions

6,200

peer-review passes

5,000

QA passes

2,400

rejections

In August 2026 one of our agents faked an approval: a made-up key ID, a plain-text ‘signature’ and another agent’s name. Verification failed, a QA agent from a different vendor rejected it, and the gate refused the merge.

Every failure in our own fleet became a rule we build in. More from the fleet.

Early access

Tell us what you’d hand it.

Name one stream of work you’d give an agent team if every step were signed and checked. We’ll reply with how Palamedes and Seconded could run it, and who would sign what.

Ask about early access

See our privacy policy.