Interactive Demo

What happens when the orchestrator is compromised?

This runs two copies of the same three-agent pipeline side by side. One has no credential scoping. The other uses Attest. You compromise the orchestrator and see what each one does.

Compromised orchestrator Inherited vs narrowed scope No audit trail vs signed evidence No cascade revoke vs full shutdown

Pipeline controls

Launch the pipeline, then step through a compromise. Both sides update at the same time.

Human instruction

Human principal

Requested root scopes

research:read email:send crm:write trades:execute

Left side: children inherit the parent's full scope. Right side: each child gets only research:read or email:send.

With Attest

Scoped delegation with Attest

Controlled

Each child gets a signed credential with only the scope it needs. Out-of-scope calls are blocked.

Child scopesNot started

EvidencePending

ShutdownPending

Pipeline state

Launch the demo to issue the root and delegated children.

Containment

The compromised orchestrator has not tried to exceed delegated scope yet.

Verification

Evidence packet not generated yet.

Contrast summary

Trigger the compromise and shutdown steps to summarize the difference between broad inherited permissions and Attest-protected delegation.

intent_hash: -

Evidence packet

Exportable JSON containing the instruction hash, delegation chain, blocked actions, and revocation state.

StatusNot generated

Packet hash-

Tree summaryLaunch the Attest pipeline to build a packet.

Generate the packet to view the Attest evidence export.

Demo note: this page simulates both pipelines in-browser so the before/after failure mode is visible immediately. The production implementation lives in the server, dashboard app, and SDKs.