From 11038cf5429eeb7a3f35134fcb38752571b072fd Mon Sep 17 00:00:00 2001 From: Ralf Anton Beier Date: Mon, 27 Apr 2026 20:53:35 +0200 Subject: [PATCH] content(overdoing): name witness as the cell-filler + add 11th matrix column MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Per advisor's recommendation: ship this post with witness named in it before doing anything else on either the post or the tool. The post is the carrier wave; witness is what people click through to once they understand why the cell was empty. Three concrete changes: - Add gloss bullet for "Structural coverage (Wasm IR)" naming witness with a link to github.com/pulseengine/witness, framed as the cell-filler for the §FM.6.7(f) / MC/DC-shaped slot that source-level lcov has long pretended to satisfy across DO-178C, ISO 26262, IEC 61508 - Add 11th column "Struct. coverage" to the credit matrix (between Mutation testing and Trace-ability) - Fill the column: strong dot for DO-178C, ISO 26262, IEC 61508; the other four standards (EN 50128, IEC 62304, ECSS-Q-ST-80C, IEC 60880) have deliberately-empty fit-na cells with title="not yet mapped — credit-template work is the next post's hook" The empty cells are intentional — they mark the credit-template gap honestly and give the next post a hook. Tooltips on hover clarify the "not yet mapped" framing vs. the existing "standard silent" use of fit-na (which the legend still describes; the overload is small enough to leave alone for now). Date and draft flag unchanged: still scheduled for auto-publish on 2026-04-29. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../blog/2026-04-22-overdoing-the-verification-chain.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/content/blog/2026-04-22-overdoing-the-verification-chain.md b/content/blog/2026-04-22-overdoing-the-verification-chain.md index cd40875..85ea377 100644 --- a/content/blog/2026-04-22-overdoing-the-verification-chain.md +++ b/content/blog/2026-04-22-overdoing-the-verification-chain.md @@ -148,6 +148,7 @@ A one-line gloss for each technique in the matrix below — skip if these read l - **tokio-rs/loom** — permutation-checks every possible thread interleaving in a bounded concurrent program. - **Sanitizer · Miri** — runtime instrumentation that detects undefined behaviour, memory errors, and data races (ASAN, TSAN, LSAN, UBSAN, Miri). - **Mutation testing** — inject small plausible bugs into the source and check whether the test suite catches them; empirical test-suite adequacy. +- **Structural coverage (Wasm IR)** — branch / MC/DC coverage measured on the post-compile WebAssembly module rather than at source. Closes the §FM.6.7(f) / MC/DC-shaped cell that source-level lcov has long pretended to satisfy across DO-178C, ISO 26262, IEC 61508. Shipping as [witness](https://github.com/pulseengine/witness); the credit-template work for the other four standards is the next post's hook. - **Traceability** — requirement ↔ design ↔ code ↔ test ↔ proof chain, validated on every commit (rivet). At a glance, all seven domains against the core chain techniques: @@ -166,6 +167,7 @@ At a glance, all seven domains against the core chain techniques: tokio-rs
loom Sanitizer
 · Miri Mutation
testing + Struct.
coverage Trace-
ability @@ -181,6 +183,7 @@ At a glance, all seven domains against the core chain techniques: ● ● ● + ● ● @@ -194,6 +197,7 @@ At a glance, all seven domains against the core chain techniques: ◐ ● ◐ + ● ● @@ -207,6 +211,7 @@ At a glance, all seven domains against the core chain techniques: ● ● ● + ● ● @@ -220,6 +225,7 @@ At a glance, all seven domains against the core chain techniques: ● ● ● + ● @@ -233,6 +239,7 @@ At a glance, all seven domains against the core chain techniques: ◐ ● ● + ● @@ -246,6 +253,7 @@ At a glance, all seven domains against the core chain techniques: ◐ ● ◐ + ◐ @@ -259,6 +267,7 @@ At a glance, all seven domains against the core chain techniques: ◐ ◐ ◐ + ◐