Skip to content

Calibrate maturity claims: public stabilization status instead of 'production-ready' - #127

Merged
ivkan merged 1 commit into
mainfrom
docs/honest-maturity-status
Jul 27, 2026
Merged

Calibrate maturity claims: public stabilization status instead of 'production-ready'#127
ivkan merged 1 commit into
mainfrom
docs/honest-maturity-status

Conversation

@ivkan

@ivkan ivkan commented Jul 27, 2026

Copy link
Copy Markdown
Member

Summary

The README overclaimed relative to the project's own (public) stabilization program: "production-ready", "designed for production workloads". This PR replaces adjectives with receipts, turning honesty into a differentiator:

  • README: status block now points at the machine-checked INVARIANTS.md (durability claims mapped to enforcing tests, gaps marked NAKED on purpose), the crash-recovery proof harness, and the 72h endurance gate; the batched-fsync trade-off is named up front. "Production-ready" claims (intro + deployment section) re-worded to "stable for single-node workloads + here are the public gates".
  • docs site: the four migration guides' "production-ready in single-node mode" cells re-pointed to a new Stabilization Status section on the roadmap page (the rest of the site was already well-calibrated — "single-node stable today" everywhere).
  • No positioning change: H1/hero outcome-first framing untouched.

Docs-only; no code. Site auto-deploys on merge.

… of 'production-ready'

README overclaimed ('production-ready', 'designed for production workloads')
relative to the project's own public stabilization program. Replace the
adjectives with the receipts: INVARIANTS.md catalog, the crash-recovery proof
harness, and the 72h endurance gate, plus the documented batched-fsync
trade-off. Same calibration applied to the four migration guides'
'production-ready in single-node mode' cells; roadmap.mdx gains the
Stabilization Status section both link to.
@ivkan
ivkan merged commit 181723d into main Jul 27, 2026
8 checks passed
@ivkan
ivkan deleted the docs/honest-maturity-status branch July 27, 2026 13:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant