Examples Gallery
Examples that keep uncertain actions honest.
Start with a small local example. See what happens when a business action succeeds but its response disappears, and how to check the result before retrying or confirming.
These examples use AnswerUp Core with local test business systems. Your application supplies trusted identity, authorization, admission, business access, independent verification, recovery storage and customer messages.
Read the guides and public source here. Running the examples requires the selected SDK packages through approved private-preview access.
Runnable locally · Test HTTP service
A reservation succeeds. Its response disappears.
A booking is saved, but the application never receives the response.
- Demonstrates
- Keep your booking and lookup functions. Check the original booking before confirming, without sending it again.
- Validated
- Real SDK packages and localhost HTTP: UNKNOWN resolves to COMMITTED after an exact receipt check, with one booking and zero recovery redispatches.
- Scope
- Sample restaurant and process-local host state; no real restaurant or production authorization.
Runnable locally · Test HTTP service
Reserve stock and confirm only what was verified.
An inventory request may succeed, be refused or lose its response.
- Demonstrates
- Try a small stock integration with refusal, duplicate requests and an independent receipt check.
- Validated
- The selected Generic HTTP preview.4 first-action exercise ran with real SDK packages: a lost response resolves through verification without additional provider POSTs.
- Scope
- Sample inventory and policy on localhost with process-local admission; no production persistence or distributed guarantee.
Runnable locally · Single-writer reference
Recover an uncertain action after restarting.
An equipment reservation is still uncertain when its host process exits.
- Demonstrates
- Resume checking from a saved host record in another process, without repeating the write.
- Validated
- Controlled local restart recovery with a single-writer file store: one original mutation, three verifier reads and zero recovery redispatches.
- Scope
- Test equipment service and controlled graceful restart. This is not arbitrary-crash or distributed recovery, or a supplied production store or recovery worker.
Runnable locally · n8n CLI verified
Verify a record update from n8n.
A workflow needs to distinguish a confirmed update from a lost response.
- Demonstrates
- Let n8n schedule calls while your Node.js host governs the update and checks the business receipt.
- Validated
- n8n 2.0.3 CLI import and execution of the 14-node governed workflow: confirmed and uncertain updates, followed by verifier-only recovery with no redispatch.
- Scope
- Local test record service. Graphical editor execution and real CRM integration were not validated; this does not establish whole-workflow atomicity.
Runnable locally · Simulated tool calls
Handle a Retell-style equipment request.
A tool call asks your application to reserve equipment.
- Demonstrates
- Connect the tool call to a governed reservation while your application supplies trusted caller context, authorization and an independent equipment check.
- Validated
- The selected Retell adapter and equipment example ran with simulated tool calls and a localhost service, including controlled recovery with one mutation and no recovery redispatch.
- Scope
- No live voice session, telephony transport or external equipment system was validated.
Optional companion · Runnable locally
Save useful diagnostics without logging payloads.
Your host needs readable and structured records for troubleshooting.
- Demonstrates
- Record result observations in .log and .jsonl files through one allowlist, using per-run HMAC aliases for identities.
- Validated
- The public companion emits both formats from real Actions result observations while preserving first-action behavior and recovery without redispatch.
- Scope
- Diagnostic logs are not authenticated audit evidence, a recovery store or a Trace exporter. Inputs, authority data, business payloads, receipts and secrets stay out of ordinary logs.
Optional local viewer · Accepted captured runs
Inspect an uncertain result in Trace Local.
You want to compare an initial uncertain result with its later reconciliation.
- Demonstrates
- Load your own captured evidence. Compare package fields with separately labeled host observations and see where evidence is missing.
- Validated
- Trace Local preview.7 imported captured initial and reconciled SDK results, showing UNKNOWN followed by COMMITTED/PRESENT with permitted claims.
- Scope
- The viewer opens empty. It does not independently verify business truth or authenticate host-reported reads. Ordinary logs are not Trace import files.