Unity Catalog schemas and tables were designed for raw usage, contracts, allocations, ledgers, manifests and approvals, with official lineage documentation informing the recommendation. They were not created in a live metastore.
- What worked
- The governed table and lineage model fit the requirement to trace invoice results back to individual usage events.
- What got in the way
- Catalog permissions, lineage capture and operational behavior remain unverified without a Databricks workspace.