> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usespoke.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Product evidence matrix

> Trace each product capability to live behavior, source, tests, inspectable proof and honest limits.

The [versioned engineering evidence matrix](https://github.com/Enoch208/spoke/blob/main/docs/evidence.md) links implementations, tests and public proof for all five entered categories. The table below summarizes what a reviewer can actually inspect.

| Category | Product capability and journey | Evidence | Remaining weakness |
| - | - | - | - |
| Social, Attention & Culture | Merchant discovers/compares a distributor, reviews a Passport, invites them, then inspects their contribution through a live network and settled receipt | [Example Passport](https://usespoke.xyz/u/0x7e05742C7c6F8A7Bedf1F77627299DfEdAA18260), [receipt 4](https://usespoke.xyz/receipts/10143/4), [journey artifact](https://github.com/Enoch208/spoke/blob/main/packages/contracts/deployments/10143-production-journey.json) | Scripted activity does not prove adoption; no unmeasured conversion rate |
| Nansen AI | Merchant requests external public wallet context and reviews evidence beside native performance before a partnership | [Actual provider sample](https://github.com/Enoch208/spoke/blob/main/docs/proof/nansen-public-example-20261015.json), [service and tests](https://github.com/Enoch208/spoke/blob/main/apps/api/tests/partner-research.test.ts) | The researched example is not a Spoke distributor; no measured decision-quality improvement |
| Envio | Canonical events drive Passport history, Network Activity, receipt links and graph refresh | [Live network](https://usespoke.xyz/c/1/network), [health](https://api.usespoke.xyz/v1/health), [indexer tests](https://github.com/Enoch208/spoke/blob/main/apps/api/tests/indexer.test.ts) | Bounded polling, prototype capacity; no production load/SLA claim |
| Best Mera-powered UX | Passkey-first sign-in retains the campaign/referral path; clear cancellation/support guidance and existing bounded testnet gas help | [Login](https://usespoke.xyz/login), [guidance tests](https://github.com/Enoch208/spoke/blob/main/apps/web/tests/passkey-guidance.test.ts) | Physical Safari/Chrome account creation and a new successful passkey action need verification |
| One Passkey, Many Keys | Same original passkey controls account operations and a separate encrypted campaign workspace with ciphertext sync and backups | [Workspace](https://usespoke.xyz/earn/workspace), [crypto tests](https://github.com/Enoch208/spoke/blob/main/apps/web/tests/campaign-notes.test.ts), [API tests](https://github.com/Enoch208/spoke/blob/main/apps/api/tests/workspace.test.ts) | Physical cross-device PRF restoration is unverified; wallet recovery cannot recover the notes key |

## Device verification procedure

1. Record browser, OS and passkey provider on two devices. Start from a campaign/referral URL, cancel sign-in once, then complete it with the original passkey and confirm the return context.
2. Perform a testnet link or purchase action, record its transaction and verify its indexed result. Do not use real funds for this commerce test.
3. Write non-sensitive test text in a campaign notebook, **Encrypt & sync**, download an encrypted backup, reload and reopen with the same passkey.
4. On the second device, use that same provider-synced passkey and verify PRF support by actually decrypting the synced note. Record unsupported combinations as failures or limitations, not successes.
5. Test conflicting edits on disposable notes, restoring a backup and retrying after an interrupted sync. Keep the original working copy until restoration is verified.

## Merchant usability test

Ask a consenting merchant to compare two distributors, inspect a receipt, send an invitation, then have the recipient accept and create a link. Record where they hesitate, which states are unclear and whether they can find the final reward allocation. Collect observed feedback; do not substitute scripted tests for user adoption.

All proof must retain its network and data origin: demo fixtures, scripted testnet assets, external cached history and real mainnet funds are different things. Contract source verification and passing tests are not an independent security audit.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.