Trust and limits
Status: Not decidedStatus: Built, runs on simulator
Trust in Merces depends on the implementation, its operators, the evidence supplied to it and the terms that still need legal review.
The checked source is local software. Independent audits have not started, and no launch is established by these docs. A passing arithmetic test does not establish a production service or an enforceable agreement.
Start with the visible limits
- Security review and audit status distinguishes internal review from independent work.
- Privacy data map shows who can read each class of information.
- Known limitations identifies unavailable or provisional parts.
- Public open questions identifies the decisions still needed.
A backer can see public payment records without seeing the issuer's raw income evidence. A report verifier briefly sees an attested figure in memory. Server-key encryption, device-only data and encryption for a chosen attestor are different boundaries.
The role model, governance analysis and legal risk texts are being reviewed separately. Their absence from the published navigation does not mean those questions are settled.
What can go wrong
A status badge describes development progress. It does not remove financial, operational, evidence or privacy risk. Check the actual terms and deployment when they exist.