# Data contracts

Data contracts formalize the format, content, and quality of shared data. Amfelt uses the Open Data Contract Standard (ODCS) to capture these contracts.

- [Authoritative Definitions](/docs/reference/data-contract/authoritative-definitions/index.md): Links to external, authoritative documentation or definitions for an element.
- [Common Types](/docs/reference/data-contract/common-types/index.md): Shared primitive type definitions reused across the schema.
- [Custom Properties](/docs/reference/data-contract/custom-properties/index.md): Extension mechanism for arbitrary key-value metadata not covered by the standard.
- [Data Quality](/docs/reference/data-contract/data-quality/index.md): Quality expectations attached to schema objects and properties: library checks, SQL rules, and custom assertions.
- [Pricing](/docs/reference/data-contract/pricing/index.md): Optional cost information for consuming the data product described by the contract.
- [Schema](/docs/reference/data-contract/schema/index.md): The logical data model of a contract: objects such as tables, views, or topics and the properties, types, and constraints they expose.
- [Server](/docs/reference/data-contract/server/index.md): Where the data physically lives, including the connection target and the per-technology settings for each supported server type.
- [Service Levels](/docs/reference/data-contract/sla/index.md): Service-level agreement properties such as freshness, availability, and retention targets.
- [Support](/docs/reference/data-contract/support/index.md): Communication channels for the contract, such as a support email, chat, or issue tracker.
- [Tags](/docs/reference/data-contract/tags/index.md): Free-form labels used to classify and discover contracts and their elements.
- [Team & Roles](/docs/reference/data-contract/team/index.md): The people accountable for the contract and the access roles available on its servers.