Verification register Compute & Web Infra
Current reading
Readiness band and full integer triple
AI-assisted assembly · derived results
Readiness band
Watch
Primary summary from verified readiness
- Confidence
- 79% · fresh
- Computed at
- 2026-09-30T22:53:48.593838+00:00
- Claimed
- 65
- Reported
- 55
- Verified
- 35
- Gap
- +30
Public ambition and stated capability
Observed practitioner reporting
Independently supported evidence
Claimed leads verified
Evidence strength Growing
Decision
What the current evidence supports
Agent-assisted assessment · independently reviewed · 2026-09-30
Choose a supported Kafka release for new production deployments; keep 4.0.x only with an explicit maintenance arrangement and upgrade plan.
- Why
- Kafka 4.0 has demonstrated production capability, but every 4.0 release is archived and Apache provides bugfix releases only for supported versions.
- Next
- Plan migration to a supported release, rehearse recovery and metadata changes, and test transaction-heavy workloads under representative load.
Constraints
Blockers
- Every Kafka 4.0 release is archived and outside Apache's supported bugfix policy.
- ZooKeeper clusters require migration before upgrading to 4.0.
- Metadata finalization restricts downgrade options.
- Transaction-heavy workloads require dedicated performance testing.
- Kafka 4.0 share groups must remain disabled in production.
- Older patch levels contain consequential correctness defects.
- Java and removed API requirements may require application changes.
Evidence summary
Derived counts
AI-assisted assembly
- Total
- 9
- Tier 1
- 6
- Tier 2
- 3
- Tier 3
- 0
- Supports
- 4
- Contradicts
- 4
- Context
- 1
- Latest observed
- 2026-09-04
Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.
Publication record
Revisions
Revision 3
- 2026-07-27 Reading moved from mature to mature.
- 2026-09-22 Reading moved from mature to mature.
- 2026-09-30 Reading moved from mature to watch.