Tracked artifact
Tracked website source implements the causal story, visitor takeover and resume, desktop and mobile layouts, and two finished outcomes.
A causal demo moves from Lobby orientation through Workday setup, three sources of work, board progression, presentation and email outcomes, Workforce depth, Settings, and a safe visitor takeover.

Tracked website source implements the causal story, visitor takeover and resume, desktop and mobile layouts, and two finished outcomes.
A browser runtime returned 200, completed the 23-chapter desktop story, rendered at 390 by 844 without overflow, and recorded zero console errors.
The source task passed its completion gate and remains in human review.
This proves the staged website demo. It does not prove a real customer Workday, a current installed extension payload, or publication of this proof page.
Define the finished artifact and the one operating sequence a visitor must understand.
Use fictional identity and deterministic workspace data while keeping the visible mechanics faithful.
Move through direction, work generation, review progression, outputs, workforce context, and controls.
Pause on genuine input and provide one explicit resume path without discarding progress.
Capture desktop and mobile states, verify no overflow, and reject console errors and private identity tokens.
Use a fictional operator and studio. Move from Lobby orientation to a deadline, focus, Workday, three sources of work, review, finished outputs, and safe visitor takeover. Exclude customer data, account state, and live dispatch.
The proof ID and verified-Workday intent stay attached to the activation path.