← RailCall home · Security guide

UNDERSTAND THE CONTROLS BEFORE YOU CONNECT

You approve the action.
You can inspect the record.

Try the boundaries with fictional data. See what a changed request, a reviewer’s decision, and a stop command mean—without connecting a service.

EXACT-ACTION APPROVALBrowser-only example
01 / REVIEW THE REQUEST

Weekly sales report

Destination
finance@example.test
Sample total
$12,840
Permission
Exact payload · one use

Start the example to create a temporary signing key in this browser.

02 / INSPECT THE RECORD

Don’t just take its word.

Each example event gets a real Ed25519 signature. Open a receipt to inspect its fields, then try changing a copy.

No report or message is sent. Keys exist only for this page session and are not trusted production identities. Signatures do not prove an answer is correct, an action occurred, or that the end of a log was not removed.

WORK TOGETHER. KEEP THE BOUNDARIES.Fictional agents · no model calls

Check an invoice. Record it. Approve the payment.

Matched invoices up to $500 can be recorded automatically. Every payment needs Finance approval.

Advance each step to see what happens.

Illustrative approval roles and rules, not a connection to your account. No payments, CRM changes, messages, or AI requests leave this example.

YOUR NETWORK. YOUR RULES.Illustrative control model

This computer

Local work permitted

Trusted team computer

Transfer blocked

External service

Exact transfer needs approval

0 simulated transfers. No real data sent.

These buttons do not control your device or network. Real blocking requires enforcement on every permitted route. Stopping work cannot undo an already completed action.

What these examples prove—and what they don’t