Going to be at @rustconf.com 2026? Interested in safety-critical systems like Automotive and Avionics? 🦀🦺 We'll be at RustConf 2026 with a Safety-Critical Rust Consortium Room! Big thank you to @adacore.bsky.social for sponsoring the room 🎉 Check below on how to join!

Want to extend heartfelt gratitude to - @rustnl.bsky.social for hosting the Safety-Critical Rust Consortium at the RustWeek Unconf - @ferroussystems.bsky.social for sponsoring the SCRC room And of course -- to our members for coming out and making sparks fly with ideas!

Hey folks, here's the Safety-Critical Rust Consortium's March 2026 Newsletter Key highlights: - RustWeek 2026 SCRC room secured, thank you to @ferroussystems.bsky.social for sponsoring it - CERT C => Rust mapping got major reviews - ISO 26262 + Rust readiness analysis ready (more follow in-thread)

Hey folks 👋 February newsletter coming out a bit late, but better than never! Highlights: - baseline SCRC RFC got merged - increased stability and review guidance for coding guidelines - the Safety-Critical Rust roadmap was accepted into the Rust Project Goals

Shout out to Stefan Akatyschew for the work he did on mapping out how ready Rust is for Automotive! (ISO 26262)

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...

Safety-Critical Rust Consortium@safetycriticalrust.bsky.social · 7mo ago

Curious about joining the Safety-Critical Rust Consortium? It's as easy as submitting a GitHub issue: github.com/rustfoundati...

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! ⤵

Safety-Critical Rust Consortium@safetycriticalrust.bsky.social · 7mo ago

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.

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.

Curious about joining the Safety-Critical Rust Consortium? It's as easy as submitting a GitHub issue: github.com/rustfoundati...

Build software better, together

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

github.com

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!

Safety-Critical Rust Consortium@safetycriticalrust.bsky.social · 8mo ago

Are you in a safety-critical industry? Using the Rust programming language (@rust-lang.org) or would like to? Make your voice heard when it comes to what you'd like to see for Rust Project Goals! (survey link below)

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

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?

We've improved the guidance on how to use the coding guideline that's been converted from Markdown to reStructuredText and -- we now test all code examples in the submitted guideline! More details follow.

A couple of significant upgrades to contributing to our coding guidelines: - all example code is now extracted and tested - each guideline exists as its own source file These both fall under our contributor experience label and we take these seriously. Writing a bit more about this below

Howdy y'all 👋 reminder that our survey of safety-critical Rust users for potential Project Goals in 2026 ends next Friday Check the quoted post for more details! bsky.app/profile/safe...

Safety-Critical Rust Consortium@safetycriticalrust.bsky.social · 8mo ago

Are you in a safety-critical industry? Using the Rust programming language (@rust-lang.org) or would like to? Make your voice heard when it comes to what you'd like to see for Rust Project Goals! (survey link below)

Are you in a safety-critical industry? Using the Rust programming language (@rust-lang.org) or would like to? Make your voice heard when it comes to what you'd like to see for Rust Project Goals! (survey link below)

Hey there 👋 are you aware of the Safety-Critical Rust Consortium? 🦀🦺 We were founded about a year and a half ago with the mission to make Rust a first-class choice when starting a safety-critical systems project (think trains, planes and automobiles -- and more).