specformula-fork

Payload validation for agent workflow clarifications enforces option-count invariants, forbids free-text options, and requires location fields to ground fork questions in the graph. This prevents silent degradation and rejects legacy anchors when fields are missing.

Dispatch fork clarifications by building a fork question string and triggering the fork tool with located_file_type, located_file_path, and location. This applies during clarify-loop planning when a question requires 2-4 discrete options and a recommendation affecting downstream decisions.

Specification clarification payload validation fails because the invariants explicitly forbid OTHER and free_text options to ensure deterministic decisions. The route is marked incomplete to avoid silent degradation when option-count or location field requirements are violated.

Trigger a fork question during clarify-loop planning when an ambiguous specification requires 2-4 discrete options and a recommendation that affects downstream decisions. The fork tool uses verbatim readGraph anchors to dispatch the structured clarification deterministically.

This clarification approach does not support fuzzy location anchors. It rejects legacy and fuzzy anchors to keep the decision grounded in the graph, requiring exact graph anchors like located_file_path and location fields for valid payload validation.

Using other route types when the fork-route payload is missing required location fields causes fail-fast correctness guarantees to mark the route as incomplete. This avoids silent degradation to other routes and ensures the fork tool only triggers with valid graph anchors.