Define a data contract between a producing and consuming team: schema, freshness, quality guarantees, and the change process that prevents silent breakage.
Draft a data contract for: {{dataset}} (who produces it, who consumes it for what, past breakages: {{incidents}}). Define: the schema commitment (fields, types, nullability — and which fields are guaranteed vs best-effort), freshness SLA (updated by when, and how staleness is signalled), quality guarantees (uniqueness keys, valid ranges, the checks the producer runs), the change process (additive changes: notice period; breaking changes: migration path + consumer sign-off — the rule that ends silent renames), the incident channel and response expectation, and ownership named on both sides. Trace each clause to one of my past {{incidents}} where possible — contracts written from scars get honoured.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekPull structured data out of messy text — emails, PDFs pastes, reports — into a clean table, with con...
Get the right Excel or Google Sheets formula for your layout — explained part by part, with a worked...
Get a structured first read of pasted data: observations with the numbers cited, trends vs noise sep...
Turn open-ended survey answers into themes and quotes.
Pick the best chart type for what you want to show.
Write or optimise a SQL query from a plain-English description of the data and the question — with t...