How Sinera works
How a commercial agreement becomes a Commercial Atom, how ATP owns its lifecycle, and where other systems stop.
Sinera separates convenience from authority. Apps, wallets, payment providers and AI help people prepare commercial work. Only one system, the Atomic Transaction Protocol (ATP), owns the lifecycle state of a commitment. This page explains that split.
Implementation candidate
ATP 2.4.0 is an implementation candidate. Its only public deployment is BSC Testnet (chain id 97). See Status and roadmap.
The flow in one picture
Application identity (sign-in)
-> verified wallets and an explicit Root
-> planning by a person, an AI agent, or CAEM
-> deterministic intent and authority checks
-> ATP execution core
-> settlement, asset and resolution effects
-> canonical events and evidence
-> indexers and read views (derived, never authoritative)Each arrow is a hand-off. A later step never grants authority that an earlier step did not have.
From agreement to Commercial Atom
CAEM is the commercial analysis layer. It reads commercial material, such as an order or an agreement, and proposes how to break it into units. It only prepares proposals. It cannot sign, open a dispute, move funds or change ATP state.
A Commercial Atom is the smallest commercial commitment that needs its own attributable lifecycle and can reach its own final outcome. One order can contain several Atoms, because one order may hold several obligations that close independently. A contract clause does not map to an Atom automatically.
CAEM labels a proposal with one of four outcomes:
| Outcome | Meaning |
|---|---|
CANDIDATE | A semantic graph exists. Blockers or authorization may remain. |
MATERIALIZABLE | The material terms are exact enough to move forward. This is not a signature, an accepted contract or an on-chain effect. |
UNRESOLVED | Material facts are missing or ambiguous. |
REJECTED | The representation breaks an invariant. |
If a required term is unknown, such as a counterparty address, price, token or expiry, the proposal is blocked. Nothing fills the gap from a guess or a default template.
ATP owns lifecycle state
ATP is the reference execution protocol and system of record for commercial lifecycle state. That covers authorized progress, finality, dispute and recovery. Each state domain has exactly one owner:
| State | Owner |
|---|---|
| Sign-in identity and profile | Identity provider and application backend |
| Which wallet is the Root | Verified application wallet relationship, re-checked on each command |
| Funding provider status | Funding integration and application record |
| Commercial Atom lifecycle | ATP core (AtomCore) |
| Custody, escrow and settlement | Escrow and settlement contracts |
| Asset entitlement | Asset registry |
| Delegation authority | Delegation manager |
| Dispute decision | Resolution manager plus an authorized lifecycle transition |
| AI or CAEM plan | Planning layer. It is not authoritative. |
| Read views and history screens | Indexers and application databases. They are derived. |
No component silently owns another's state. An action on one Atom does not rewrite another Atom's private lifecycle.
Boundaries that hold the system together
Identity
Commercial identity and execution identity are separate. These roles are all different things:
application user != Root wallet != delegate != payer != buyer != beneficiarySigning in proves who you are to the application. It does not prove you control a Root wallet. The Root may act through a payer, a wallet, a backend, a delegate or an AI agent without handing over the underlying commercial position.
Authority
Delegation creates an execution envelope, not unlimited power. Scope, value, counterparties, time and expiry can all limit it, and the Root can revoke it. Read Intent is not authority for the details.
State ownership
Funding is outside the Atom lifecycle. A purchase draft or a "funding pending" record in an app is not an Atom and is not an ATP stage. A webhook from a payment provider can update app status. It is never a signature or a delegation.
Finality and recovery
A final outcome stays in the record as historical truth. Recovery is append-only: a refund, replacement or other remedy is recorded as what happens next. Failures stay local to the Atom they affect.
What this means for you
- If you use the App or Platform, your sign-in identifies you. It does not move money or approve anything by itself.
- If you build on ATP, check every authority claim against the protocol, not against an app, a prompt or an agent. See the delegation reference.
- If you only want to verify what happened, use the Explorer. It is read-only.