# 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.

## Run

A **run** is one execution of a Protege.

## 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.

{% 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://docs.tryprotege.com/glossary.md?ask=<question>
```

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.