# kestra - 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: `kestra-io/kestra` - capability: Event Driven Orchestration & Scheduling Platform for Mission Critical Applications - expected_user_outcome: Event Driven Orchestration & Scheduling Platform for Mission Critical Applications ## 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. - **System Architecture & Multi-Server Topology**: importance `high` - source_paths: cli/src/main/java/io/kestra/cli/commands/servers/ServerCommand.java, cli/src/main/java/io/kestra/cli/commands/servers/WebServerCommand.java, cli/src/main/java/io/kestra/cli/commands/servers/ExecutorCommand.java, cli/src/main/java/io/kestra/cli/commands/servers/SchedulerCommand.java, cli/src/main/java/io/kestra/cli/commands/servers/WorkerCommand.java - **Flows, Tasks, Triggers & Execution Model**: importance `high` - source_paths: core/src/main/java/io/kestra/core/models/flows/Flow.java, core/src/main/java/io/kestra/core/models/flows/AbstractFlow.java, core/src/main/java/io/kestra/core/models/flows/State.java, core/src/main/java/io/kestra/core/models/flows/Concurrency.java, core/src/main/java/io/kestra/core/models/flows/PluginDefault.java - **Frontend UI, Filters, Dashboards & Topology**: importance `high` - source_paths: ui/src/main.ts, ui/src/App.vue, ui/src/components/layout/SideBar.vue, ui/src/components/layout/TopNavBar.vue, ui/src/components/filter/QuickFilters.vue - **Concurrency Limits, Replay & Execution Lifecycle**: importance `high` - source_paths: core/src/main/java/io/kestra/core/models/flows/Concurrency.java, core/src/main/java/io/kestra/core/models/executions/Execution.java, core/src/main/java/io/kestra/core/models/executions/ExecutionKilled.java, core/src/main/java/io/kestra/core/models/executions/ExecutionQueued.java, core/src/main/java/io/kestra/core/executor/command/Replay.java ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `b84ebef50774c247c42534a609d674433b91d0bb` - inspected_files: `Dockerfile`, `README.md`, `docker-compose.yml`, `docs/architecture/METRICS_GUIDELINES.md` 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: Installation risk requires verification - Trigger: Project evidence flags a installation 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: community_evidence:github | https://github.com/kestra-io/kestra/issues/16896 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance 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: community_evidence:github | https://github.com/kestra-io/kestra/issues/16603 - 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: Project evidence flags a installation 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 | https://github.com/kestra-io/kestra - 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: v0.22.44 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v0.22.44. Context: Observed during installation or first-run setup. - Why it matters: Upgrade or migration may change expected behavior: v0.22.44 - Evidence: failure_mode_cluster:github_release | https://github.com/kestra-io/kestra/releases/tag/v0.22.44 - 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: Project evidence flags a installation 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: community_evidence:github | https://github.com/kestra-io/kestra/issues/16433 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: Allow adjusting the flow template based on configuration - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Allow adjusting the flow template based on configuration. Context: Source discussion did not expose a precise runtime context. - Why it matters: Developers may misconfigure credentials, environment, or host setup: Allow adjusting the flow template based on configuration - Evidence: failure_mode_cluster:github_issue | https://github.com/kestra-io/kestra/issues/4956 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v1.0.46 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.0.46. Context: Observed during version upgrade or migration. - Why it matters: Upgrade or migration may change expected behavior: v1.0.46 - Evidence: failure_mode_cluster:github_release | https://github.com/kestra-io/kestra/releases/tag/v1.0.46 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v1.3.20 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.3.20. Context: Observed during version upgrade or migration. - Why it matters: Upgrade or migration may change expected behavior: v1.3.20 - Evidence: failure_mode_cluster:github_release | https://github.com/kestra-io/kestra/releases/tag/v1.3.20 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v1.3.21 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.3.21. Context: Observed during version upgrade or migration. - Why it matters: Upgrade or migration may change expected behavior: v1.3.21 - Evidence: failure_mode_cluster:github_release | https://github.com/kestra-io/kestra/releases/tag/v1.3.21 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Configuration risk requires verification - Trigger: Developers should check this configuration risk before relying on the project: v1.3.22 - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: v1.3.22. Context: Source discussion did not expose a precise runtime context. - Why it matters: Upgrade or migration may change expected behavior: v1.3.22 - Evidence: failure_mode_cluster:github_release | https://github.com/kestra-io/kestra/releases/tag/v1.3.22 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.