Project status
Current posture
| Item | Current value |
|---|---|
| Spec revision | V1-FROZEN-2026-08-13 |
| Product status | V1 complete |
| Validation | All ten V1 release gates passed |
| Next phase | Optimization, refactoring, review, and further evolution |
V1 is no longer waiting on implementation closure. It includes the Direct SDK and optional Gateway entry paths, Kafka and Pulsar sources and destinations, durable Shard state, scheduling, recovery, large payloads, control operations, observability, and guarded delivery evidence.
V1 validation coverage
The completed validation matrix covers:
- protocol and golden-vector compatibility;
- correctness, no-early delivery, and chaos failure cuts;
- real Kafka, Pulsar, Oxia, Worker, Gateway, and Object Store integration;
- benchmark and physical-capacity envelopes;
- soak, upgrade, and downgrade behavior;
- restore, fencing, DLQ replay, uncertainty resolution, and operational drills;
- guarded Kafka and Pulsar client distribution and resource-recreation cuts.
What comes after V1
Follow-on work belongs to continuing engineering:
- performance and resource optimization;
- implementation simplification and refactoring;
- code, design, security, and operational review;
- usability, tooling, diagnostics, and documentation improvements;
- future protocol or product evolution under an explicit new revision when semantics change.
These activities improve V1 without being unresolved V1 release blockers. A behavior-changing update must use an explicit new revision and rerun the affected validation gates.
Completion boundary
V1 complete means the product contract, implementation, and registered release matrix are closed. It does not mean:
- every deployment environment is automatically approved for production;
- later behavior-changing releases inherit validation without rerunning affected gates;
- the system promises capabilities listed as V1 non-goals.