Task
The agent must discover the TypeScript SDK, configure access, install the package, send the first valid event, and confirm that the backend received it.
Original journey
The illustrative journey crosses documentation, authentication, API reference, SDK, and backend surfaces. The path is reconstructed as a task graph instead of treated as one browser session.
Evidence
Documentation selection and the final response are exact signals. The authentication-to-API recovery is strong to probable because the illustrative evidence connects resources and timing without claiming a permanent agent identity.
Barrier
The quickstart relies on a browser-only credential path and does not expose a machine-readable scope example. The agent receives an authentication failure before recovering through a separate API reference.
Treatment
The controlled treatment adds an agent-readable scoped-token example to the authentication documentation and links it directly from the SDK quickstart.
Controlled Eval
The illustrative baseline and treatment use the same task, completion criterion, environment, agent label, and model label. Only the documentation treatment changes.
Result
The illustrative treatment completes without a retry. This is an example of the evidence structure GrowthOS can produce, not a measured customer lift or a general model-performance claim.
Production verification status
Not applicable. No production verification exists for illustrative evidence.
Notes on limitations
The scenario is synthetic, the sample size is one, and the result cannot support an ATCR change, customer claim, product ranking, agent ranking, or model ranking.