# Security Boundaries and Known Limitations

This is a prototype. Nothing in the local test suite, static analysis or dependency check constitutes independent review, certification, or an assurance that real assets are safe.

## Sandbox boundaries

- Run the fixture with `npm run sandbox`; the server binds to loopback and uses in-memory SQLite.
- Use only `TEST-USD` and fixed, short-lived test personas. They are not production authentication.
- No private provider key is sent to the browser; the sandbox harness creates its signed mock-provider message server-side.
- API authorization, object-state checks and idempotency remain authoritative for mutations. The UI cannot grant itself pool/reviewer/merchant privileges.
- Do not expose or tunnel the sandbox; harness-only identity, provider and simulation-clock routes are not production endpoints.
- Reconciliation is read-only and can report `NOT_VERIFIABLE`; it does not repair state or prove custody.

## Separate blockchain prototype

The local Hardhat vault is not integrated with the sandbox ledger. There is no durable cross-system transaction journal, confirmed-chain event cursor, restart resume or complete reorg recovery. No verified Base Sepolia deployment is evidenced. There is no wallet integration, live provider, production monitoring, incident response or independent security audit.

## Release boundary

No mainnet, real funds, public deployment or hosted testnet status is authorized by the presence of code or tests. External deployment and any real-asset use require a separately approved gate, threat model, independent review, documented key governance, operational controls and explicit evidence.