The Power of 10 Rules were created in 2006 by Gerard J. Holzmann of the NASA/JPL Laboratory for Reliable Software.[1] The rules are intended to eliminate certain C coding practices that make code difficult to review or statically analyze. These rules are a complement to the MISRA C guidelines and have been incorporated into the greater set of JPL coding standards.[2]
Developer Ecosystems for Software Safety
How to design and implement information systems so they are safe and secure is a complex topic. Both high-level design principles and implementation guidance for software safety and security are well established and broadly accepted. For example, Jerome Saltzer and Michael Schroeder’s seminal overview of principles of secure design was published almost 50 years ago,10 and various community and governmental bodies have published comprehensive best practices about how to avoid common software weaknesses—for example, Common Weakness Enumeration (CWE)a and Open Worldwide Application Security Project (OWASP) Cheat Sheet Series.b
The Rule of Least Power
This document is also available in these non-normative formats: XML.
Introducing gpt-oss-safeguard
OpenAI introduces gpt-oss-safeguard—open-weight reasoning models for safety classification that let developers apply and iterate on custom policies.
Code Worth Writing - Ray Myers | SSW 2026
Write code that is easy to delete, not easy to extend.
“Every line of code is written without reason, maintained out of weakness, and deleted by chance” Jean-Paul Sartre’s Programming in ANSI C.
Open by Design: ROOST's Approach to Safety Tool Development
Tailoring Legal Protection for Computer Software
Peter S. Menell, Tailoring Legal Protection for Computer Software, Stanford Law Review, Vol. 39, No. 6 (Jul., 1987), pp. 1329-1372
Reports of code's death are greatly exaggerated
A sufficiently detailed spec is code begins with this lovely comic:
roostorg/osprey
Automate the obvious and investigate the ambiguous. High-performance safety rules engine for real-time event processing at scale.
A sufficiently detailed spec is code
Specifications do not address the limitations of agentic coding
Lessons from the hacks
Musings on model alignment, what determines safety, and where we go from here.
Computational Law
RaC, rules as code, legislation as code, automated decision making, papers, resources, disasters, people
Legislation as Code | Version: 2
Governing Digital Legal Systems: Insights on Artificial Intelligence and Rules as Code · MIT Computational Law Report
Hamish Fraser
