Misleading "production-ready" claim contradicts v0.1.0 semver #13
Description
The Problem
The landing page prominently claims "Production-grade", but the project is at v0.1.0.
These two things are fundamentally incompatible with semver conventions and software industry norms.
Why This Matters
Semver 0.x.x explicitly means unstable.
From the semver spec:
"Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable."
Calling a 0.1.0 release "production-ready" directly contradicts this.
The scale of the claims raises further questions.
137,000 lines of Rust, 14 crates, 16 security systems, 40 channel adapters - all released as v0.1.0 with no prior public history or staged rollout. Production-grade Rust projects like tokio, axum, and sqlx took years of real-world iteration and community hardening before earning that label.
Security claims without evidence are dangerous.
The project advertises 16 security layers, including WASM sandboxing, taint tracking, Merkle audit trails, prompt-injection scanning, and more. These are serious claims. Has any of this been independently audited? Users who deploy this in real environments based on "production-ready" marketing are taking on unverified risk.
Suggestion
Please consider one of the following:
- Remove the "production-ready" label until the project reaches a stable API (v1.0+) with real-world battle testing.
- Replace it with something honest like "alpha", "experimental", or "early access".
- If you genuinely believe it is production-ready, back it up - publish a security audit, test coverage reports, and real-world deployment examples.
Honest versioning builds trust. Overclaiming erodes it.