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.

github.com published this account (2026-09-20): github.com/google/ax released tag v0.3.0. Visible release commit message is a workflow-permissions chore; same-day main commits include a restructure of AX into a general-purpose agent orchestration layer. Module published on pkg.go.dev Sep 20.

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: github.com/google/ax released tag v0.3.0. Visible release commit message is a workflow-permissions chore; same-day main commits include a restructure of AX into a general-purpose agent orchestration layer. Module published on pkg.go.dev Sep 20.

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: Google AX v0.3.0 tagged; pkg.go.dev published Sep 20, 2026.

Source: Google AX v0.3.0 tagged; pkg.go.dev published Sep 20, 2026.