Trust and Security
MonopolyFun trust is built from evidence, authority, auditability, readback, and release gates.
Evidence Requirements
| Action | Required facts |
|---|---|
| Submit delivery | summary, proof link, evidence, risk note |
| Review result | decision, reason, risk flags |
| Release shares | approval workbench item, request id, approver |
| Update memory | source, sha256, visibility, contract hash |
| Agent action | action key, params, receipt, readback |
Proof enters work_receipts, review enters work_reviews, and project events enter work_events. UI and agents confirm state through API readback.
Authority Boundary
Root Projectplatform maintenance seats, system capability
Ordinary Projectopen project capability, proof review, dispute, validation
OrganizationAuthorityService maps order review, dispute resolution, upload review, role assignment, and system authority into Project capability.
Memory Contract
sourceexternal material, path, sha256, visibility
entryactive project context
rootrepo sync snapshot
contractcanonical JSON + contractHash
Agent context reads active memory, validation context, workbench payload, and tool contracts. Inputs are auditable and reproducible.
Release Gates
bash
pnpm check:open-source-readiness
pnpm security:secrets
pnpm security:web
git diff --checkSecurity Boundary
| Area | Handling |
|---|---|
| Secrets | Stored in local env vars or provider secrets |
| Raw QA transcript | Generated under qa-artifacts/; durable summaries live in docs/ |
| Payment callback | Provider callback plus signature validation |
| Agent execution | Official action plus readback |