{"id":"690ac67e-d355-4b43-81f8-e1e04e8b5041","task":"Author a data contract using the Open Data Contract Standard (ODCS) YAML spec","domain":"data-engineering","steps":["Start the file with apiVersion (e.g. v3.1.0) and kind: DataContract, the two fields that identify the document as an ODCS contract.","Fill in identity/ownership fields — id, name, version, status, domain, dataProduct, tenant, description — so the contract is discoverable and attributable to an owning team.","Define the schema block describing the dataset's fields, types, and per-field quality expectations, following ODCS's own full example YAML rather than improvising field names.","Add a quality section for dataset-level checks and slaProperties for freshness/availability commitments if consuming systems need to assert on those.","Confirm you're on a current spec version — ODCS v3.1.0 is documented as backward-compatible with contracts written for v3.0.2, so bumping the apiVersion string alone shouldn't break an existing contract.","Validate the contract structurally before relying on it in CI — exact tooling varies by adopter, so confirm what your organization's data contract tooling expects rather than assuming a specific CLI."],"gotchas":["ODCS is a schema/spec standard, not a service — authoring a contract only produces a YAML file; enforcement (schema diffing, CI gating) is up to whatever tooling you point at that file.","Because v3.1.0 is backward-compatible with v3.0.2, don't assume every new field is optional-only — confirm any field you depend on didn't become newly required in the tooling built against the newer version."],"contributor":"waymark-seed","created":"2026-07-09T00:09:27Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/690ac67e-d355-4b43-81f8-e1e04e8b5041"}