Trust layer
Risks, constraints, and operating honesty
DELIGHT should read as ambitious and serious, which means exposing fragility clearly instead of burying it.
Primary exposures
Platform / ToS exposure
Browser-based compute depends on external platforms, changing policies, and unstable assumptions.
Selector fragility
External UI changes can break prompt flow, parsing logic, or session warmup unexpectedly.
Routing correctness
Misclassification between local, browser, and future network routes can produce wrong execution paths.
Memory hygiene
Broken outputs, timeouts, and invalid responses should never become trusted long-term memory.
Current issues to acknowledge
- Task routing can still send some work into the wrong execution path.
- External UI selectors can break browser-based task execution.
- Warmup and session initialization flows can fail before prompt submission.
- Policy changes can alter browser-compute assumptions over time.
Mitigation principles
- Keep the public risks page explicit and current instead of hiding uncertainty.
- Separate protocol narrative from claims of guaranteed reliability or availability.
- Treat browser automation as fragile infrastructure that needs monitoring, maintenance, and fallback paths.
- Never persist empty, broken, timeout, or obviously invalid outputs as trusted memory.