# Concepts ## Protege A **Protege** is a Hookshot™ automation. It describes what starts the workflow, what the workflow decides, and what result it should produce. ## Trigger source A **trigger source** is the live source of events that can start a Protege. ## Schedule A **schedule** is a time-based way to start a Protege instead of waiting for an external event. ## Trigger Access **Trigger Access** controls which connected sources are allowed to start a Protege. ## Tool Access **Tool Access** controls which actions a Protege can take after it starts. ## Setup blocker A **setup blocker** is anything that still prevents a Protege from being fully ready, such as a missing connection, missing trigger source, or missing required configuration. ## Event Feed The **Event Feed** shows incoming events and how Hookshot responded to them. ## Audit **Audit** shows Protege run history and outcomes so you can confirm what happened. Audit includes fleet-wide runs, Protege-specific history, run detail timelines, tool usage, logs, teaching notes, and analytics. ## Run A **run** is one execution of a Protege. Runs can be **standard** (event or schedule triggered) or **chat** (triggered by a conversation mention). Run statuses include `queued`, `running`, `success`, `failure`, and `dead_letter`. ## Outcome An **outcome** is the result of a run. It is the answer to “what happened after the Protege ran?” ## Dispatching In the Event Feed, **dispatching** means Hookshot is still working through the event and the final run state is not ready yet. ## Skipped In the Event Feed, **skipped** means Hookshot saw the event but did not run the Protege for that event. ## Unevaluated In the Event Feed, **unevaluated** means the event has not yet been fully processed into a final decision you can rely on. ## Connected An integration or trigger source is **connected** when Hookshot can use it for the intended workflow. ## Ready **Ready** means the integration or Protege has the required setup in place for live use. ## Skill A **skill** is a reusable markdown instruction document (SKILL.md) that can be assigned to a Protege to give it specific behavior rules. Skills live in the Skills Hub and are scoped to a team. ## Skills Hub The **Skills Hub** is the team-scoped library where skills are created, managed, and assigned to Proteges. ## Chat **Chat** is the feature that lets you talk directly to Hookshot or a Protege inside Slack threads and Asana task comments by mentioning `@hookshot`. ## System Chat **System Chat** is the built-in Hookshot responder that handles direct @mention conversations without needing a user-created Protege. ## Pending Write A **pending write** is a Protege-authored change that is waiting for human approval before it is applied. Pending writes are created when the write policy requires approval. ## Write Policy The **write policy** controls whether a Protege's changes are applied immediately (`autonomous`) or require human approval (`approval_required`). ## Decision In the Work Hub, a **decision** is an approval or recommendation attached to a work item. Proteges can request decisions when they need human judgment. ## Collection (Queue) A **collection** is a named queue of work items in the Work Hub, with optional custom fields, completion rules, and provider sync. ## Context Record A **context record** is a note, attachment, or link that provides background for a work item, helping Proteges make better decisions. ## Teaching Note A **teaching note** is operator feedback attached to a Protege run, indicating whether the Protege should have run and providing guidance for future decisions. ## Credit A **credit** is the unit of consumption for Protege runs. Each run consumes credits based on the AI model's token usage. ## Credit Pack A **credit pack** is a one-time purchase that adds credits to your workspace balance. ## Auto Top-Up **Auto top-up** automatically purchases a credit pack when your balance falls below a threshold you configure. ## SE Access **SE Access** (Solutions Engineering Access) is a controlled overlay that allows Protege AI staff to view or edit your workspace configuration for support purposes. ## Provider Projection **Provider projection** is the process of pushing changes from the Work Hub back to an external provider like Asana or Jira. ## Drift Reconciliation **Drift reconciliation** is a periodic full sync between the Work Hub and an external provider that catches changes webhooks may have missed. ## Conversation Binding A **conversation binding** maps an external conversation (Slack thread or Asana task) to a chat session in Hookshot, maintaining context across messages. ## Environment Link An **environment link** pairs a production workspace with a sandbox workspace. Each workspace can belong to only one environment pair. The sandbox is used for testing Protege configurations before promoting them to production. ## Sandbox Workspace A **sandbox workspace** is a dedicated testing workspace linked to a production workspace. Proteges can be configured and tested in the sandbox, then promoted to production. Team and people administration in the sandbox is inherited from the production workspace. ## Promotion **Promotion** is the process of deploying a Protege's configuration from a sandbox workspace to its linked production workspace. Promotion copies behavior settings, tool access, and schedules while preserving production credentials and run history. {% hint style="info" %} If you see a term in the UI and are not sure what action to take next, look for that term again in [Event Feed](/event-feed.md), [Audit](/event-feed/audit.md), or [Troubleshooting](/event-feed/troubleshooting.md). Those pages turn labels into actions. {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://gitbook.tryprotege.com/glossary.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.