Proof, Not Posture

Start with the state

An agentic claim should tell the reader whether the thing was observed, implemented but not production-wired, experimentally tried, documented as planned, recommended, failed, or deprecated.

Those labels are useful only when the evidence basis, date, source, boundaries, and known failures are visible.

An output is not an outcome

Generated text, a completed command, or model agreement does not establish acceptance. An accepted outcome meets the task's quality, evidence, authority, and owner or delegated acceptance requirements.

When deterministic checks exist, run them. Use independent model review for assumptions and failure modes, not as a substitute for tests.

Unavailable is valid

Do not invent traffic, cost savings, benchmark wins, Vitals, or user results to make a foundation look complete. A clear not-activated state is evidence of discipline.

Current claims about products, providers, prices, software, hardware, laws, or terms need fresh sources at publication time.

Correct visibly

Material corrections need a date, original-claim summary, corrected claim, reason, affected pages, and decision impact. Consequential errors should not disappear through silent edits.

The practical test

A reader should leave with a better decision, reusable pattern, concrete next step, clearer risk, or test they can run. If the evidence does not support the headline, reduce the claim rather than decorate the uncertainty.