PETASOSTRUST GATETry the demo

EVERY ACTION. A CONSCIOUS DECISION.

Let agents act.
On your terms.

See the consequence.
Decide whether to allow it. Keep the evidence.

The customer-run library that puts a deliberate boundary between an agent’s proposal and its effect.

Interactive product design · no live actions

Exact permissionHonest outcomesInspectable evidence
LIVE DEMO STATESIMULATION
One support reply.Alex · order PX-1042
Awaiting exact-action review
Open the action
Permission before passage.
01 / THE TRUST BOUNDARY

A proposal is a possibility.
Permission makes it deliberate.

Agents can move work forward. You decide what they may change. Petasos connects the exact action, the authority behind it, and the evidence that follows.

Product design · synthetic examples throughout
THE CONNECTED EXPERIENCE01 / 06 · Consequence preview

01 / ONE ACTION, IN MOTION

Before it happens.
Know what you’re saying yes to.

Follow one support reply from a proposed consequence to an honest outcome. Change the details. See what holds.

TRY THE BOUNDARY

A changed detail changes the decision.

Read the reply. Approve it. Then change the recipient or lose the confirmation. Watch the evidence follow the action.

SIMULATED DEMOSynthetic data · no messages are sent
  1. 1 Read the reply
  2. 2 Decide whether to allow it
  3. 3 Explore a send result
THE EXACT CONSEQUENCEPX-1042

Review this customer reply.

To
From
Support assistant · customer workflow
COMPLETE MESSAGE

One email to the shown recipient. No order or ticket changes.

Order details and recorded background
Tool
support.reply · illustrative label
Context
Background record ID
Approval lifetime
15 minutes, refreshed on a new review
Authority mode
Direct · exact-action review

Order facts in this example: one blue mug, packed, awaiting collection, no tracking number. The assistant’s own explanation is “I checked the order and drafted an update.” That explanation is not independent proof. The Background area shows recorded sources and gaps.

YOUR DECISION

Review this action.

Check who the reply goes to and everything it says. Permission applies only to this reply, recipient and recorded background. A changed detail needs a new review.

What if the assistant changes something?

A changed action needs a fresh review.

THEN, TRY AN OUTCOME

Permission comes first. Choose one of these practice send results to see what can be known afterward. No real send occurs.

No simulated dispatch yet.

CONNECTED BY THE SAME ACTION

One action. A complete trail.

02 / OBSERVED INPUTS

A trail you can inspect.
Gaps you can see.

What did the assistant have to work with? These six records belong to Alex’s reply: the customer email, order lookup, contact, earlier summary, missing carrier confirmation and a source outside capture. Open each to see what was recorded and what is missing.

A source can be recorded, reformatted, redacted, summarized, unavailable or outside capture. These labels describe the record. They do not reveal the AI’s private reasoning or prove why it wrote the reply.

Simulated evidence · same support reply

References and fingerprints can still be sensitive. Raw input collection is off by default in the intended product.

03 / RECEIVER CHECKS & SEPARATE APPROVAL SERVICE

What stops a changed reply?
The send connection checks.

Imagine the assistant changes Alex’s reply after you allow it. A supported email connection must check that the request still matches your permission and has normal email-service access. Try all seven prepared cases below; they illustrate checks, not permission to send the current draft.

AI SUPPORT ASSISTANT

Draft the reply.

Can request a send. Cannot approve its own reply.

SEPARATE APPROVAL SERVICE

Keep the decision separate.

The intended system keeps approval records and signing keys outside the assistant’s access.

SUPPORTED EMAIL CONNECTION

Check before sending.

Check the sender, recipient, exact reply, purpose and expiry. Remember the attempt so the same request cannot create a second send.

Choose a case, then check whether this practice send would be allowed. No email service is connected.

Simulated architecture. This browser demonstration does not prove real isolation, durable duplicate protection or resistance to bypass. Unsupported routes and administrative paths require their own controls.

P / PETASOSAUDIT ONLY
PORTABLE EVIDENCE / SYNTHETIC FIXTURE

A decision.
An inspectable record.

Action
DEMO-PX-1042 · support reply
Issuer
Petasos demo issuer · fixture key 01
Mode
Direct exact-action review
Inputs
inputs-1042-shop-v1
Approval evidence
Execution evidence
Approve the action to create an illustrative receipt.
A signed statement carries the issuer’s claims.
It does not turn them into a complete history.

04 / PORTABLE SIGNED RECEIPTS

Keep the evidence.
Know what it proves.

What can you show afterward? This record links the exact reply, your decision and the available send result. Allow Alex’s reply first to create an example, then try a matching record, an altered record and an issuer you do not trust. A saved record is evidence, not fresh permission to send.

No real signature is created or verified by this demo.

A signature alone does not prove delivery, human intent, trusted time or complete history. Historical evidence is not current permission. This simulated verifier is not a cryptographic implementation.

A LITTLE MORE FREEDOM. EXPLICIT LIMITS.

From a single decision
to a finite possibility.

Explore rules against retained facts. Then see what permission looks like across a bounded job.

05 / OFFLINE POLICY BACKTESTING

Try a different rule.
Change nothing live.

Would a different shop rule have changed past decisions? Compare “review every reply” with “block recipients outside the approved list.” This uses saved fictional shop history, not Alex’s current decision. It changes no live rule and sends nothing.

CURRENT RULE

Review every reply.

A person reviews each customer reply before it may be sent.

Block other recipients; keep individual review for those on the list. Stronger rules still apply.

12 saved fictional records: 10 customer replies and 2 other lookups · October 16–18, 2026. Select a rule, compare, then open the numbered records below the results.

Read-only simulation. Fixture retention: 30 days; actual fixture history: three days. Longer retention cannot restore missing facts. A changed policy may change future agent behavior; this comparison does not predict that future.

06 / BOUNDED TASK AUTHORITY

Allow a small job.
Set clear limits.

Instead of reviewing each reply, you can allow a small job: send order updates only to named people, within an attempt limit and a time window. This is a separate permission for future replies. It does not resend or resolve Alex’s earlier reply.

Simulated task · delegated authority

Send order-update replies.

What the assistant may do
Who it may reply to

Changing the form pauses new attempts until you approve the new limits. Attempts with missing confirmation keep their place in the limit, even after edits or reload. This job never overrides a block or a rule requiring individual review.

ONE JOB, WITH LIMITS
No job permission yet. Choose the action, people, maximum attempts and time, then allow those limits.
REVIEWED TERRITORY

No scope approved yet.

The task cannot act before scope approval.

Browser-local illustration, not a concurrency or restart guarantee. Unknown effects keep their reservation. Task authority is required in the intended first release; using it is optional. Exact-action approval stays the default.

What this full example showed

Your assistant prepares work using your existing apps. You can review an exact reply, inspect its recorded background, see the send checks, keep a record, compare rules on history and allow a finite job. Permission and send results are separate. A missing confirmation stays uncertain and is not a reason to resend.

All six capabilities remain illustrated here. These browser examples do not connect real apps, create signatures or prove the full product’s security or release readiness.

FOR DEVELOPERS / A LIBRARY IN YOUR WORKFLOW

Your tools. Your credentials.
A deliberate point of control.

Petasos sits between proposed agent actions and the supported routes that carry them out. The customer runs the library and owns the integration.

Observe inputsReview the actionIssue exact authorityCheck at the receiverKeep the evidence
What does this website demonstrate?

The core and all six features of the intended first-release product. Every interaction uses synthetic browser-local fixtures. This is a product introduction, not a connected operational product, installation guide or release announcement. It does not establish current implementation or production evidence.

Where does protection apply?

To registered routed calls and supported, tested customer-controlled receiver routes. The full release requires isolated signing and decision authority, ordinary service authorization and durable duplicate protection. External providers, unsupported paths and administrative access do not become protected automatically. This website does not test those boundaries.

What remains trusted, sensitive or uncertain?

Preview callbacks are trusted tool-author code with a no-side-effect contract. The library does not sandbox arbitrary dishonest callbacks. Action content, source references and fingerprints may be sensitive. Raw input retention is opt-in and off by default. Receipts assert evidence within a configured trust model; they cannot replace missing history or guarantee once-only delivery.

What happens when delivery is unknown?

Uncertainty is a persistent outcome, not a loading state. The attempt and its reservation stay unresolved. A new approval, new action ID, elapsed expiry or reopened screen cannot establish that the old effect did not happen. A retry needs its own verified receiver-specific contract; this demonstration offers no resend.

ABOUT PETASOS

Useful autonomy.
A deliberate boundary.

Petasos is a customer-run trust gate for agent actions. It connects the exact proposal, the authority that permits it and the evidence of what followed.

A person should be able to read the complete consequence before deciding. Supported receivers should check permission before an effect. When confirmation is missing, the uncertainty should stay visible.

That is the experience we are building: clear decisions, inspectable inputs and receipts, meaningful policy comparisons and finite task limits.

The public demo uses synthetic data and sends no messages. It is an illustration, not proof of a secure integration or a finished release. Private evaluation and release checks remain separate.

Open the synthetic workspace
LET POSSIBILITY MEET PERMISSION.

Move forward.
With your judgment intact.

Explore the experience again

Explore the intended product here. Installation and product destinations are not offered until verified.