Skip to content
SineraDocs

Conformance and release gates

What the ATP conformance matrix covers, and why production promotion is still pending.

Two documents describe how far ATP 2.4.0 is from production. The conformance matrix maps each protocol requirement to the code and tests that express it. The release gates say whether the whole candidate may be promoted. This page explains both in plain terms.

Implementation candidate

Production is not approved

The release verdict is that local checks pass and production promotion is blocked. Several gates are open. Nothing on this page certifies ATP as secure or ready for production use.

The conformance matrix

The matrix is a traceability table. Each row has an ID, a requirement, the place in the implementation that expresses it, and the kind of evidence needed to confirm it.

A row that says a source path was identified means only that the code appears to contain the behavior. It does not claim that tests, formal proof, audit or deployment checks are complete. The matrix carries no pass or fail verdict. Only the release gates do.

The matrix groups requirements into these areas:

AreaExamples of what a row checks
Identity and signingAtom identity is independent of a global counter. Signatures bind the chain, the deployment and the 2.4.0 domain
Roots and refundsA payer cannot replace a root or the refund beneficiary
Creation and escrowCreation, exact escrow and asset reservation succeed together
Lifecycle and timeDeadlines have exactly one owner at each boundary. A material revision needs Buyer reacceptance
DisputesOnly two presets exist, a dispute opener cannot choose the economics, and consensus or an award cannot finalize an ACTIVE Atom
AuthoritiesThe authority endpoints and committee are bound to the configuration, and roots cannot alias them
Fees and settlementFee rules are fixed per Atom. Escrow value conserves and settles once
AssetsAsset quantity conserves independently of the money split
ConfigurationPause blocks only new creation. Replacement is a fresh deployment

The release gates

Promotion requires every gate, from G0 to G9, to pass for one exact, frozen manifest. A later gate cannot make up for an earlier mismatch.

GateTopicCurrent status
G0Normative specification freezeOpen
G1Source, ABI and traceability freezeOpen
G2Build, compiler configuration and runtime sizeLocal pass
G3Executable verification (tests, fuzzing, invariants)Local pass
G4Security analysis and finding closureOpen
G5Formal verification and implementation linkageBlocked
G6Compiler and bytecode provenanceOpen
G7Fresh deployment and independent readbackBlocked
G8Canary, soak and operational readinessBlocked
G9Independent review and production promotionBlocked

A local pass means the checks ran on the candidate source. It never implies production readiness.

What the status means

  • Tests pass locally. The default executable test lanes pass on the current candidate. That is useful evidence, but it is not a frozen-release record.
  • Security analysis is not closed. Internal review work is not independent review. A gate stays open until every finding is dealt with and an independent campaign covers the frozen scope.
  • Formal work is partial. Some scoped formal evidence exists. Open queries and incomplete proof scope keep the formal gate blocked.
  • A testnet deployment exists. It has been read back on BSC Testnet, but that does not approve the deployment. Canary and soak runs have not been accepted. See Networks and deployments.
  • No whole-protocol certification. Sinera does not claim that ATP has a complete security certification.

Earlier test and audit results from older protocol versions are historical. They cannot close a 2.4.0 gate. Any semantic change to the source reopens the gates it affects.

What this means for you

If you build on ATP today, treat it as a candidate on a test network.

  • Use BSC Testnet. Do not move real value.
  • Expect the specification and tooling to change before any release.
  • Check this page and Status for changes.

Next