# Release dependency map

By Ocula · Updated 23 September 2026
Guide: https://www.ocula.dev/guides/release-dependency-map/

## Release outcome

What needs to be available, to whom, and by when?

## Blank dependency record

Copy this block once per dependency. Keep need-by and agreed dates separate.
Include timezones where timing matters. Add links to the actual source records.

Dependency / required outcome:
Consumer owner:
Provider owner:
Needed by (include timezone):
Provider-agreed date:
Acceptance criteria / scope:
Evidence links and last checked:
Constraint / conflicting commitment:
Status and unresolved question:
Next action / owner / check time:
Verified outcome / learning:

## Suggested status labels

- Unconfirmed: a dependency is identified but an owner or agreement is missing.
- Confirmed: the relevant owners agree the scope and date; the outcome may still be ahead.
- Conflicting: records or commitments disagree; state the unresolved question.
- Resolved: the required condition has been met and checked against its acceptance criteria.

## Worked example: Atlas launch

- **Dependency / required outcome:** EXAMPLE: two Platform engineers available for the Atlas launch
- **Consumer owner:** Atlas release lead
- **Provider owner:** Platform lead
- **Needed by (include timezone):** Monday (example; replace with date and timezone)
- **Provider-agreed date:** Unconfirmed until migration reschedule is agreed
- **Acceptance criteria / scope:** Two Platform engineers allocated to support the customer launch
- **Evidence links and last checked:** Customer launch thread; Platform capacity plan; migration ticket (replace with links and check time)
- **Constraint / conflicting commitment:** The migration needs the same engineers on Monday
- **Status and unresolved question:** Conflicting: approval and owner agreement to move migration still open
- **Next action / owner / check time:** Release lead seeks priority decision; Platform lead updates plan and confirms with both owners; set check time
- **Verified outcome / learning:** Pending: verify updated dates, owner acknowledgements and launch allocation

### Decision and trade-off

Keep Monday's customer launch and move the migration to the following week.
Migration benefits arrive a week later. This needs approval and affected owners' agreement.
The Platform lead's confirmation of next week's capacity has been checked against the plan.
That check alone does not approve the move.

### Close when

The agreed dates are recorded, both owners acknowledge them and Monday's launch support is allocated.
This verifies the coordination outcome; the launch itself may still be ahead.

## When to review

Recheck when the date, scope, owner, available capacity or customer commitment changes.
If records conflict, ask which one needs updating. For an unanswered question, name an owner
and a check time. After release, retain the useful dependency and outcome, then check whether
they still apply on the next initiative.