YOUR WORKFLOW. YOUR DECISION.
Review an action
The example: your online shop’s support assistant
You run an online shop. Alex asks, “Has my blue mug shipped?” Order 1042 is packed, waiting for carrier collection, with no tracking number yet. Your AI assistant has checked the question and order, then drafted a reply. Petasos is where you decide whether it may send it.
Start by reading the reply. Mark it reviewed, then allow or decline it. If you allow it, choose a practice send result below. The other five areas explain what was recorded, how the send is checked, and how rules and limited jobs work. All data is fictional. No apps connect, no messages are sent, and the record checks perform no real signature verification.
01 / ONE ACTION, IN MOTION
One reply. Your decision.
Follow one support reply from a proposed consequence to an honest outcome. Change the details. See what holds.
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.
- 1 Read the reply
- 2 Decide whether to allow it
- 3 Explore a send result
Review this customer reply.
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.
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.
Inspect this action’s evidence →What if the assistant changes something?
A changed action needs a fresh review.
Permission comes first. Choose one of these practice send results to see what can be known afterward. No real send occurs.
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 replyReferences 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.
Draft the reply.
Can request a send. Cannot approve its own reply.
Keep the decision separate.
The intended system keeps approval records and signing keys outside the assistant’s access.
Check before sending.
Check the sender, recipient, exact reply, purpose and expiry. Remember the attempt so the same request cannot create a second send.
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.
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
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.
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.
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.
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.
No scope approved yet.
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.