This protocol defines how testers can experience AION Guard, KINE decisions, approval intelligence, and Agent Arena without risking real funds.
Core doctrine
Real beta experience
Testers can experience the guard, scanner, KINE decisions, receipts, and Agent Arena.
Mainnet is read-only
Mainnet wallet testing is inspection, scoring, warning, and receipt generation only.
No custody. No hidden execution.
AION Guard must never request secrets, hold funds, or move assets without explicit wallet approval.
The complete beta experience without real capital risk.
Safe inspection, scoring, warnings, and receipts.
Read wallet public address.
Read connected chain.
Read visible token balances.
Read token approvals and spender contracts.
Analyze approval risk.
Show wallet health score.
Generate read-only receipts.
Explain ALLOW / WARN / BLOCK reasoning.
These boundaries protect testers and the product.
No seed phrases.
No private keys.
This is not production security software and must remain truth-bounded during beta.
No hidden signatures.
No automatic mainnet transactions.
No automatic approval revokes.
No custody of user funds.
No direct fund movement by AION Guard.
No agent-controlled mainnet execution.
Full execution experience belongs on faucet funds first.
Execution testing must use testnet wallets.
Use faucet funds only.
Use dummy contracts and dummy approvals.
Use explicit testnet warnings.
Require visible wallet confirmation.
Generate receipts for all test actions.
Agents propose. AION governs. Wallet signs only with explicit approval.
Agents may propose actions.
Agents may not execute directly in beta.
AION Guard must classify every proposal first.
KINE must produce ALLOW / WARN / BLOCK.
User or team approval remains required.
Production agent runtime requires later audits.
Browser Runtime
KINE Guard observes approved KINE origins, classifies supported signing context, and explains warnings before the user acts. It remains read-only: it does not intercept signing, replace providers, mutate transactions, or enforce policy.
Observe supported signing context on approved KINE origins
Normalize intent
Ask KINE Kernel
Show read-only warning context without intercepting the wallet
Prepare Guardian, structured-record, and supporting-evidence references
Let the user decide whether to continue or cancel in the wallet
Layer 1
Layer 1 Website Runtime - public beta
Layer 2
Layer 2 Browser Runtime - certified beta
Layer 3
Layer 3 KINE SDK - certified local alpha
Layer 4
Layer 4 Governed Execution - Sepolia proof path
Detected intent: WalletIntent
Selected governors: Risk Governor, Policy Governor, Evidence Governor
Plain-English explanation: Low-risk swap intent passes the governed preview with a clear evidence trail.
Required action: Continue to the wallet only after reviewing the read-only warning context.
Truth boundary: demo only
Detected intent: WalletIntent
Selected governors: Risk Governor, Policy Governor, Budget Governor, Identity Governor
Plain-English explanation: Unlimited approval is an approval-risk pattern that should surface before signing.
Required action: Review allowance scope and require approval or cancel.
Truth boundary: demo only
Detected intent: WalletIntent
Selected governors: Risk Governor, Policy Governor, Evidence Governor
Plain-English explanation: A drain-like pattern warrants a strong warning. Blocking requires a separately verified governed route.
Required action: Cancel the action and inspect the supporting evidence.
Truth boundary: demo only
Truth boundary