Do real work.
The agent reaches APIs, local processes, and browser interfaces inside a recorded workspace.

rote turns a successful execution trace into an inspectable, versioned Play that another permitted agent can run with fresh inputs.
An agent can reason well, choose the right tools, recover from errors, and finish a task. When the session ends, the result usually remains but the useful path does not. The next run pays to rediscover the same method and may repeat the same mistakes.
The reusable object is a typed execution contract, not a larger memory dump.
The agent reaches APIs, local processes, and browser interfaces inside a recorded workspace.
Each useful response becomes an immutable, queryable workspace artifact instead of disappearing into chat.
rote turns the successful trace into typed inputs, declared steps, dependencies, effects, and presentation.
Another permitted agent invokes the Play URI and follows the preserved method with fresh inputs.
A Play declares parameters, tools, services, authentication, privileged requirements, effects, steps, dependencies, ownership, visibility, and version. It can render an honest human report, concise summary, or canonical JSON result.
The method does not depend on prose alone.
A skill guides reasoning; a Play preserves a specific executable method.
Inputs, effects, evidence, presentation, ownership, visibility, and versions stay attached.
rote is a portable method layer for existing agents and harnesses.