Project status
Public baseline
| Item | Current value |
|---|---|
| Product source | main@9281890f42772cc01b6b2b607fd93e31de64879b |
| Spec revision | V1-FROZEN-2026-08-01 |
| Verification date | 2026-08-07 |
| Public posture | V1 in development |
| Website authority | Reader-facing summary pinned to the source commit above |
The implementation-status source reports substantial local progress across protocol codecs, deterministic Shard Runtime behavior, RocksDB projections, scheduler state, payload reservation/commit, and typed outcome boundaries. Those entries are evidence for the named local scope only.
Remaining release blockers
The public site must continue to show these blockers:
- concrete pinned Kafka/Pulsar ingress and destination transports with authenticated non-persistence and publish evidence;
- production Oxia session, Owner Lease, checkpoint catalog, Recovery Pin, and activation CAS authority;
- external Object Store and Broker ownership/quiescence evidence;
- complete large-payload, quota, control reserve, Lane terminal-guard, and guarded GC orchestration;
- real-service integration, failure-cut, chaos, benchmark, soak, upgrade, and release-runbook evidence.
The V1 Design Audit is a cross-document audit view and the Implementation Status document is the current code/evidence view. Neither replaces the normative design or Registry. A release claim is valid only after the design's release artifact matrix and all release gates are complete.
Public reading path coverage
The public documentation now exposes the core decision path in separate pages:
- time and scheduling semantics:
deliverAt,actionAt,expireAt, Trusted UTC, Due, Claim, and Publish Admission; - command semantics: Command, message, receipt, Source Position, Shard Log, and ACK-after-sync;
- delivery mode and guarantee boundaries:
MANAGED,AUTO_FAST, at-least-once, andUNCERTAIN; - lifecycle operations: Schedule, Cancel, Reschedule, Query, and the Query Barrier;
- ownership and recovery: Source Assignment, Owner Lease, Activation Barrier, Lane readiness, checkpoint recovery, and guarded GC;
- payload and release operations: reserve/upload/attest/commit, durable SLO evidence, observability, and release gates.
These pages are reader-facing summaries pinned to the same source baseline above. The design document, Protocol Registry, ADRs, and implementation-status evidence remain authoritative for exact wire fields, preconditions, and release claims.
Website publication contract
Each page declares the product, source repository, full source commit, verification date, status, authority, and (for Delay pages) source paths. The website's docs:check gate verifies these fields against the Delay source lock and content map, checks that every Delay page is mapped, and validates the legacy redirect manifest. This is publication integrity evidence for the website; it does not replace the product repository's implementation or release gates.