Data PlatformZoom level 3
Who calls what: Deployable bundles (realms)
Every class, function and method in Deployable bundles (realms), with who calls it. Found by reading the code. A call written as object.method() is matched by the method's name, so a same-named method elsewhere can appear: those rows say by name.
135 definitions in 19 modules. Jump to a module: generate_bundle.py · integration.py · lakeformation.py · meta_setup.py · generate_bundle.py · test_realm.py · enable_anomaly_detection.py · generate.py · compare.py · silver.py · probe.py · semantic_layer.py · silver.py · deploy_genie.py · generate.py · render.py · checks.py · main.py · paths.py
realms/aws-databricks/generate_bundle.py
Generate the Databricks Asset Bundle for Databricks on AWS from the compiled manifests (M4: jobs are generated, never hand-written). none yet
realms/aws-databricks/integration.py
Integration test on a deployed environment (CI: after deploy dev, before the release gate). none yet
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
proof_jobsfunction, line 25 | The proof job of every compiled domain, by its key in the generated bundle. | main · realms/aws-databricks/integration.py:39 | no test names it |
commandfunction, line 30 | main · realms/aws-databricks/integration.py:41 | test_cli.py | |
mainfunction, line 34 | module level · realms/aws-databricks/integration.py:46 | no test names it |
realms/aws-databricks/lakeformation.py
Lake Formation grants from the same access plan as Unity Catalog (ADR-028 rule 4, B12): AWS engines (Redshift, Athena) read the Unity Catalog tables through a Glue federated catalog, and Lake Formation decides what each reader sees. Permiss none yet
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
_qfunction, line 29 | terraform · realms/aws-databricks/lakeformation.py:67 | no test names it | |
_dbfunction, line 33 | intents · realms/aws-databricks/lakeformation.py:48terraform · realms/aws-databricks/lakeformation.py:91 | no test names it | |
intentsfunction, line 37 | What Lake Formation must hold: one row per (principal, database, table, permission, filter). | terraform · realms/aws-databricks/lakeformation.py:63 | test_lakeformation.py |
terraformfunction, line 59 | The Terraform for the intents, plus one data-cells filter per (group, table) that hides protected columns and one per row-filtered table and limited group. | none found in the code | test_lakeformation.py |
driftfunction, line 98 | missing: in the model, not in Lake Formation (a reader is blocked). extra: in Lake Formation, not in the model (a reader sees more than the model allows: the dangerous side). | none found in the code | test_lakeformation.py, test_governance_catalog.py and 4 more |
realms/aws-databricks/meta_setup.py
Install the metadata store (ADR-010) on a Lakebase instance and load a domain's manifest into it. none yet
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
clifunction, line 31 | dsn · realms/aws-databricks/meta_setup.py:43token · realms/aws-databricks/meta_setup.py:50wake · realms/aws-databricks/meta_setup.py:59 | no test names it | |
sayfunction, line 38 | wake · realms/aws-databricks/meta_setup.py:65main · realms/aws-databricks/meta_setup.py:80 | no test names it | |
dsnfunction, line 42 | main · realms/aws-databricks/meta_setup.py:76 | no test names it | |
tokenfunction, line 48 | main · realms/aws-databricks/meta_setup.py:77 | test_bundle.py, test_semantic_governance.py and 18 more | |
wakefunction, line 53 | Lakebase moved to Autoscaling (projects, branches, endpoints): an instance made on 4 Nov is now project <instance> with endpoint production/primary, and an endpoint can be disabled (seen 13 Nov: connections refused with "The endpoint has be | main · realms/aws-databricks/meta_setup.py:75 | no test names it |
mainfunction, line 68 | module level · realms/aws-databricks/meta_setup.py:94 | no test names it |
realms/azure-databricks/generate_bundle.py
Generate the Databricks Asset Bundle that deploys the platform's engine job to an Azure Databricks workspace. none yet
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
repointfunction, line 38 | A path in the engine's bundle (relative to realms/databricks/engine), as seen from this bundle. | generate · realms/azure-databricks/generate_bundle.py:62 | no test names it |
targetfunction, line 45 | generate · realms/azure-databricks/generate_bundle.py:65 | test_bundle.py, test_obs_dashboards.py and 16 more | |
generatefunction, line 53 | render · realms/azure-databricks/generate_bundle.py:76 | test_bundle.py, test_semantic_governance.py and 1 more | |
renderfunction, line 74 | main · realms/azure-databricks/generate_bundle.py:83 | test_semantic_governance.py, test_obs_dashboards.py and 3 more | |
mainfunction, line 79 | module level · realms/azure-databricks/generate_bundle.py:96 | no test names it |
realms/azure-databricks/tests/test_realm.py
Offline checks of the Azure Databricks realm: names, layers, secrets, budget, isolation, pinned versions, bundle. none yet
realms/databricks/dashboards/enable_anomaly_detection.py
Turn on the platform's anomaly detection (freshness and completeness, limits learned per table) on every schema of the silver and gold catalogs: the adopted half of "freshness" (obs/native.py `anomaly_detection`). Idempotent: a schema alrea Operations page and dashboards
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
clifunction, line 18 | main · realms/databricks/dashboards/enable_anomaly_detection.py:32 | no test names it | |
mainfunction, line 26 | module level · realms/databricks/dashboards/enable_anomaly_detection.py:49 | no test names it |
realms/databricks/dashboards/generate.py
Write (or check) the ops dashboards, the ops metric views and the adopted native set (ADR-024). Operations page and dashboards
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
filesfunction, line 29 | stale_files · realms/databricks/dashboards/generate.py:41main · realms/databricks/dashboards/generate.py:53 | test_bundle.py, test_semantic_governance.py and 42 more | |
stale_filesfunction, line 39 | Generated files no definition produces any more (a dashboard or view removed). | main · realms/databricks/dashboards/generate.py:60 | no test names it |
mainfunction, line 46 | module level · realms/databricks/dashboards/generate.py:72 | no test names it |
realms/databricks/declarative/compare.py
Compare the declarative silver (schema declarative_proof) with the job-built silver, dataset by dataset: current live rows (history) or all rows (append), version counts, and rows that differ on the business columns. Declarative engine
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
qfunction, line 7 | module level · realms/databricks/declarative/compare.py:15 | no test names it |
realms/databricks/declarative/silver.py
The declarative silver engine on Databricks (ADR-035): one generic definition for every dataset whose silver_engine is `declarative` (or the datasets named in dp.only, for proofs). Declarative engine
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
declarefunction, line 38 | module level · realms/databricks/declarative/silver.py:87 | test_world_tyre.py, test_adf_generator.py and 1 more | |
declare.stagedfunction, line 41 | declare · realms/databricks/declarative/silver.py:44 | no test names it | |
declare.appendedfunction, line 59 | declare · realms/databricks/declarative/silver.py:68 (value) | test_hop_reports.py, test_ingest_pipelines.py and 3 more |
realms/databricks/engine/tasks/probe.py
What Databricks serverless allows the engine (13 Nov probe). Each check prints one line: ok or FAIL with the reason. Throwaway schema, dropped at the end. Orchestration, end to end
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
checkfunction, line 27 | module level · realms/databricks/engine/tasks/probe.py:35 | test_azure_adapters.py, test_contract_rules.py and 30 more | |
createfunction, line 44 | module level · realms/databricks/engine/tasks/probe.py:52 (value) | test_genie_deploy.py, test_deploy_use_case.py and 1 more | |
lakebasefunction, line 75 | module level · realms/databricks/engine/tasks/probe.py:86 | test_lakebase.py, test_meta_store.py |
realms/databricks/engine/tasks/semantic_layer.py
After a proof run: create the business metric views (the semantic generator's committed SQL for this environment) and ask each certified known answer of the DEPLOYED views, the way a dashboard tile or a Genie answer would. Orchestration, end to end
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
_statementsfunction, line 18 | create_views · realms/databricks/engine/tasks/semantic_layer.py:25check · realms/databricks/engine/tasks/semantic_layer.py:36 | no test names it | |
create_viewsfunction, line 22 | none found in the code | no test names it | |
_samefunction, line 30 | check · realms/databricks/engine/tasks/semantic_layer.py:46 | no test names it | |
checkfunction, line 34 | One row per certified known answer: the deployed view's number, gold's (Python) and the world's. | none found in the code | test_azure_adapters.py, test_contract_rules.py and 30 more |
realms/databricks/pipelines/silver.py
Silver, as a Lakeflow Declarative Pipeline: maximum use of what Databricks offers, driven by the metadata DB. none yet
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
validfunction, line 30 | none found in the code | azure_fakes.py, gold_helpers.py and 14 more | |
quarantinefunction, line 35 | none found in the code | silver_helpers.py, test_azure_adapters.py and 10 more |
realms/databricks/semantic_governance/deploy_genie.py
Deploy the generated Genie space (B12, SERV-06): create it, or update the space with the same title. Semantic layer
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
payloadfunction, line 23 | The create/update request body from the generated file (warehouse id filled in per environment). | main · realms/databricks/semantic_governance/deploy_genie.py:51 | test_genie_deploy.py, test_governance_catalog.py and 6 more |
existingfunction, line 29 | main · realms/databricks/semantic_governance/deploy_genie.py:52 | test_genie_deploy.py, azure_fakes.py and 8 more | |
clifunction, line 36 | main · realms/databricks/semantic_governance/deploy_genie.py:52 | no test names it | |
mainfunction, line 43 | module level · realms/databricks/semantic_governance/deploy_genie.py:66 | no test names it |
realms/databricks/semantic_governance/generate.py
Generate the semantic layer, BI, catalog sync, access model and audit files for one domain's slice (cost belongs to the separate cost tool since 4 Nov 2026; the jobs keep the tag convention, governance.tables.COMPUTE_TAGS). Semantic layer
realms/databricks/semantic_governance/render.py
Databricks rendering of the kernel's semantic, BI, governance and access definitions (product names live here). Semantic layer
realms/databricks/tasks/checks.py
The day's checks on Databricks. Every result carries the run id, so the evidence view joins them to the run log. none yet
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
run_checksfunction, line 20 | none found in the code | no test names it | |
detectorsfunction, line 61 | SIM-01: each planted incident is noticed on its day, and nothing fires on a clean day. | run_checks · realms/databricks/tasks/checks.py:46 | test_obs_steps.py |
metric_viewfunction, line 97 | SERV-04: the business definition lives in one place, and it agrees with the gold table. | run_checks · realms/databricks/tasks/checks.py:57 | test_semantic_governance.py, test_governance_catalog.py and 2 more |
realms/databricks/tasks/main.py
Slice 1 job steps on Databricks. One entry file; the job calls it once per step. none yet
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
argsfunction, line 19 | module level · realms/databricks/tasks/main.py:31 | no test names it | |
step_resetfunction, line 49 | module level · realms/databricks/tasks/main.py:166 (value) | no test names it | |
step_preparefunction, line 57 | module level · realms/databricks/tasks/main.py:166 (value) | no test names it | |
probe_platformfunction, line 92 | DE-057: which system tables this workspace exposes. Cost, audit and lineage depend on them. | step_prepare · realms/databricks/tasks/main.py:63 | no test names it |
step_landfunction, line 110 | module level · realms/databricks/tasks/main.py:166 (value) | no test names it | |
step_finishfunction, line 121 | module level · realms/databricks/tasks/main.py:166 (value) | no test names it | |
metric_view_sqlfunction, line 142 | step_finish · realms/databricks/tasks/main.py:131 | no test names it |
realms/databricks/v1/tasks/paths.py
Where the V1 jobs meet: the landing volume the feeder writes and ingestion reads, and the folders the proof driver and the platform tasks pass files through. One catalog per environment and layer (ADR-012). none yet
| Definition | What it does (its own first sentence) | Called by | Named in tests |
|---|---|---|---|
landingfunction, line 5 | none found in the code | test_azure_adapters.py, test_cloud_adapters.py and 13 more | |
hopsfunction, line 9 | none found in the code | no test names it | |
sourcesfunction, line 13 | none found in the code | test_semantic_governance.py, test_end_to_end.py and 20 more | |
reportsfunction, line 17 | none found in the code | test_azure_adapters.py, test_hop_reports.py and 6 more |