No protected action runs without a valid approval.

For an IAM tool (access permissions), API gateway (request filter), chat bot or agent framework, check which actions actually pass through its checks.

The published door guard checks actions sent through it. It can hold risky actions for approval. It cannot see a route that bypasses it.

Ask whether changing the amount or recipient makes an earlier approval invalid.

The signed approval binds to the held request through paramsHash, a fingerprint of the parameters defined by that receipt format. A signature proves key use, not a person’s identity or understanding.

For an audit-log or AI-observability tool, ask whether exported records carry signatures and whether you retain a trusted checkpoint outside the system.

The open-source checker verifies signed receipts offline. Keep the public keys, their validity history and a trusted checkpoint to check old records. An approval is not proof of execution.

Ask for a working example in your language, and separate a prototype from a supported production integration.

The public Gate source includes a plain-HTTP reference path. It is a prototype using a test ledger, not a supported payment or production integration. The Gate is not published on npm.

Check both the approval signing key and the key that can write to the protected system. Closing one route is not enough if another direct key still works.

Under the four required rules, only the vault’s own lock holds its write key; no Gate, agent or person receives a direct key for protected actions. The vault guard is being built. The published door guard alone does not meet these rules.

Check whether the phone signs the exact request and whether the app is publicly available.

Coming to the App Store and Google Play. Working builds exist, but neither app is in a store yet, so neither can be downloaded today. The published proxy also documents the noa-approve command for local approval.

Ask what the hosted service stores, what it can read, and whether it can authorize an action.

Phone approval through the hosted relay mailbox was last proven for our own workspace on 29 September 2026. It carries encrypted approval displays and signed decisions; it cannot approve or execute an action. It is separate from the supported vault lock being built.