Skip to content
Request Demo

See EDDI work, no setup needed

Follow one business decision from question to audit trail: a board of AI agents deliberates, a human approves, and every step is recorded. About two minutes, nothing to install.

  1. 1The question on the table
  2. 2The board deliberates
  3. 3A human decides in Slack
  4. 4Everything lands in the audit ledger
  5. 5Now try it on your own case
Step 1

The question on the table

A leadership team has to decide whether to commit to a new supplier for three years. Instead of one answer from one model, three specialist agents look at it, each from its own angle.

Illustrative example

The questionShould we sign a 3-year contract with a new logistics supplier?

  • FinanceChecks price and volume
  • RiskLooks for what can go wrong
Step 2

The board deliberates

Pick a style below. It is the same question and the same three agents, but a different way of reasoning together. Watch what each style does differently.

Illustrative example

The questionShould we sign a 3-year contract with a new logistics supplier?

  • FinanceChecks price and volume
  • RiskLooks for what can go wrong

Choose how the board reasons

What is differentEveryone answers independently and at the same time. A moderator then merges the answers into one recommendation.

Phases
  1. Finance

    The rates are 8% below our current carrier, but only if we meet a volume floor. At last year’s volume we stay above it, with a thin margin.

  2. Risk

    This supplier would carry most of our freight. One failure at their main hub could stop our shipments for days.

  3. Moderator

    Sign only with changes: an exit right after repeated late deliveries, a lower volume floor, and a backup carrier for at least 20% of volume.

Result

Sign, but only with three changes

Recorded dissent: Finance would accept a backup carrier for 15% of volume instead of 20%.

A mock conversation to show how each style works. Real boards use your own agents, data and rules.

Step 3

A human decides in Slack

The board only recommends. The group pauses before it concludes, and a named approver receives a card in Slack. Try the buttons.

Illustrative example
EDDIPosted in a Slack channel (example)

Approval needed: Group phase Synthesis

Question
Should we sign a 3-year contract with a new logistics supplier?
Recommendation
Sign, but only with three changes

Only approvers on the allow-list can decide. Every decision is written to the audit ledger.

  • Only people on the approver allow-list can decide. Without the list, the buttons are not shown.
  • Approve or reject: the decision is attributed to the person who made it.
  • The same approval is also available in the EDDI Manager, through the API and through MCP.
Step 4

Everything lands in the audit ledger

Each step of the run writes a signed entry: what the agent was asked, what it answered, and who approved. Entries are HMAC-signed, append-only and sequence-checked, so a gap or an edit shows up.

Example entries
  1. Finance agent gives its opinionSignature verified
    Sequence
    1
    Time
    2026-03-12 09:14:07 UTC
    Agent
    finance-advisor
    Task
    LLM task (opinion)
    Signature
    HMAC v4:9f2c41ab…e81a Ed25519 · a41f…09c2
  2. Moderator writes the synthesisSignature verified
    Sequence
    2
    Time
    2026-03-12 09:14:41 UTC
    Agent
    board-moderator
    Task
    LLM task (synthesis)
    Signature
    HMAC v4:3b07d5c9…14f2 Ed25519 · 7be0…3d58
  3. Approver decides in SlackSignature verified
    Sequence
    3
    Time
    2026-03-12 09:19:03 UTC
    Agent
    board-moderator
    Task
    hitl.approval
    Decided by
    slack:U0EXAMPLE
    Signature
    HMAC v4:c81e6a20…4d03 Ed25519 · 52d9…b6e1

An integrity check over the whole conversation reports INTACT, BROKEN or INCOMPLETE.

Step 5

Now try it on your own case

The example above is a mock. We can build the same flow on your documents, your systems and your approval rules.

For technical evaluators

Prefer to click around the real thing? Open the raw EDDI sandbox and explore the Manager yourself.

Open the sandbox ↗

Demo system for exploration only. Data is wiped every 48h at 03:00 UTC.