---
title: "#formal-methods articles | Hashnode"
description: "Explore 5 articles tagged #formal-methods on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/formal-methods"
---

Tag

# #formal-methods

5 posts · 0 followers

[Mayckon Giovani](https://hashnode.com/@mayckongiovani) · [Jul 7](https://hashnode.com/posts/protocol-core-101-most-systems-are-never-actually-specified/6a4d2ebd4443103c3614f20e)

### [Protocol Core 101 — Most Systems Are Never Actually Specified](https://protocol101.hashnode.dev/protocol-core-101-most-systems-are-never-actually-specified?utm_source=hashnode&utm_medium=feed)

Correctness cannot be derived from implementation. It requires a specification that exists independently of the code that realizes it.

4 min read · [protocol101.hashnode.dev](https://protocol101.hashnode.dev/protocol-core-101-most-systems-are-never-actually-specified?utm_source=hashnode&utm_medium=feed)

[Yves Eychenne](https://hashnode.com/@yeychenne) · [Jun 23](https://hashnode.com/posts/trains-formally-verified/6a3aa9cc2e89fe2c3d1b6be8)

### [I reimplemented a CAP-aware total-order broadcast protocol in Rust and verified it seven ways](https://yeychenne.hashnode.dev/trains-formally-verified?utm_source=hashnode&utm_medium=feed)

I co-invented a total-order broadcast protocol in the 1990s for power-plant control. I rebuilt it in Rust, checked it seven ways, and a model checker found a bug I'd shipped 30 years ago.

10 min read · [yeychenne.hashnode.dev](https://yeychenne.hashnode.dev/trains-formally-verified?utm_source=hashnode&utm_medium=feed)

[Mayckon Giovani](https://hashnode.com/@mayckongiovani) · [May 26](https://hashnode.com/posts/protocol-core-101-bugs-are-not-exceptions/6a15c933da253d50d4cb0cc6)

### [Protocol Core 101 — Bugs Are Not Exceptions](https://protocol101.hashnode.dev/protocol-core-101-bugs-are-not-exceptions?utm_source=hashnode&utm_medium=feed)

Failures are rarely anomalous events. They are usually valid state trajectories the system was never designed to exclude.

4 min read · [protocol101.hashnode.dev](https://protocol101.hashnode.dev/protocol-core-101-bugs-are-not-exceptions?utm_source=hashnode&utm_medium=feed)

[Christo Zietsman](https://hashnode.com/@nuphirho) · [Mar 22](https://hashnode.com/posts/specification-as-quality-gate-three-hypotheses/69c0707b35159a786e710ee7)

### [The Specification as Quality Gate: Three Hypotheses on AI-Assisted Code Review](https://nuphirho.hashnode.dev/specification-as-quality-gate-three-hypotheses?utm_source=hashnode&utm_medium=feed)

This is Part 4 of a four-part series, "The Specification as Quality Gate." Part 1 developed the correlated error hypothesis. Part 2 grounded the argument in complexity science. Part 3 mapped what specifications cannot catch. This post is the complete...

28 min read · [nuphirho.hashnode.dev](https://nuphirho.hashnode.dev/specification-as-quality-gate-three-hypotheses?utm_source=hashnode&utm_medium=feed)

[Christo Zietsman](https://hashnode.com/@nuphirho) · [Mar 22](https://hashnode.com/posts/what-specifications-cannot-catch-residual-defect-taxonomy/69c06c0274703d9312fa25e0)

### [What Specifications Cannot Catch: A Proposed Taxonomy of the Residual](https://nuphirho.hashnode.dev/what-specifications-cannot-catch-residual-defect-taxonomy?utm_source=hashnode&utm_medium=feed)

This is Part 3 of a four-part series, "The Specification as Quality Gate." Part 1 developed the correlated error hypothesis. Part 2 grounded the argument in complexity science. This post maps what executable specifications cannot catch. Part 4 will f...

11 min read · [nuphirho.hashnode.dev](https://nuphirho.hashnode.dev/what-specifications-cannot-catch-residual-defect-taxonomy?utm_source=hashnode&utm_medium=feed)
