Prove it, don't test-and-hope. Use for concurrent or distributed code with no written spec, "how do we know this is correct?", interfaces that break when implementations are swapped, correctness argued by walking through example traces, wall-clock time used for ordering, or "can this be decided at all?".
mdr add cdeust/zetetic-team-subagents/formal-correctness@git:20260805.e8cc65emdr add cdeust/zetetic-team-subagents/formal-correctness@sha256:dab70955b737ab3c[](https://markdownregistry.com/a/art_frnfaj3vkcvhz3pf)
0 badge views in 30 days
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260805.e8cc65e latest | 2026-08-05 | e8cc65e | 2,962 B | A | view · diff |
| git:20260722.b89f9c1 | 2026-07-22 | b89f9c1 | 2,933 B | A | view |
cdeust/zetetic-team-subagents · 7 stars · license MIT · pushed 2026-09-05 · branch main
GET https://markdownregistry.com/api/v1/artifacts/art_frnfaj3vkcvhz3pf GET https://markdownregistry.com/api/v1/resolve?ref=cdeust/zetetic-team-subagents/formal-correctness GET https://markdownregistry.com/api/v1/blob/dab70955b737ab3cf71d30c4c97f7942175065b66a052c41ee46138158207efd