# dagster - 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: `dagster-io/dagster` - capability: An orchestration platform for the development, production, and observation of data assets. - expected_user_outcome: An orchestration platform for the development, production, and observation of data assets. ## 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. - **Dagster Overview and Core Concepts**: importance `high` - source_paths: README.md, docs/docs/intro.md, docs/docs/getting-started/quickstart.md, docs/docs/getting-started/installation.md, docs/docs/getting-started/concepts.md - **System Architecture and Deployment**: importance `high` - source_paths: docs/docs/deployment/oss/oss-deployment-architecture.md, docs/docs/deployment/oss/dagster-yaml.md, docs/docs/deployment/dagster-plus/index.md, docs/docs/deployment/dagster-plus/hybrid/architecture.md, docs/docs/deployment/dagster-plus/serverless/index.md - **Integrations and Extensibility**: importance `high` - source_paths: docs/docs/integrations/index.md, docs/docs/integrations/libraries/index.md, docs/docs/integrations/libraries/dbt/index.md, docs/docs/integrations/external-pipelines/index.md, docs/docs/integrations/external-pipelines/using-dagster-pipes/index.md - **Operations, Observability, and Community Roadmap**: importance `medium` - source_paths: docs/docs/guides/operate/managing-concurrency/index.md, docs/docs/guides/observe/asset-freshness-policies.md, docs/docs/guides/observe/asset-health-status.md, docs/docs/guides/observe/alerts/index.md, docs/docs/observe/index.md ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `8ebdf4aa5f24ef42e5447596ee23ea5972e8d40a` - inspected_files: `README.md`, `pyproject.toml`, `uv.lock`, `docs/.eslintrc.js`, `docs/.prettierrc.js`, `docs/.remarkrc.js`, `docs/.yarnrc.yml`, `docs/CLAUDE.md`, `docs/README.md`, `docs/babel.config.js`, `docs/dagsterVersions.json`, `docs/docs/about/changelog.md`, `docs/docs/about/community.md`, `docs/docs/about/contributing-docs/content-model.md`, `docs/docs/about/contributing-docs/formatting-style.md`, `docs/docs/about/contributing-docs/index.md`, `docs/docs/about/contributing.md`, `docs/docs/about/data-portability.md`, `docs/docs/about/releases.md`, `docs/docs/about/telemetry.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/dagster-io/dagster/issues/24989 - 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: 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/dagster-io/dagster/issues/29674 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Configuration risk requires verification - Trigger: Project evidence flags a configuration 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/dagster-io/dagster/issues/33946 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Configuration risk requires verification - Trigger: Project evidence flags a configuration 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/dagster-io/dagster/issues/33945 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - 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: capability.assumptions | https://github.com/dagster-io/dagster - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: 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/dagster-io/dagster/issues/33944 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: 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/dagster-io/dagster/issues/29693 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: 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/dagster-io/dagster/issues/33943 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: 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: evidence.maintainer_signals | https://github.com/dagster-io/dagster - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 10: Security or permission risk requires verification - Trigger: no_demo - 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: downstream_validation.risk_items | https://github.com/dagster-io/dagster - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.