RAVEN. / portability

The receipt is the portable artifact

Raven is not tied to one agent, wallet, UI, framework, device, or runtime. The unit that travels is the signed receipt — never the chat message, screenshot, or UI state. Machine-readable: /agent-portability.json.

Works from any surface

Hosted verifier · local MCP · ACP provider · OpenAPI client · Solana Agent Kit plugin · backend service · CLI workflow · human review console. Same contract everywhere.

Never authority

Screenshots · chat summaries · copied text without a signature · model explanations · social links · token marketing pages · wallet UI badges without a receipt. If it is not the exact signed JSON, it is not the receipt.

Handoffs

When a token passes between agents, the exact receipt JSON and signature travel WITH the action request. The receiving agent verifies signature, keyId, engineVersion, observed slot, verdict, findings, coverage gaps, and staleness before acting — never trusts a prior agent's verdict string.

Context engineering

Context can help an agent decide what to ask Raven, but only the signed receipt states what Raven actually checked. Needed: mint, token program, optional metadata/pool addresses, action context, policy version. Ignored or rejected: social hype, influencer claims, screenshot-only evidence, marketing copy, "trust me", user-supplied rpcUrl/issuerIdentity, anything price-related. Better context improves coverage; missing context becomes a coverage gap; unsupported context never improves a verdict.