# sqlmesh - 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: `SQLMesh/sqlmesh` - capability: Scalable and efficient data transformation framework - backwards compatible with dbt. - expected_user_outcome: Scalable and efficient data transformation framework - backwards compatible with dbt. ## 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. - **SQLMesh Overview and Core Architecture**: importance `high` - source_paths: README.md, sqlmesh/__init__.py, sqlmesh/core/context.py, sqlmesh/core/plan/definition.py, sqlmesh/core/environment.py - **Database Engine Adapters and External Integrations**: importance `high` - source_paths: sqlmesh/core/engine_adapter/base.py, sqlmesh/core/engine_adapter/snowflake.py, sqlmesh/core/engine_adapter/bigquery.py, sqlmesh/core/engine_adapter/databricks.py, sqlmesh/core/engine_adapter/duckdb.py - **LSP, VSCode Extension, and Web UI**: importance `medium` - source_paths: sqlmesh/lsp/main.py, sqlmesh/lsp/api.py, sqlmesh/lsp/context.py, sqlmesh/lsp/completions.py, sqlmesh/lsp/lineage.py - **State Management, Migrations, and CI/CD**: importance `high` - source_paths: sqlmesh/core/state_sync/base.py, sqlmesh/core/state_sync/db/facade.py, sqlmesh/core/state_sync/db/snapshot.py, sqlmesh/core/state_sync/db/environment.py, sqlmesh/core/state_sync/db/migrator.py ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `960775f38bfe2b73822f0a18b7d23d4a641cd9b0` - inspected_files: `README.md`, `package.json`, `pnpm-lock.yaml`, `pyproject.toml`, `docs/HOWTO.md`, `docs/cloud/cloud_index.md`, `docs/cloud/features/alerts_notifications.md`, `docs/cloud/features/costs_savings.md`, `docs/cloud/features/data_catalog.md`, `docs/cloud/features/debugger_view.md`, `docs/cloud/features/incident_reporting.md`, `docs/cloud/features/observability/development_environment.md`, `docs/cloud/features/observability/measures_dashboards.md`, `docs/cloud/features/observability/model.md`, `docs/cloud/features/observability/model_freshness.md`, `docs/cloud/features/observability/overview.md`, `docs/cloud/features/observability/plan.md`, `docs/cloud/features/observability/prod_environment.md`, `docs/cloud/features/observability/run.md`, `docs/cloud/features/scheduler/airflow.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/SQLMesh/sqlmesh/issues/5765 - 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/SQLMesh/sqlmesh/issues/5350 - 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/SQLMesh/sqlmesh/issues/5841 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Capability evidence risk requires verification - Trigger: Project evidence flags a capability evidence 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/SQLMesh/sqlmesh/issues/5767 - 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/SQLMesh/sqlmesh/issues/5842 - 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: 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/SQLMesh/sqlmesh/issues/5843 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: 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/SQLMesh/sqlmesh - 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: evidence.maintainer_signals | https://github.com/SQLMesh/sqlmesh - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 9: 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/SQLMesh/sqlmesh - 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: risks.scoring_risks | https://github.com/SQLMesh/sqlmesh - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.