# trigger.dev - Doramagic AI Context Pack

> Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated.

## Project

- canonical_name: `triggerdotdev/trigger.dev`
- capability: Trigger.dev – build and deploy fully‑managed AI agents and workflows
- expected_user_outcome: Trigger.dev – build and deploy fully‑managed AI agents and workflows

## Operating Boundaries

- Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it.
- Project facts must come from repo evidence, Claim Graph, or explicit source references.
- When a capability is not verified, mark it as unverified instead of completing it as fact.
- publish_status: `publishable`
- blocking_gaps: none

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Platform Overview & Architecture**: importance `high`
  - source_paths: README.md, package.json, turbo.json, pnpm-workspace.yaml, docs/introduction.mdx
- **Trigger.dev CLI v3 & Developer Workflows**: importance `high`
  - source_paths: packages/cli-v3/README.md, packages/cli-v3/DEVELOPMENT.md, packages/cli-v3/src/cli/index.ts, packages/cli-v3/src/commands/dev.ts, packages/cli-v3/src/commands/deploy.ts
- **Run Engine, Queues, and Task Execution**: importance `high`
  - source_paths: internal-packages/run-engine/README.md, internal-packages/run-engine/src/engine/index.ts, internal-packages/run-engine/src/engine/systems/systems.ts, internal-packages/run-engine/src/run-queue/index.ts, internal-packages/run-engine/src/batch-queue/index.ts
- **Deployment, Self-hosting & Worker Infrastructure**: importance `high`
  - source_paths: DOCKER_INSTALLATION.md, docker/docker-compose.yml, docker/Dockerfile, hosting/docker/docker-compose.traefik.yml, hosting/k8s/helm/Chart.yaml

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `8dc77c0ccde7cf0e127f3d3da04d892d4aa54e6d`
- inspected_files: `pnpm-lock.yaml`, `README.md`, `package.json`, `docs/migration-defer.mdx`, `docs/wait-for-token.mdx`, `docs/examples.mdx`, `docs/cli-dev-commands.mdx`, `docs/cli-preview-archive.mdx`, `docs/help-email.mdx`, `docs/video-walkthrough.mdx`, `docs/how-to-reduce-your-spend.mdx`, `docs/openapi.yml`, `docs/run-usage.mdx`, `docs/cli-init-commands.mdx`, `docs/apikeys.mdx`, `docs/batch-queue-metrics.md`, `docs/docs.json`, `docs/cli-deploy-commands.mdx`, `docs/manual-setup.mdx`, `docs/community.mdx`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Identity risk requires verification

- Trigger: Project evidence flags a identity risk. Review the linked source before relying on this workflow.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: identity.distribution | github_repo:572570113 | https://github.com/triggerdotdev/trigger.dev
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: bug: CLI crashes with "Invalid comparator: catalog:" when @trigger.dev/* deps use workspace catalogs (bun/pnpm catalog: protocol)
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: bug: CLI crashes with "Invalid comparator: catalog:" when @trigger.dev/* deps use workspace catalogs (bun/pnpm catalog: protocol). Context: Observed when using node, windows
- Why it matters: Developers may fail before the first successful local run: bug: CLI crashes with "Invalid comparator: catalog:" when @trigger.dev/* deps use workspace catalogs (bun/pnpm catalog: protocol)
- Evidence: failure_mode_cluster:github_issue | https://github.com/triggerdotdev/trigger.dev/issues/3905
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: trigger.dev v4.4.3
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: trigger.dev v4.4.3. Context: Observed when using node, python, docker
- Why it matters: Upgrade or migration may change expected behavior: trigger.dev v4.4.3
- Evidence: failure_mode_cluster:github_release | https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.4.3
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: trigger.dev v4.4.4
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: trigger.dev v4.4.4. Context: Observed when using node, docker
- Why it matters: Upgrade or migration may change expected behavior: trigger.dev v4.4.4
- Evidence: failure_mode_cluster:github_release | https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.4.4
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: trigger.dev v4.4.5
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: trigger.dev v4.4.5. Context: Observed when using node, docker
- Why it matters: Upgrade or migration may change expected behavior: trigger.dev v4.4.5
- Evidence: failure_mode_cluster:github_release | https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.4.5
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 6: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: trigger.dev v4.4.6
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: trigger.dev v4.4.6. Context: Observed when using node, python, docker
- Why it matters: Upgrade or migration may change expected behavior: trigger.dev v4.4.6
- Evidence: failure_mode_cluster:github_release | https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.4.6
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 7: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: trigger.dev v4.5.0-rc.0
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: trigger.dev v4.5.0-rc.0. Context: Observed when using node, docker
- Why it matters: Upgrade or migration may change expected behavior: trigger.dev v4.5.0-rc.0
- Evidence: failure_mode_cluster:github_release | https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.0-rc.0
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 8: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: trigger.dev v4.5.0-rc.1
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: trigger.dev v4.5.0-rc.1. Context: Observed when using node, python, docker
- Why it matters: Upgrade or migration may change expected behavior: trigger.dev v4.5.0-rc.1
- Evidence: failure_mode_cluster:github_release | https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.0-rc.1
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 9: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: trigger.dev v4.5.0-rc.2
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: trigger.dev v4.5.0-rc.2. Context: Observed when using node, python, docker
- Why it matters: Upgrade or migration may change expected behavior: trigger.dev v4.5.0-rc.2
- Evidence: failure_mode_cluster:github_release | https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.0-rc.2
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 10: Installation risk requires verification

- Trigger: Developers should check this installation risk before relying on the project: trigger.dev v4.5.0-rc.3
- Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: trigger.dev v4.5.0-rc.3. Context: Observed when using node, python, docker
- Why it matters: Upgrade or migration may change expected behavior: trigger.dev v4.5.0-rc.3
- Evidence: failure_mode_cluster:github_release | https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.0-rc.3
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.