Route 05 · start here

One screen, and a refusal you can watch.

No job title required. Here is a governed agent being given an instruction and refusing it, then the whole idea in four sentences. If something below turns out to be your problem specifically, the other four doors are at the bottom.

Demo
Recorded on the live demo environment, 2026-10-07. Real clicks: an authenticated request that policy still refuses, near the end of the clip. Live demo available on request.
01

The whole idea

Software now acts on people's behalf. An AI agent books, buys, files, replies and calls other software, sometimes software built by a different company entirely.

Nobody can prove afterwards what it was allowed to do. The record lives inside whoever ran the agent, in their logs, on their word. That is fine until the question is asked by someone who has no reason to take their word for it.

So every action carries its own proof. Who acted, and under what authority, signed into the action itself, checkable by anyone holding the signer's public key, offline, with no prior relationship and no service to call.

And the authority is enforced, not merely recorded. When a rule says no, the agent stops. You get the name of the rule that decided.

SYNTHERA is the trust layer for multi-agent systems: every agent gets a verifiable identity, scoped authority and a tamper-evident record, so software from different teams, vendors and frameworks can act on each other’s behalf without custom glue between every pair.

02

An agent being refused

The agent is woken for a walkthrough, not left running.

The panel below drives a governed agent through the production policy engine, and that agent is torn down between walkthroughs rather than kept up. When it is asleep the panel says so and offers to book a walkthrough, and it never reports that as a refusal. The recording underneath is the same path, captured while the stack was awake. No account, no key, nothing installed, and the rule that decides is named in the answer.

Fig · Live governance (production policy engine)
Ask the agent to do something

Every option below is evaluated for real, by the production policy engine, against a governed agent. You are not choosing a canned answer: the verdict comes back from the same path a provisioned agent takes.

Loading what the demo can evaluate…

What happened
Ready Pick something on the left.

    No account, no key, and nothing installed. Solara signs this request as the shared demo agent, because you hold no credential and were issued none, a dedicated agent with an identity of its own is what the paid tier is.

    One shared demo agent signs for everyone who visits, that is not an agent of yours, and nothing separates your request from anyone else's.

    03

    Where this is up to

    Early, and specific about it.

    The standardOpen, Apache-2.0, published on three package registries
    The productPre-pilot, live demo on request
    An accountOpen to anyone, takes a moment
    An agent of your ownGranted deliberately, not bought