Developers
Documentation
The architecture, the security model and the decision records are the documentation. They are written to be read by somebody deciding whether to trust this, not to be skimmed.
What it changes
- ArchitectureNineteen sections covering the system shape, layer boundaries, tenant isolation, money, authorization, the ledger, payments, compliance, offerings, the register, asset lifecycle, audit, events and the contract layer.
- Security modelEvery control, how each is verified, and an explicit table of what is *not* mitigated — including malware scanning, SSRF egress control, oracle manipulation and compromised deployer keys.
- Decision recordsWhy sessions are opaque rather than JWTs, why invariants are enforced twice, why payments post to the ledger in one transaction, and why compliance rules are data.
What it includes
ConventionsMoney as exact minor units, every division naming a rounding mode, and no floating point anywhere near a balance.
Testing747 automated tests including a Solidity suite executing against a real in-process EVM.
EnvironmentsLocal, development, test, staging and production, with chain families constrained by tier.
What this deployment does not do
Stated plainly
Published API reference documentation is not yet available, because the public API surface is not yet exposed.
See it against something real.
Bring an instrument you are actually considering. Structuring it is the only way to judge whether the model fits.