Each engine is ordinary code over the normalized facts. The same input produces the same output. No language model runs in this path.
| Screen | Plan | What it establishes |
|---|---|---|
| Mission Control | Free | live mainnet telemetry, wallet gate, policy rule set. |
| Verification | Free | describe a settlement, run it against a domain, get an explainable verdict and a SHA-256 receipt. Nothing is broadcast. |
| Credentials | Free | XLS-70 objects held by the wallet, and which domains they unlock. |
| Domain Grid | Free | XLS-80 permissioned domains and their rule sets. |
| Audit Trail | Free | wallet history, filterable, exportable to CSV. |
| Portfolio & Radar | Desk | multi-wallet surveillance and the compliance radar. |
| Exposure Analysis | Desk | issuer freeze rights, Travel Rule scope, counterparty concentration. |
| Ledger & Policy | Desk | local adjudication history, evidence chain and receipt verification, investigations (cases a person opens on a verdict, with notes and a written resolution; a resolution never changes the verdict), the versioned institutional policy (drafts, simulation, activation, audit trail), policy simulation, signed export. |
| Check an Address | Free | read what the ledger publishes about any account. |
| Token Rights | Free | what the issuer of an NFT can still do to it after someone owns it — destroy it (lsfBurnable), rewrite what its URI points at (lsfMutable), block resale entirely, or take a cut of every transfer. All of it is encoded in the NFTokenID itself and decoded offline, so no server is asked and none can answer wrongly. |
| Inbox | Free | every check a stranger has addressed to an account, and whether the token each one offers has ever been issued by anyone. A currency code is not a name anyone owns — any account can issue a token called USDT — so an unsolicited claim for a large round sum from an issuer with no obligations is impersonation, not money. Receiving one costs nothing and cannot move funds. |
| Ledger Sync | Free | four public XRPL nodes queried and compared, with disagreement between them treated as the reading. |
| Settlement | Desk | what a transaction actually DELIVERED against what it requested. A partial payment can return tesSUCCESS having delivered a fraction of the stated amount; this is the screen for that question. |
| Ledger Garden | Desk | walk the ledger's relationships one validated read at a time — an issuer's assets, an asset's holders (from the first 200 of the issuer's trust lines, in ledger order; Issuance walks them all), an account's holdings and recent transactions, a transaction's settlement evidence — then hand the whole path to this agent as a question. |
| Provenance | Desk | how long an account has existed and who sent it its first XRP. Note the sequence number is not a transaction count on modern accounts. |
| Control Surface | Desk | how few signers can actually move a treasury, whether the master key bypasses the quorum, and how much balance is locked rather than spendable. |
| Order Book | Desk | how much of an order book's quoted depth is backed by an owner who still holds the asset. An offer rests whether or not its owner kept the funds, and nothing removes it until someone tries to cross it — on some mainnet books over 90% of the visible depth cannot fill. |
| Pool Governance | Desk | who votes an AMM's trading fee, on what share of the liquidity, and who holds the discounted auction slot. |
| Issuance | Institution | holder concentration and enforcement history for an issuer, from the issuer's side. |
| Authority Certificate | Desk | what authority an issuer has kept over an asset it issued — whether it can freeze a holder, whether it gave that power up irrevocably (lsfNoFreeze cannot be cleared once set), whether the asset is frozen right now, whether holding it needs the issuer's permission, whether one signer reaches the quorum alone, what it charges on a transfer between holders, and how concentrated the supply is. Each answer is a fact at one named ledger index, and the set is digested with SHA-256 so the same reading can be checked again later. It is NOT a score — no number is composited from the checks — and NOT a legal finding: whether an asset is decentralised or is a security is a determination for an agency applying statutory criteria, which this software does not evaluate. If the supply walk is skipped, or trust-line coverage falls below 95%, the concentration check abstains rather than passing. |
| Asset Passport | Enterprise | a signed, portable record of an asset’s compliance posture — issuer authority, freeze rights, concentration, domain eligibility — that travels with the asset and can be verified by any counterparty without re-running the checks. |
Generated from src/lib/agent/context.ts · src/lib/trust/boundary.json