Skip to main content

Reference

This page is the long-form map of the repository areas client teams are most likely to use.

Where to work first​

  • datacontracts.rockdata.nl for source-model meaning, schema intent, and contract-driven expectations.
  • databricks_example/ for Databricks configuration, contracts, notebooks, jobs, and deployment inputs.
  • fabric_example/ for Fabric configuration, contracts, notebooks, jobs, and deployment inputs.

Databricks reference surface​

  • databricks_example/data_contracts/ for contract files used in the Databricks implementation.
  • databricks_example/notebooks/ for notebook entry points and platform execution flow.
  • databricks_example/jobs/ for orchestration and scheduling configuration.
  • databricks_example/asset_bundle_compute/ for bundle-related compute configuration.

Platform-maintained repo surfaces​

  • libs/ contains the shared platform packages and adapters.
  • infra/ contains reusable infrastructure assets.
  • documentation_app/ contains the published docs shell and generated site assets.

Most client teams will read these areas more often than they edit them.

When to use the Accelerator capabilities browser​

Open the Accelerator capabilities browser when you want a fast, visual way to explore the available surface area and jump into exact symbols. Stay on this page when you need the higher-level map of where responsibility lives before drilling into implementation details.

Last updated on