v0.6.3 shipped as an evaluation / beta release with CI-backed quality gates and honest stability labels. Code blockers for that release are closed; organizational gates remain before v1.0 production positioning.
Tracked as RB-007 / #51 in release-blockers.md.
| Claim | Status |
|---|---|
| Language, verify, sim, replay, recovery, continuity demos | Supported for evaluation — README smoke + golden tests in CI Integration |
| Control Center, REST v1, SDKs | Supported for evaluation — cross-interface consistency in CI Fast + Integration |
| Default AI / in-memory transport | Mock-backed — live paths require env and optional features |
| Enterprise ops pillars (E1–E4) | Stable in code/CI — organizational soak and external audit not yet complete |
| Full production readiness | Not claimed until gates below are accepted |
Public messaging: use evaluation / beta, link known-limitations.md, and do not imply IEC/ISO certification or managed-cloud SLAs.
v1.0 is a major workspace bump (1.0.0) when code and organizational exit criteria are met.
See ROADMAP.md § v1.0 and
versioning.md.
Run representative workloads in staging or pilot environments — warehouse fixture,
rover/self-healing showcase, Control Center with --config + --program.
# One-time: record soak start date
./scripts/enterprise_ops_field_soak_init.sh
# After 30+ days, verify elapsed time (gate script checks this)
./scripts/enterprise_ops_stable_promotion_gate.sh
Detail: field-soak-gate.md · enterprise-ops-stable-promotion.md
Acceptance: no P0/P1 incidents attributable to platform core during soak; promotion gate passes
without SPANDA_ENTERPRISE_OPS_SKIP_SOAK=1.
Generate the audit prep packet and engage an external reviewer.
./scripts/security_audit_prep.sh
# Artifact: .spanda/security-audit-prep.json (or SPANDA_SECURITY_AUDIT_PREP_FILE)
Detail: security-audit-third-party.md
Acceptance: signed audit report on file; no unresolved critical findings; promotion gate passes
without SPANDA_ENTERPRISE_OPS_SKIP_AUDIT=1.
Maintain through v1.0 tag:
Use this when preparing the 1.0.0 workspace tag:
| # | Item | Owner | Status |
|---|---|---|---|
| 1 | Field soak ≥ 30 days | Ops / pilot team | In progress — started 2026-06-29 (.spanda/field-soak-start.txt) |
| 2 | Third-party security audit sign-off | Security | Open |
| 3 | RB-007 closed or explicitly accepted in release notes | Maintainers | Open |
| 4 | Open P0/P1 release blockers | Engineering | Met (v0.6.3) |
| 5 | CI Fast + Integration green on main |
CI | Met — see ci-architecture.md |
| 6 | known-limitations.md matches shipped behavior | Docs | Met |
| 7 | Native codegen / device pool / RBAC promotion criteria (code) | Engineering | Partial — see ROADMAP.md v1.0 table |
When rows 1–3 and 7 code items are satisfied, bump workspace with python3 scripts/bump_version.py
major, update CHANGELOG.md, and tag v1.0.0.
While soak and audit run, engineering follows the Next horizon priorities in ROADMAP.md under scope-control.md:
VSCE_PAT)Organizational gates and platform work proceed in parallel; v1.0 messaging waits on gates 1–2.