Operations
Security and trust boundaries
Understand what LoomCredit protects, what it deliberately does not claim, and how to operate the prototype safely.
Trust boundaries
| Boundary | Rule |
|---|---|
| Source chain | The source receipt and trusted emitter are authoritative for the encoded event. |
| USC verifier | Native verification plus exact event checks are required before evidence registration. |
| Model | May propose a typed quote; never receives private keys or authorizes capital. |
| RiskGuard | Recovers the signer and enforces deterministic limits before reservation. |
| Browser | May inspect evidence and run local fixtures; does not submit transactions. |
Secret handling
- Keep .env ignored and out of commits, screenshots, logs, and prompts.
- Keep worker and agent keys out of web/.env.local and all NEXT_PUBLIC_* variables.
- Use separate source, deployer, worker, and agent identities before serious deployment.
- The web service emits a baseline Content-Security-Policy plus frame, referrer, permission, and content-type protections. Recheck allowed analytics hosts when changing providers.
- Authentication writes have a bounded single-instance limiter and return Retry-After; configure AUTH_ORIGIN explicitly and use a trusted distributed edge limiter before exposing authentication to many users.
- Rotate any credential pasted into chat or committed to history.
Known limits
- The current prototype uses SQLite and is not a multi-instance production data layer.
- SandboxCapitalVault is accounting-only test liquidity; it is not custody or a lending product.
- On-chain evidence does not prove physical delivery, repayment, or off-network duplicate financing.
- Public deployment, eligibility, and submission media require human-owned release steps.
Documentation is generated from the current repository contract. For the recorded testnet evidence, inspect the live proof console.