# Map task dependencies as concrete contracts

Illustrative planning brief; no automatic product import.

Illustrative case: a report interface depends on an API response, and QA depends on a test dataset. Both dependencies are called “backend ready.”

## Decision

Allow downstream work to begin against an agreed response example; reserve final acceptance for verified live test behavior.

## Owned work

- Agree the response contract
  - Owner role: API owner
  - Acceptance evidence: An example response defines required fields, empty results and the agreed failure state.
- Prepare independent test data
  - Owner role: QA owner
  - Acceptance evidence: A synthetic dataset covers the response cases and is available through approved test tooling.
- Verify the integrated contract
  - Owner role: UI owner
  - Acceptance evidence: The interface behavior is checked against the actual test response before acceptance.

## Workflow

1. Name the deliverable at each dependency edge.
2. Ask the receiving owner what evidence is sufficient to start work and to accept it.
3. Review contract changes with downstream owners before they invalidate completed work.

## Judgment

A mock can support parallel implementation but does not establish successful production integration.


## Filled illustrative decision

The fictional UI owner receives a sample response containing a report title and total. QA receives a distinct test dataset with an empty-result case. UI planning can start against that agreed contract, but final acceptance still waits for the real test service and dataset to produce the specified behavior.


## Workflow questions

### Must every dependency stop all downstream work?

No. Distinguish the evidence needed to start from the evidence needed to accept. An agreed contract may allow safe parallel work.

### How do we find circular dependencies?

Follow each required deliverable back to its owner. If two tasks require each other to start, choose a smaller contract or investigation to break the loop.

## Product connection

Describe the required deliverable and its acceptance check before representing task dependencies in the workflows available to your account.

Confirm account availability before adopting this manual outline.