Evidence-driven, not version-number driven.

Near-term work is prioritized by real integration failure modes, interoperability evidence and security/reliability gaps.

Near-term priorities

1. Effect coverage: reviewed Effect Profiles requested by real workflows.
2. MCP/adapters: compatibility fixtures from independent clients/servers and current protocol evolution.
3. Failure recovery: more response-loss, delayed-effect, concurrency and stale-state scenarios.
4. External review: independent security/compatibility findings when usage is mature enough to make review meaningful.
5. Release verification: public provenance, SBOM, hosted controls and reproducible artifact evidence.
6. Ergonomics: shorter time to first protected action and clearer diagnostics for missing effect semantics/bypass paths.

1.0 is an evidence threshold

1.0 requires stable public contracts, externally verifiable releases, mature compatibility/conformance, independent security review, documented production recovery and meaningful external integrations. No date is promised.