Knowledge baseAnswers
Glossary
The words this documentation uses, defined once.
| Term | Meaning |
|---|---|
| Activation | Moving a routine from draft to active. Requires a successful manual run of the current configuration. |
| API key | A project-scoped bearer credential, wor_<prefix>_<secret>, shown once and stored only as a SHA-256 hash. |
| Automatic execution | The second grant on a tool policy: permission for an enabled tool to be called while nobody is watching. |
| Connection | A configured MCP server and its encrypted authentication metadata, owned by a project. |
| Delivery | One persisted webhook event with its attempt count, response codes, and state. |
| Error category | The classification of a non-successful run: tool_denied, step_limit, gateway_timeout, and so on. |
| LLMGateway | The single directory and inference path for every model Work on Repeat can use. |
| Managed provider | GitHub, PostHog, or Zernio — connections Work on Repeat knows how to authenticate for you. |
| MCP | Model Context Protocol. Work on Repeat connects to Streamable HTTP MCP servers. |
| Operations tick | The one-minute job that claims due routines, executes queued runs, and retries due webhook deliveries. |
| Organization | Billing-level identity and membership. Owns projects; members are owner, admin, or member. |
| Project | The unit of isolation. Owns routines, runs, connections, and API keys. |
| Proof run | The successful manual run that unlocks activation, and that any material change invalidates. |
| Routine | A recurring responsibility: instructions, model, schedule, variables, limits, tools, and delivery settings. |
| Run | One manual, API, or scheduled execution of a routine. |
| Scope | A capability on an API key, such as runs:write. Sessions are not scope-limited; keys always are. |
| Self-managed server | Any Streamable HTTP MCP server you register yourself with a URL and optional encrypted headers. |
| Step | One entry in a run trace: model, tool_call, tool_result, or error. |
| Tool policy | The per-routine record of which tools from a connection may be used, and which may run automatically. |
| Trace | The ordered, redacted record of everything a run did. |
| Trigger | How a run started: manual, api, or schedule. |
| Variable | A key-value pair substituted into {{placeholders}} in the instructions before each run. |
| Webhook secret | The per-routine HMAC signing key, returned once and stored encrypted. |