bricksentry 0.1.0__tar.gz

bricksentry-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+__pycache__/
+*.egg-info/
+dist/
+build/
+.pytest_cache/
+*.duckdb
+bricksentry-report.md
+bricksentry-result.json

bricksentry-0.1.0/CHANGELOG.md

@@ -0,0 +1,12 @@
+# Changelog
+
+## 0.1.0 (2026-11-10)
+
+- Key-based data diff with SQL pushdown: schema changes, added/removed/changed rows, per-column changes, nulls, numeric totals, duplicate keys, samples, segment attribution, deterministic hash sampling.
+- Downstream impact from Unity Catalog lineage system tables (tables, jobs, notebooks, pipelines, dashboards, queries) with owners and tags, plus static lineage for local work.
+- Policy-as-code verdicts: pass / warn / needs_human / block.
+- `preview_write`: run one write against a disposable shallow clone, with SQL guards.
+- Rollback plans from Delta history.
+- CLI (`diff`, `impact`, `assess`, `preview`, `rollback`, `mcp`, `init`), markdown PR report, GitHub PR comment, composite GitHub Action.
+- MCP server with six agent tools; the same tools as plain Python functions.
+- Backends: Databricks SQL warehouse (Statement Execution API) and DuckDB.

bricksentry-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

bricksentry-0.1.0/PKG-INFO

@@ -0,0 +1,186 @@
+Metadata-Version: 2.5
+Name: bricksentry
+Version: 0.1.0
+Summary: Change-safety for Databricks pipelines and the AI agents that edit them: data diffs, Unity Catalog blast radius, policy verdicts and rollback plans.
+Author: Brahma
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ai-agents,ci,data-diff,data-engineering,data-quality,databricks,delta-lake,impact-analysis,lineage,mcp,unity-catalog
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Database
+Classifier: Topic :: Software Development :: Quality Assurance
+Classifier: Topic :: Software Development :: Testing
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Requires-Dist: click>=8.1
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: all
+Requires-Dist: databricks-sdk>=0.30; extra == 'all'
+Requires-Dist: duckdb>=1.0; extra == 'all'
+Requires-Dist: mcp>=1.10; extra == 'all'
+Provides-Extra: databricks
+Requires-Dist: databricks-sdk>=0.30; extra == 'databricks'
+Provides-Extra: dev
+Requires-Dist: databricks-sdk>=0.30; extra == 'dev'
+Requires-Dist: duckdb>=1.0; extra == 'dev'
+Requires-Dist: mcp>=1.10; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Provides-Extra: duckdb
+Requires-Dist: duckdb>=1.0; extra == 'duckdb'
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.10; extra == 'mcp'
+Description-Content-Type: text/markdown
+
+# bricksentry
+
+**Change-safety for Databricks pipelines and the AI agents that edit them.**
+
+Before a change reaches production, bricksentry answers three questions, in a
+pull-request comment for humans and in structured JSON for agents:
+
+1. **What does it do to the data?** A key-based data diff: added, removed and changed rows, schema changes, per-column changes, numeric totals, duplicate keys, and *where* the change is concentrated ("100% of affected rows are region = APAC").
+2. **Who gets hurt?** The downstream blast radius from Unity Catalog lineage: tables, jobs, notebooks, Lakeflow pipelines, dashboards and queries, with owners and tags.
+3. **Is it safe, and how do I undo it?** A deterministic policy verdict (`pass` · `warn` · `needs_human` · `block`) and the exact `RESTORE TABLE … VERSION AS OF n` rollback.
+
+```
+pip install "bricksentry[databricks,mcp]"
+```
+
+## Why it exists
+
+AI now writes much of our pipeline code, and checking what that code does to the data hasn't kept up. Code review can't see a silent 3% revenue shift or a join that fans out. The tools that do catch this mostly cover dbt, or need a paid platform. Most Databricks work is PySpark notebooks, Jobs and Lakeflow pipelines, and bricksentry is built for that work:
+
+- **Unity Catalog runtime lineage**, not SQL parsing, so PySpark notebooks and jobs are included.
+- **SQL pushdown**: all diffing runs on your SQL warehouse, so no Spark session is needed and calls stay cheap enough for an agent loop.
+- **One engine, three faces**: CLI and GitHub Action · Python API · MCP server.
+
+## For AI agents: the MCP server
+
+```bash
+bricksentry mcp --config bricksentry.yml                 # stdio
+claude mcp add bricksentry -- bricksentry mcp --config /abs/path/bricksentry.yml
+```
+
+| Tool | What the agent gets |
+|---|---|
+| `whats_downstream(table, depth)` | Downstream assets with owners and tags. Call it *before* editing. |
+| `rollback_plan(table)` | The restore SQL. Capture it *before* changing anything. |
+| `preview_write(sql, target, keys?)` | Runs one write against a **disposable shallow clone**, never production, and returns the diff plus verdict. |
+| `assess_change(tables, candidates?, pr?)` | Diffs prod vs. the candidate built by your change, plus lineage and policy. Returns a verdict and an `id`. |
+| `explain_diff(assessment_id or table)` | Plain-English summary. |
+| `safe_to_ship(assessment_id)` | `safe_to_ship`, the reasons, and an explicit `next_step` to follow. |
+
+Designed for agents:
+
+- **The verdict never comes from an LLM.** Rules in `policy.yml` decide, so the same change always gets the same answer.
+- **Read-only by default.** Only `preview_write` writes, and only to a sandbox clone. It accepts a single INSERT / MERGE / UPDATE / DELETE / CREATE OR REPLACE whose target must be the clone, and it refuses DROP, TRUNCATE, ALTER, GRANT and multiple statements.
+- **Errors come back as `{"error": ...}`**, so agents can recover instead of crashing.
+- **Bounded cost:** deterministic hash sampling (`sample_pct`), capped samples, and lineage limited by depth and lookback window.
+
+The same tools are plain Python functions in `bricksentry.agent_tools`, so you can use them from LangGraph, the OpenAI Agents SDK or the Databricks Agent Framework without MCP.
+
+### See the agent loop (no Databricks needed)
+
+```bash
+pip install "bricksentry[duckdb]"
+python examples/demo/agent_loop_demo.py
+```
+
+In the demo, an agent previews a risky DELETE (needs_human, production untouched), ships a pipeline change with a join fan-out (**blocked**: 40 duplicate keys), fixes it, and gets routed to the certified table's owners. It ends with the pull-request comment a reviewer would see.
+
+## For data engineers: CLI and CI
+
+```bash
+bricksentry init                                        # starter bricksentry.yml + policy.yml
+bricksentry impact main.sales.orders                    # blast radius
+bricksentry diff main.sales.orders main.sales_pr_42.orders
+bricksentry preview main.sales.orders --sql "MERGE INTO {{target}} t USING updates u ON t.order_id = u.order_id WHEN MATCHED THEN UPDATE SET *"
+bricksentry assess --from-git origin/main --pr 42 --format markdown --fail-on needs_human
+bricksentry rollback main.sales.orders
+```
+
+Exit codes: `0` below `--fail-on`, `1` at or above it, `2` for configuration errors.
+
+**In GitHub Actions.** Build your PR's version of the pipeline into a per-PR schema (for example with a Databricks Asset Bundle `ci` target), then add:
+
+```yaml
+- run: pip install "bricksentry[databricks]"
+- run: >
+    bricksentry assess
+    --from-git origin/${{ github.base_ref }}
+    --pr ${{ github.event.pull_request.number }}
+    --comment --output bricksentry-report.md
+    --fail-on needs_human
+  env:
+    GITHUB_TOKEN: ${{ github.token }}
+    DATABRICKS_HOST: ${{ secrets.DATABRICKS_HOST }}
+    DATABRICKS_CLIENT_ID: ${{ secrets.DATABRICKS_CLIENT_ID }}
+    DATABRICKS_CLIENT_SECRET: ${{ secrets.DATABRICKS_CLIENT_SECRET }}
+    DATABRICKS_WAREHOUSE_ID: ${{ secrets.DATABRICKS_WAREHOUSE_ID }}
+```
+
+It detects changed tables from the files in the PR and posts or updates one PR comment. Check out with `fetch-depth: 0` and give the job `pull-requests: write` permission. The source repository also ships a composite `action.yml` that wraps these steps.
+
+## Python API
+
+```python
+from bricksentry import Sentry
+
+s = Sentry()                                   # reads ./bricksentry.yml
+a = s.assess(["main.sales.orders"], pr="42")
+print(a.verdict, a.notify)
+print(a.tables[0].summary)
+
+s.preview_write("DELETE FROM main.sales.orders WHERE status = 'test'", "main.sales.orders")
+```
+
+## Configuration
+
+```yaml
+backend: {type: databricks, warehouse_id: abc123}      # auth: standard Databricks SDK chain
+sandbox_schema: main.bricksentry_sandbox
+candidate_pattern: "{catalog}.{schema}_pr_{pr}.{table}"
+sample_pct: 10
+lineage: {type: databricks, depth: 3, lookback_days: 90}
+tables:
+  main.sales.orders:
+    keys: [order_id]
+    segment_by: [region]
+    paths: ["src/pipelines/orders/**", "resources/orders_job.yml"]
+policy: policy.yml
+```
+
+### Policy conditions
+
+`table` (glob) · `tag` · `downstream_tag` · `downstream_kind` · `downstream_count_gt` · `removed_pct_gt` · `added_pct_gt` · `changed_pct_gt` · `row_count_change_pct_gt` · `row_count_drop_pct_gt` · `column_removed` · `column_added` · `column_type_changed` · `duplicate_keys` · `sum_change_pct_gt` / `null_increase_gt` (optionally with `column`) · `any_change` · `diff_error`
+
+All conditions in a `when` must hold. The most severe matching rule sets the verdict. Unknown conditions are rejected at load time, so a typo can't silently disable a rule.
+
+## Permissions needed on Databricks
+
+- `CAN USE` on a SQL warehouse.
+- `SELECT` on the tables you assess and their candidates.
+- `SELECT` on `system.access.table_lineage`, plus `system.information_schema` for owners and tags. Without these, bricksentry still diffs; lineage is just empty.
+- `CREATE TABLE` on `sandbox_schema`, for `preview_write`.
+
+## Known limits (v0.1)
+
+- **Lineage is recorded at runtime.** Brand-new tables have no downstream history yet. Unity Catalog doesn't capture RDD operations, and UDFs hide column-level mapping.
+- **Keys are required.** Tables without a stable key can't be diffed row by row yet (an aggregate-profile mode is planned).
+- **Changed-table detection uses path globs** from config. It doesn't parse Asset Bundles yet.
+- **The Databricks backend is tested against a mocked SDK.** Run it against a dev workspace before relying on it in CI.
+
+## Roadmap
+
+Asset Bundle parsing for automatic table detection · column-level blast radius from `system.access.column_lineage` · an aggregate diff for keyless tables · Lakeflow expectations in the verdict · `bricksentry watch` for scheduled drift checks · a Databricks App UI.
+
+## License
+
+Apache-2.0

bricksentry-0.1.0/README.md

@@ -0,0 +1,146 @@
+# bricksentry
+
+**Change-safety for Databricks pipelines and the AI agents that edit them.**
+
+Before a change reaches production, bricksentry answers three questions, in a
+pull-request comment for humans and in structured JSON for agents:
+
+1. **What does it do to the data?** A key-based data diff: added, removed and changed rows, schema changes, per-column changes, numeric totals, duplicate keys, and *where* the change is concentrated ("100% of affected rows are region = APAC").
+2. **Who gets hurt?** The downstream blast radius from Unity Catalog lineage: tables, jobs, notebooks, Lakeflow pipelines, dashboards and queries, with owners and tags.
+3. **Is it safe, and how do I undo it?** A deterministic policy verdict (`pass` · `warn` · `needs_human` · `block`) and the exact `RESTORE TABLE … VERSION AS OF n` rollback.
+
+```
+pip install "bricksentry[databricks,mcp]"
+```
+
+## Why it exists
+
+AI now writes much of our pipeline code, and checking what that code does to the data hasn't kept up. Code review can't see a silent 3% revenue shift or a join that fans out. The tools that do catch this mostly cover dbt, or need a paid platform. Most Databricks work is PySpark notebooks, Jobs and Lakeflow pipelines, and bricksentry is built for that work:
+
+- **Unity Catalog runtime lineage**, not SQL parsing, so PySpark notebooks and jobs are included.
+- **SQL pushdown**: all diffing runs on your SQL warehouse, so no Spark session is needed and calls stay cheap enough for an agent loop.
+- **One engine, three faces**: CLI and GitHub Action · Python API · MCP server.
+
+## For AI agents: the MCP server
+
+```bash
+bricksentry mcp --config bricksentry.yml                 # stdio
+claude mcp add bricksentry -- bricksentry mcp --config /abs/path/bricksentry.yml
+```
+
+| Tool | What the agent gets |
+|---|---|
+| `whats_downstream(table, depth)` | Downstream assets with owners and tags. Call it *before* editing. |
+| `rollback_plan(table)` | The restore SQL. Capture it *before* changing anything. |
+| `preview_write(sql, target, keys?)` | Runs one write against a **disposable shallow clone**, never production, and returns the diff plus verdict. |
+| `assess_change(tables, candidates?, pr?)` | Diffs prod vs. the candidate built by your change, plus lineage and policy. Returns a verdict and an `id`. |
+| `explain_diff(assessment_id or table)` | Plain-English summary. |
+| `safe_to_ship(assessment_id)` | `safe_to_ship`, the reasons, and an explicit `next_step` to follow. |
+
+Designed for agents:
+
+- **The verdict never comes from an LLM.** Rules in `policy.yml` decide, so the same change always gets the same answer.
+- **Read-only by default.** Only `preview_write` writes, and only to a sandbox clone. It accepts a single INSERT / MERGE / UPDATE / DELETE / CREATE OR REPLACE whose target must be the clone, and it refuses DROP, TRUNCATE, ALTER, GRANT and multiple statements.
+- **Errors come back as `{"error": ...}`**, so agents can recover instead of crashing.
+- **Bounded cost:** deterministic hash sampling (`sample_pct`), capped samples, and lineage limited by depth and lookback window.
+
+The same tools are plain Python functions in `bricksentry.agent_tools`, so you can use them from LangGraph, the OpenAI Agents SDK or the Databricks Agent Framework without MCP.
+
+### See the agent loop (no Databricks needed)
+
+```bash
+pip install "bricksentry[duckdb]"
+python examples/demo/agent_loop_demo.py
+```
+
+In the demo, an agent previews a risky DELETE (needs_human, production untouched), ships a pipeline change with a join fan-out (**blocked**: 40 duplicate keys), fixes it, and gets routed to the certified table's owners. It ends with the pull-request comment a reviewer would see.
+
+## For data engineers: CLI and CI
+
+```bash
+bricksentry init                                        # starter bricksentry.yml + policy.yml
+bricksentry impact main.sales.orders                    # blast radius
+bricksentry diff main.sales.orders main.sales_pr_42.orders
+bricksentry preview main.sales.orders --sql "MERGE INTO {{target}} t USING updates u ON t.order_id = u.order_id WHEN MATCHED THEN UPDATE SET *"
+bricksentry assess --from-git origin/main --pr 42 --format markdown --fail-on needs_human
+bricksentry rollback main.sales.orders
+```
+
+Exit codes: `0` below `--fail-on`, `1` at or above it, `2` for configuration errors.
+
+**In GitHub Actions.** Build your PR's version of the pipeline into a per-PR schema (for example with a Databricks Asset Bundle `ci` target), then add:
+
+```yaml
+- run: pip install "bricksentry[databricks]"
+- run: >
+    bricksentry assess
+    --from-git origin/${{ github.base_ref }}
+    --pr ${{ github.event.pull_request.number }}
+    --comment --output bricksentry-report.md
+    --fail-on needs_human
+  env:
+    GITHUB_TOKEN: ${{ github.token }}
+    DATABRICKS_HOST: ${{ secrets.DATABRICKS_HOST }}
+    DATABRICKS_CLIENT_ID: ${{ secrets.DATABRICKS_CLIENT_ID }}
+    DATABRICKS_CLIENT_SECRET: ${{ secrets.DATABRICKS_CLIENT_SECRET }}
+    DATABRICKS_WAREHOUSE_ID: ${{ secrets.DATABRICKS_WAREHOUSE_ID }}
+```
+
+It detects changed tables from the files in the PR and posts or updates one PR comment. Check out with `fetch-depth: 0` and give the job `pull-requests: write` permission. The source repository also ships a composite `action.yml` that wraps these steps.
+
+## Python API
+
+```python
+from bricksentry import Sentry
+
+s = Sentry()                                   # reads ./bricksentry.yml
+a = s.assess(["main.sales.orders"], pr="42")
+print(a.verdict, a.notify)
+print(a.tables[0].summary)
+
+s.preview_write("DELETE FROM main.sales.orders WHERE status = 'test'", "main.sales.orders")
+```
+
+## Configuration
+
+```yaml
+backend: {type: databricks, warehouse_id: abc123}      # auth: standard Databricks SDK chain
+sandbox_schema: main.bricksentry_sandbox
+candidate_pattern: "{catalog}.{schema}_pr_{pr}.{table}"
+sample_pct: 10
+lineage: {type: databricks, depth: 3, lookback_days: 90}
+tables:
+  main.sales.orders:
+    keys: [order_id]
+    segment_by: [region]
+    paths: ["src/pipelines/orders/**", "resources/orders_job.yml"]
+policy: policy.yml
+```
+
+### Policy conditions
+
+`table` (glob) · `tag` · `downstream_tag` · `downstream_kind` · `downstream_count_gt` · `removed_pct_gt` · `added_pct_gt` · `changed_pct_gt` · `row_count_change_pct_gt` · `row_count_drop_pct_gt` · `column_removed` · `column_added` · `column_type_changed` · `duplicate_keys` · `sum_change_pct_gt` / `null_increase_gt` (optionally with `column`) · `any_change` · `diff_error`
+
+All conditions in a `when` must hold. The most severe matching rule sets the verdict. Unknown conditions are rejected at load time, so a typo can't silently disable a rule.
+
+## Permissions needed on Databricks
+
+- `CAN USE` on a SQL warehouse.
+- `SELECT` on the tables you assess and their candidates.
+- `SELECT` on `system.access.table_lineage`, plus `system.information_schema` for owners and tags. Without these, bricksentry still diffs; lineage is just empty.
+- `CREATE TABLE` on `sandbox_schema`, for `preview_write`.
+
+## Known limits (v0.1)
+
+- **Lineage is recorded at runtime.** Brand-new tables have no downstream history yet. Unity Catalog doesn't capture RDD operations, and UDFs hide column-level mapping.
+- **Keys are required.** Tables without a stable key can't be diffed row by row yet (an aggregate-profile mode is planned).
+- **Changed-table detection uses path globs** from config. It doesn't parse Asset Bundles yet.
+- **The Databricks backend is tested against a mocked SDK.** Run it against a dev workspace before relying on it in CI.
+
+## Roadmap
+
+Asset Bundle parsing for automatic table detection · column-level blast radius from `system.access.column_lineage` · an aggregate diff for keyless tables · Lakeflow expectations in the verdict · `bricksentry watch` for scheduled drift checks · a Databricks App UI.
+
+## License
+
+Apache-2.0

bricksentry-0.1.0/action.yml

@@ -0,0 +1,59 @@
+name: bricksentry
+description: Data diff, Unity Catalog blast radius and a policy verdict for every pull request that changes Databricks pipelines.
+branding:
+  icon: shield
+  color: orange
+
+inputs:
+  config:
+    description: Path to bricksentry.yml
+    default: bricksentry.yml
+  base-ref:
+    description: Git ref to compare against for changed-table detection (defaults to the PR base branch)
+    default: ""
+  tables:
+    description: Optional space-separated list of tables to always assess
+    default: ""
+  fail-on:
+    description: Fail the check when the verdict is at least this severe (pass, warn, needs_human, block)
+    default: needs_human
+  comment:
+    description: Post or update a PR comment with the report
+    default: "true"
+  version:
+    description: bricksentry version spec to install (e.g. "==0.1.0"); empty = latest
+    default: ""
+
+outputs:
+  verdict:
+    description: pass, warn, needs_human or block
+    value: ${{ steps.run.outputs.verdict }}
+
+runs:
+  using: composite
+  steps:
+    - uses: actions/setup-python@v5
+      with:
+        python-version: "3.12"
+    - name: Install bricksentry
+      shell: bash
+      run: pip install "bricksentry[databricks]${{ inputs.version }}"
+    - name: Assess change
+      id: run
+      shell: bash
+      env:
+        BRICKSENTRY_PR: ${{ github.event.pull_request.number }}
+        GITHUB_TOKEN: ${{ github.token }}
+      run: |
+        set +e
+        BASE="${{ inputs.base-ref }}"
+        if [ -z "$BASE" ]; then BASE="origin/${{ github.base_ref }}"; fi
+        ARGS=(assess --config "${{ inputs.config }}" --from-git "$BASE" --format json --output bricksentry-report.md --fail-on "${{ inputs.fail-on }}")
+        for t in ${{ inputs.tables }}; do ARGS+=(--table "$t"); done
+        if [ "${{ inputs.comment }}" = "true" ] && [ -n "$BRICKSENTRY_PR" ]; then ARGS+=(--comment); fi
+        bricksentry "${ARGS[@]}" > bricksentry-result.json
+        CODE=$?
+        VERDICT=$(python -c "import json;print(json.load(open('bricksentry-result.json')).get('verdict','pass'))" 2>/dev/null || echo "error")
+        echo "verdict=$VERDICT" >> "$GITHUB_OUTPUT"
+        [ -f bricksentry-report.md ] && cat bricksentry-report.md >> "$GITHUB_STEP_SUMMARY"
+        exit $CODE

bricksentry-0.1.0/examples/databricks/bricksentry.yml

@@ -0,0 +1,34 @@
+# Example config for a Databricks workspace.
+backend:
+  type: databricks
+  # warehouse_id: 1234567890abcdef     # or set DATABRICKS_WAREHOUSE_ID
+  # profile: DEFAULT                   # ~/.databrickscfg profile; CI usually uses env vars
+
+# Disposable clones for preview_write live here (SHALLOW CLONE, metadata only).
+sandbox_schema: main.bricksentry_sandbox
+
+# Your CI job builds the changed pipeline into a per-PR schema; bricksentry diffs it against prod.
+candidate_pattern: "{catalog}.{schema}_pr_{pr}.{table}"
+
+# Big tables: diff a deterministic 10% key sample. Remove for full diffs.
+sample_pct: 10
+max_samples: 5
+
+lineage:
+  type: databricks      # reads system.access.table_lineage + information_schema
+  depth: 3
+  lookback_days: 90
+
+tables:
+  main.sales.orders:
+    keys: [order_id]
+    segment_by: [region, channel]
+    paths:
+      - "src/pipelines/orders/**"
+      - "resources/orders_job.yml"
+  main.sales.daily_revenue:
+    keys: [revenue_date, region]
+    paths:
+      - "src/pipelines/revenue/**"
+
+policy: policy.yml