# Release criteria and open decisions

Availability: **Proposed specification**  
Documentation: **1.1** | Updated: **19 September 2026**

[Documentation home](../README.md)

Release stages are defined by evidence. Calendar targets do not replace an installable artifact, an operating endpoint or a reproduced acceptance result.

| Stage | Required evidence | Current scope |
| --- | --- | --- |
| Local reference | Source, explicit contract, runnable fixtures and verification | Reference 0.2 available |
| Controlled network pilot | Authenticated endpoint, node runtime, support matrix and NET test results | Proposed; not supplied by this release |
| Paid service | Pricing, data terms, metering reconciliation, incident and recovery procedures | Requires implementation and operating evidence |
| Open provider or chain extension | Published control model, admission rules, deployed contracts where relevant and security review | Separate approval and evidence required |

## Decisions to close before a pilot

| Decision | Required basis | Suggested accountable function |
| --- | --- | --- |
| Initial remote workload | Customer need, acceptance dataset, cost and access constraints | Product and engineering |
| Hardware support | Compatibility tests and raw workload records | Infrastructure engineering |
| Lease and retry limits | Partition tests and external side-effect analysis | Backend architecture |
| Identity and signatures | Threat model, registry design, library review and test vectors | Security engineering |
| Billing and data policy | Metering source, payment reconciliation and retention requirements | Service operations |
| Chain integration | Specific business requirement, privacy, finality and control costs | Architecture and governance |

The functions above are responsibility proposals, not appointments of named personnel. Each approved decision needs a record identifier, owner, rationale, affected protocol version, approval date and supporting evidence.

A public release should connect each claimed capability to a stable documentation page, a versioned artifact and its validation record. Preview features must retain their availability label until their acceptance conditions have been met.

[Previous](./conformance.md) | [Next](./evidence.md)