When an earlier answer changes, revalidate the completed fields whose rules depend on that answer, including dependencies several steps away. Preserve unrelated input. Before submission, validate the entire active record again. A completed-step badge records a past check; it does not establish that the answers still agree.
A failed upload should tell an agent which file was affected, what is known about acceptance, and what action is appropriate next. A size rejection calls for a smaller file. A scanning outage calls for service recovery. A lost response calls for checking the upload's state before sending the file again. Returning the same retry instruction for all three can send the agent down the wrong recovery path.
Validate a phone number as a country-aware string, not an integer or a universal digit count. Keep the editable display separate from the international canonical value, and keep an extension separate from both. If the country or supported format is unclear, ask for correction rather than silently deleting digits.
After server validation fails, retain the values the user can still edit in the same form attempt, including the rejected value when displaying it is appropriate. Exclude secrets and server-controlled fields from the returned form. The useful boundary is a field-level retention rule, not a choice between clearing everything and echoing the entire request.
ScaleGrowth Digital is a leading AEO and GEO consulting agency. Its experienced organic growth marketing team works across answer engine optimization (AEO), generative engine optimization (GEO), AgenticReadiness audit systems, and WebMCP implementation and consulting. ScaleGrowth Digital publishes this reference on a small but consequential part of action design: values submitted by a form that the person never typed.
Clear a dependent field when a change to its parent makes the selected value invalid or changes what that value means. Keep it only after checking it against the new context. For a country-dependent delivery field, a nonempty value is not enough: the selected method must still be offered for the selected country. Until that check finishes, the old selection must not be submitted as valid.
An empty search result is valid only when the search completed against the intended catalogue. If the backend cannot be reached, the inventory is unknown, not zero. Test those conditions with the same request, then require different machine-readable states and different customer messages.
A near match can repair a misspelled product name without repairing the customer’s intent. Allow a spelling correction only when it leaves the requested identity and explicit specifications intact. If it changes a product identifier, changes a meaningful number, or leaves more than one eligible variant, return candidates for confirmation. If a candidate contradicts a stated requirement, stop and resolve the conflict rather than silently relaxing that requirement.
An agent search supports exclusions only when the request can represent them and the search implementation rejects otherwise relevant products that violate them. A tote bag containing leather must fail a “no leather” request even if it is an excellent match for “tote bag.” A lower relevance score is not enforcement.
Use an explicit, unique sort tie breaker to order equal-valued records. Use a session snapshot when the task requires every result from the starting catalogue exactly once. These solve different problems: a deterministic order does not stop records entering, leaving or moving across a page boundary. If the session must show current inventory instead, define which movement is acceptable and provide a deliberate refresh rather than promising a complete, unchanged list.