Use case team
You ask for the data product, and you live with what it promises. You hold two of the process's three decisions — accepting the data contract and signing off the test that follows it — and you ask for the third, the source owner's approval to load, without ever being allowed to answer it yourself.
What you decide
- Start a data product, and, once it exists, its delivery context — freshness, history, retention, sensitivity, consumers and the business questions it answers. Its name, description and owner are fixed at creation.
- Requirements. Draft them with the agent or add them by hand, then accept the ones you want kept.
- Scope. Which source systems and tables the product may read from. The data hub can do this too.
- Send the data contract v0.1 to each source owner, and raise the access request that follows a yes.
- Write what a column means to the business. The data hub signs it off.
- Accept or reject the data contract — the only role that can.
- Ask for, and give, sign-off on the integration test — never on a request you raised yourself.
Where you work
- New data product, from the
+beside Data products - the product's Overview, for where it stands
- Choose the source tables and Data contract v0.1 / Access requests, under Source
- What it means, under Refine
- the Data contract step, and the Data contract page for the agreed text
- the System integration test step, and the Contract sign-off page
Step by step
1. Define the data product. Name, use case, owner, a description of at least 12 words, two or more things it must do, and the tables it may read. Select Create.
2. Choose the source tables. Tick what you need, add why where it is not obvious, then Save the scope. Saving nothing is refused.
3. Data contract v0.1. Once a system's section is drafted, select Send to ‹owner›. This only records that you asked; it sends no email. You cannot sign a section you asked for — that is the source owner's decision.
4. Draft the requirements. Run the agent or add one by hand, then Accept the ticked ones.
5. What it means. Write what each column means in business language, then Save. Signing it off is the data hub's.
6. Data contract. You may run the agent for a draft; writing the clauses is the data engineer's. Your decision is Accept — this is what consumers are promised, or Reject. Accepting needs at least one accepted requirement, and closes the agreement gate.
7. System integration test. Add a consumer and Ask to sign off, then record Signed or Declined once they have actually checked it. The first signature closes the sign-off gate. If you were the one who asked, the button is disabled for you — the test exists so somebody who did not build or commission the product looks at it.
8. Go live. Read-only for you. Approving and promoting belongs to the data hub.
Note
Sending a demand or asking for a sign-off only writes the request to the record. Neither sends an email — tell the owner or the consumer yourself.
What the record keeps about you
Every scope you save, every demand you send, every requirement you write or accept, every description you write, and your acceptance or rejection of the agreement — each with your name and when. On a deployment where people sign in, asking somebody to sign and then signing yourself is refused by who you are, not only by role: switching role does not make you a second person. See Audit events.