RAVENThe 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.
Know which surface produced the artifact
The current signed artifact comes from hosted POST /receipt/v1 and can travel through an approved OpenAPI client, backend, CLI, or human review console without changing its wire object. Local MCP is unsigned developer output, not a signed receipt-v1. ACP is sandbox-only and not publicly hireable. POST /verify artifacts are legacy v2 compatibility. These surfaces do not share one indistinguishable contract.
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-v1 JSON and signature travel WITH the action request. The receiving agent checks payloadHash, receiptId, signature, signerPublicKey against its independent pin, expected subject, rulesVersion, slot, findings, coverage gaps, and freshness before acting. It never trusts a prior agent's summary. Legacy v2 handoffs remain explicitly versioned and retain their own keyId/verdict fields.
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 erases findings or creates evidence.