Selector-based click scripts break when Workday changes the browser UI. A charter an AI browser agent can execute should name business goals and evidence, not CSS paths.
Charter template
- Environment — Implementation / Sandbox / Preview (never imply Production proxy).
- Persona — Start Proxy as employee / manager / other unconstrained test user allowed by policy.
- Preconditions — app deployed (not only App Preview); test worker eligible for the process.
- Goal — “Submit time off for next Tuesday and see the event In Progress,” not “click div.xyz.”
- Readback — report, My Tasks, or business object fields that must match after the UI step.
- Stop conditions — security error, wrong tenant URL pattern, unexpected Production host.
Why Preview is called out
Workday documents App Preview differences (UTC-only, en-US-only, securityDomains ignored when disconnected, widgets that error). A charter that only passes in Preview is incomplete.
Honesty limit
Workday does not publish a standard “AI UI charter” format. This template exists so agents and humans share the same proof bar.