Dynamic Web Element Tool Protocol and Fallback Execution Spec

Role: Lead Reliability Engineer specializing in resilient web automation, DOM mutation recovery, and autonomous scraper tooling.

Context

• Target DOM layout patterns: {{target_dom_patterns}}
• Agent runtime reasoning model: {{llm_runtime_model}}
• Timeout and latency constraints: {{timeout_latency_limits}}
• Mutation detection heuristics: {{dom_mutation_heuristics}}
• Scraping and interaction rate limits: {{rate_limit_policy}}

Task

Create a dynamic element resolution and self-healing tool-calling specification that enables {{llm_runtime_model}} to reliably target and interact with shifting components in {{target_dom_patterns}}.

Method

1. Classify target UI elements across {{target_dom_patterns}} into structural, semantic, and accessibility locator hierarchies.
2. Specify primary CSS/XPath selector synthesis strategies alongside secondary accessibility-tree heuristics.
3. Define multi-layered fallback tiers when primary locators fail against {{dom_mutation_heuristics}}.
4. Create a standardized JSON payload structure for passing element bounding boxes, visibility states, and computed attributes to {{llm_runtime_model}}.
5. Establish strict execution time budgets adhering to {{timeout_latency_limits}} across all locator attempts.
6. Define rate-limiting throttle hooks to ensure tool call frequency complies with {{rate_limit_policy}}.
7. Formalize a self-healing patch protocol where newly resolved locators update the persistent selector cache.

Constraints

• MUST NOT rely solely on brittle static class names or auto-generated hashes (e.g., CSS modules).
• Element resolution cascades MUST abort and trigger fallback before exceeding {{timeout_latency_limits}}.
• Tool payloads MUST sanitize raw DOM fragments to minimize context window token consumption.
• The protocol MUST strictly throttle concurrent element lookups in compliance with {{rate_limit_policy}}.

Output format

• 1. Locator Cascade Architecture (ordered hierarchy from CSS to Accessibility to Vision)
• 2. Tool Interface Specification (JSON Schema for resolve_element, interact_element, and report_dom_mutation)
• 3. DOM Sanitization & Token Optimization Guidelines (filtering algorithms and size limits)
• 4. Self-Healing Selector Update Protocol (state transition logic for caching verified selectors)

Self-review

1. Does the locator cascade enforce strict timeout cutoffs matching {{timeout_latency_limits}}?
2. Are DOM payload structures optimized to prevent LLM context bloating?
3. Does the self-healing protocol clearly define when a selector cache entry must be invalidated?