saasmirrorA SOFTWARE FIELD GUIDE
← All field notes

RELEASE EVIDENCE

Check this vendor claim before you install

Quote the claim, name one install, and write the questions the page leaves open.

A public page published this account (2026-10-22): Claude generated ~180M lines of Rocq proving no-crash for 239 entry points across 123 OSS-Fuzz libs (RISC-V, inputs <64MB); bugs found and patched.

This guide uses that public page as the example. This site did not run the test, close the deal, or measure the product.

Write only what the page says

The page's claim is: Claude generated ~180M lines of Rocq proving no-crash for 239 entry points across 123 OSS-Fuzz libs (RISC-V, inputs <64MB); bugs found and patched.

Put the URL under that sentence. If a later recap adds a number or a date, keep the original page as the record.

Quote the claim, name one install, and write the questions the page leaves open.

Do the site's check on this one page. Fill a line only when the page supports it. Where the page is silent, write Not stated.

A finished note names the page, the date, and the limit of the claim. It does not borrow a result from a different story.

Stop at the untested line

Anything you did not open, install, or count stays untested. Leave that line visible.

Source page: Anthropic + Theorem: Claude formal verification of 123 OSS libraries at assembly level.

Source: Anthropic + Theorem: Claude formal verification of 123 OSS libraries at assembly level.