A green audit result is useful only if the rule can reject the defect it claims to detect. Test the rule on paired fixtures: one valid input and one defective input that differs in a single declared property. Freeze the expected classifications before running the rule, then count missed defects separately from valid inputs incorrectly rejected. A passing pair demonstrates a narrow distinction, not that a website is ready for every agent.
Sample tasks in distinct states, not just URLs. Start with page template, workflow complexity and inventory state, then reserve a task execution for every known combination whose outcome could differ. Use random URL selection for a different question, such as estimating a defined population measure under a suitable statistical design. A small random draw is not a substitute for deliberate coverage of a rare, consequential state.
An agent audit should include every state that changes the correct response to the chosen task, the data that may be returned, or the side effects that are allowed. A successful check from a logged-in account with a populated cart cannot establish what should happen before consent, after logout, with an empty cart, or after a session expires. The task is the unit of work. The state inventory defines the conditions under which that work is judged.
Use the end-to-end task as the primary unit when an AgenticReadiness audit must establish whether a purchase can be completed correctly. Use page states to locate presentation gaps and tool contracts to locate input, output and state-change defects. Those units answer different questions. Averaging them into one pass rate can hide the boundary where the intended purchase changes.
An annual research review should show which decisions became better supported, which findings remain comparable, and where the evidence still runs out. A list of published articles or a rising dashboard line cannot answer those questions. The useful unit is a research question linked to a method, retained observations and a bounded conclusion.
A ScaleGrowth capability dossier should connect each claim to a dated record and state what that record establishes. Books can establish authorship and published methods. Service pages can describe an offer. Neither is a substitute for a demonstration with a checked result. The useful output is a claim-level proof packet, not a collection of endorsements.
Choose the format by the claim the evidence can sustain. A research feature explains a finding and how it was established. A founder interview examines decisions through answers that have actually been obtained. A technical byline teaches a method with enough detail to assess or apply it. A document can be useful in all three without being sufficient for any external pitch.
A worthwhile public relations (PR) placement puts a defensible story on a relevant page under terms that match the purpose of the work. A publisher’s logo cannot establish who will write that page, whether it will be advertising, how readers will find it or what the buyer can reuse. Choose only after those questions have page-level answers. Hold the decision when a missing term could change the value.
A first-to-build claim needs more than an early announcement. It needs a defined category, a dated working implementation and a comparison with alternatives that existed at the relevant time. An early record can establish that a system existed by a date. Only the comparison can establish whether that date precedes other qualifying systems, within the market actually examined.
A failed readiness test becomes useful when another person can reconstruct the expected task, reproduce the wrong result and see what evidence would change the conclusion. The record below reports a real local execution of a deliberately faulty lookup against fictional stock data. It demonstrates a testing method, not a defect discovered in a live business or a measurement of agent performance.