Implementing data contracts using .yml files in your Unity Catalog-enabled workspace is a sound practice, especially as it allows for programmatic use in workflows and aids in governance. Best practices for this approach include:

• Catalog Organization: Segregate data using catalogs based on environment (development, production), teams, or business units. This helps in managing access and maintaining clarity.

• Governance and Access Control: Assign permissions to groups rather than individual users to simplify management. Centralized governance ensures consistency across teams while allowing them to focus on data production and insights.

• Data Contract Contents: Your data contracts should include key attributes like data descriptions, schemas, usage policies, data quality metrics, security guidelines, and service-level agreements (SLAs). This ensures that data consumers have all the necessary information.

• Consumer-Centric Design: Design data contracts with the consumer in mind. Providing supporting assets like notebooks, dashboards, or sample code can enhance understanding and usability.

Your current strategy of storing .yml files alongside the scripts that generate your data products aligns well with these best practices. It facilitates both governance and programmatic access, ensuring that your data products are well-documented and easily consumable by various stakeholders.