Skip to content

docs: make the Rust rationale public-focused - #144

Merged
Fail-Safe merged 1 commit into
mainfrom
docs/public-why-rust
Aug 18, 2026
Merged

docs: make the Rust rationale public-focused#144
Fail-Safe merged 1 commit into
mainfrom
docs/public-why-rust

Conversation

@Fail-Safe

Copy link
Copy Markdown
Owner

Summary

  • refocus docs/why-rust.md on the public decision, measured evidence, limitations, and user-relevant tradeoffs
  • move chart regeneration, evidence lifecycle guidance, operational cautions, and open qualification work into a maintainer document
  • update the release-readiness language to reflect the completed v0.20.0 cutover

Impact

The Noema website can link readers to a stable public explanation without exposing an inline maintenance checklist. Maintainers retain the procedures and outstanding qualification work in a dedicated guide.

Validation

  • make test
  • git diff --check
  • verified all local links in both changed Markdown files

@Fail-Safe
Fail-Safe merged commit 0057f1d into main Aug 18, 2026
2 checks passed
@Fail-Safe
Fail-Safe deleted the docs/public-why-rust branch August 18, 2026 22:58
Fail-Safe added a commit that referenced this pull request Aug 19, 2026
* fix(release): authenticate Homebrew tap pushes (#143)

* docs: separate public Rust rationale from maintenance (#144)

* feat(tags): add cortex-wide tag management
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