Connected is not the same as safe.
AION Guard treats every wallet connection as a live risk context. Session intelligence tracks chain posture, approval context, behavioral drift, and future session receipts before any governed execution path is allowed.
Session doctrine
Observe first.
Read-only wallet state helps establish session context.
Classify before trust.
Connected wallet sessions still require KINE posture checks.
Never ask for secrets.
AION never asks for seed phrases, private keys, or hidden signing access.
KINE Runtime
Shared activity status
One browser-local activity context supports wallet posture, Action Review, Guardian monitoring, and History.
Layer
Layer 1 Website Runtime
Intent
Observed session
Governors
Identity, Policy, Risk, Budget, Evidence
Last decision
No decision yet
Receipt
No receipt yet
Decision: No decision yet
Events
0
Boundary
Read-only beta / no custody / no hidden execution
KINE Session Timeline
Runtime activity trail
This session view shows how one wallet context becomes shared intelligence across KINE.
Awaiting wallet
Connect a supported browser wallet to begin runtime session
Runtime normalization
Pending wallet connection
Posture analysis
Waiting for wallet context
Action Review
Waiting for an action to review
History readiness
Waiting for browser-local activity
KINE Runtime Event Bus
Live session activity
KINE records browser-session activity so Sessions, Structured Records, Audit, and monitoring views can share one history context.
Session intelligence signals
What AION should observe while protecting a wallet session.
Wallet Connection
A connected wallet only proves a session exists. It does not prove the session is safe.
Network Posture
AION should detect whether the wallet is on expected chain, wrong chain, testnet, or mainnet.
Session Age
Long-lived sessions, repeated reconnects, and stale tabs can become execution risk signals.
Approval Context
High-risk approvals, unfamiliar spenders, and unlimited permissions should raise session risk.
Behavior Drift
Sudden wallet switching, unusual contract interactions, or repeated failed actions may indicate danger.
Session Receipt
Future AION sessions should emit receipts for connection, warning, preview, and decision events.
Session risk model
A future live classifier can map wallet sessions into these tiers.
Wallet connected, expected chain, no dangerous approvals observed.
Action: Allow normal read-only beta inspection.
Chain mismatch, stale session, or unclear wallet context.
Action: Warn user and request confirmation before previews.
Risky approval pattern, suspicious spender, or unusual behavior drift.
Action: Increase friction, recommend revoke/review, generate warning receipt.
Known malicious spender, compromised session, or agent authority escalation.
Action: Block execution path and route to threat response workflow.
Read-only beta rules
AION observes and governs before it ever reaches execution.
AION may read wallet address, chain, balance, and public approval context.
AION may classify session risk and explain warnings.
AION may recommend safer next steps.
AION must not ask for seed phrases.
AION must not store private keys.
AION must not silently sign or execute.
AION must keep mainnet beta read-only until explicit phase lock.
AION must treat connected as observed, not authorized.
Session red lines
AION blocks beta readiness if any session flow violates these rules.
No seed phrase input during wallet connection.
No private key collection under any beta flow.
No hidden signing request.
No automatic mainnet write transaction.
No agent-triggered wallet execution.
No confusing fake wallet prompt.
No public exposure of wallet metadata beyond user consent.
No session considered safe without current chain and risk context.
Future runtime hooks
Controls that will make session intelligence live instead of simulated.
Wallet session receipt.
Network mismatch detector.
Approval spike detector.
Known spender reputation feed.
Session anomaly timeline.
Risk-based UI friction.
Safe-mode banner.
User-facing KINE reason codes.
Session intelligence summary
The minimum rule for wallet-connected beta safety.
A connected wallet is only an observed session. AION must classify risk before trust.