Skip to main content
Request a demo
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.

One transaction boundaryThree stacked elements — a record, a rule and a ledger posting — enclosed by a single boundary, indicating that all three commit together or not at all.ONE TRANSACTION BOUNDARYRecordwhat is trueRulewhat is permittedPostingwhat it did to the bookscommit together

What it changes

  1. 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.
  2. 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.
  3. 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.
Ask, agree, then actThree steps. One person requests, a different person approves, and only then does the state change. The approval binds to what was requested, so editing it afterwards invalidates the sign-off.Requestone personApprovea different oneActnow it movesThe approval binds to what was asked.Edit it afterwards and the sign-off is void.
Every irreversible act on this platform takes this shape, whatever the subject of the page: one person asks, a different one agrees, and only then does anything move.

What it includes

ConventionsMoney as exact minor units, every division naming a rounding mode, and no floating point anywhere near a balance.
Testing1,103 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.

See it against something real.

Bring an instrument you are actually considering. Structuring it is the only way to judge whether the model fits.

Request Enterprise DemoBack to developers
Your instrument, against this modelAn unspecified asset on the left feeds four stages: structure, compliance policy, the offering book and the register. The asset is drawn as an outline because it is the reader's, not the platform's.Your assetwhatever it isStructurePolicyBookRegister