Safety-Critical Rust Coding Guidelines: each guideline now renders as a standalone page, plus improvements to RST warning order, label handling, and FLS audit triage. For the page layout change, check this PR:
github.com/rustfoundati...
@safetycriticalrust.bsky.social
https://arewesafetycriticalyet.org/
Safety-Critical Rust Coding Guidelines: each guideline now renders as a standalone page, plus improvements to RST warning order, label handling, and FLS audit triage. For the page layout change, check this PR:
github.com/rustfoundati...
Consortium repo: we clarified the tools change flow (vendor contact now after PR creation), added the AbsInt aiT WCET Analyzer tool entry, and refreshed subcommittee rosters. If you want details, check this PR:
github.com/rustfoundati...
January 2026 SCRC recap: across the consortium, coding guidelines, and RFCs repos we merged 21 PRs and closed 18 issues. The coding guidelines repo shipped prereleases 0.1.19-0.1.21.
(more below)
Did you know that: The Coding Guidelines Subcommittee rotates their meeting to make it easier for regions to join?
- Americas + Europe-friendly
- Europe + Asia-Pacific-friendly
- Asia-Pacific + Americas-friendly
If you're located in Asia-Pacific we'd love to have you!
bsky.app/profile/safe...
If you'd like to get involved, it's easy!
bsky.app/profile/safe...
Tooling Subcommittee members have done a great job in standing up a process.
Check it out if you're a tooling vendor, run an open source project, or know of some tool which could be useful in safety-critical systems development when using Rust:
arewesafetycriticalyet.org/tooling/rfc-...
Screenshot of Tiago adding AbsInt tooling to the listing the Safety-Critical Rust Consortium's Tooling Subcommittee curates
Does your company produce tooling in the safety-critical space? Can it be used with Rust?
We'd love to hear from you!
Today we had a representative from AbsInt describe how tooling works on Rust software. It operates at the binary level. (beep boop)
More on how to get involved below
Make sure to consult the following table and always check with your Dungeon Master or Game Master for any homebrew rules when employing Safety-Critical Rust! ‡
12.01.2026 16:33 β π 4 π 2 π¬ 0 π 0many 20 sided dice, orange in color, with a safety-critical rust consortium logo
zoomed in view of a 20-sided dice, orange in color, with a safety-critical rust consortium logo
The Safety-Critical Dice have arrived! π²
As a Consortium member put it: "we put the safety-critical logo on the critical miss side to keep you safe!"
We hope to be able to hand them out at Rust conferences this year.
You can submit the application in parallel to join one of our subcommittees!
- Coding Guidelines
- Liaison
- Tooling
Click here to do so:
github.com/rustfoundati...
Curious about joining the Safety-Critical Rust Consortium?
It's as easy as submitting a GitHub issue:
github.com/rustfoundati...
You can then join a subcommittee of interest:
- coding guidelines
- liaison
- tooling
By submitting an issue here:
github.com/rustfoundati...
If you're interested in joining the Safety-Critical Rust Consortium, submit an issue here:
github.com/rustfoundati...
And here's the coding guidelines repo:
github.com/rustfoundati...
There's some other recent updates that we'll share soon!
For now if you'd like to check out the deployed version, here's a link to the Expressions chapter:
coding-guidelines.arewesafetycriticalyet.org/coding-guide...
Showing the Miri button, a microscope
The result of clicking the Miri / microscope button
Miri can be run on any example code block so annotated with the `:miri:` option.
Plus, now any code block which includes `unsafe` will fail the build unless `:miri:` is attached with an attestation that either:
- UB should not happen (`:miri:`)
- UB should happen (`:miri: expect_ub`)
Clicking copy button also copies any hidden source code
Shows pasted code has hidden bits and compiles
It was important for us to have fully compilable code available in the examples so that if copied, we'd provide something copy-pasteable easily into the Rust Playground or your own project to begin with.
25.12.2025 21:14 β π 1 π 0 π¬ 1 π 0Showing hidden lines
Hiding hidden lines
We've ensured that each code block is buildable and builds without warnings, adding this check into CI to ensure that remains the case.
Note here that we've got a hidden `fn main() {}` here that we can toggle between hidden and not.
The Little Book of Rust Macros by @lukaswirth.dev was a large inspiration, check out how beautiful this is:
lukaswirth.dev/tlborm/decl-...
Screenshot showing the four buttons now available on Rust code example blocks: copy, run, miri, and hide/unhide toggle
Screenshot showing the result of clicking the run button
We've brought some requested improvements to the coding guideline example code blocks:
- copyable
- buildable, runnable
- when annotated, Miri can be run
- hide/unhide less key portions
Hey folks π the survey closes tomorrow, so be sure to get your thoughts in regarding "what it would take" to make Rust more suitable to your safety-critical industry and business!
18.12.2025 14:09 β π 2 π 1 π¬ 0 π 0Do you know of a tool that'd be a good fit?
Here's the GitHub issue template to submit a tool:
github.com/rustfoundati...
First off, here's a link to the process:
arewesafetycriticalyet.org/tooling/rfc-...
Part of flowchart describing how tools can be added to Tooling Subcommittee's review and purview for use in safety-critical software development processes
Did you know that the Tooling Subcommittee has put together a process for submitting tools which are or potentially could be used for safety-critical systems development in Rust?
More details follow
We'll probably see the work done by early next week leaning towards one guideline per page, unless folks speak up otherwise π
16.12.2025 15:58 β π 0 π 0 π¬ 0 π 0So far three in favor of one guideline per page, so if you've got other thoughts, weigh in!
16.12.2025 15:58 β π 0 π 0 π¬ 1 π 0Here's where we're gonna discuss this:
github.com/rustfoundati...
Now that we've gotten each guideline into its own source file to help with reducing merge conflicts, should we:
1. have the rendered version as it is today, with all guidelines in a chapter?
2. have the rendered version with a flat list in the chapter, linking out to one guideline per rendered page?
Step two's attending meetings for some area of interest:
- Coding Guidelines
- Liaison
- Tooling
That's also easy:
github.com/rustfoundati...
Interested in observing progress? Getting involved?
Step one's joining the Safety-Critical Rust Consortium:
github.com/rustfoundati...