Record dependencies instead of a single completion percentage
Synthetic onboarding N-243 contains coordinator confirmation C, sample approval S, configuration G and training T. G requires C and S; T requires G. C is done, S is pending, so neither G nor T is ready. An independent briefing B may proceed. The fixture has no capacity constraint: readiness means prerequisites are satisfied, not that someone is available to do the task.
| Task | Prerequisites | Evidence state | Ready now |
|---|---|---|---|
| G: configuration | C and S | C done; S pending | No |
| T: training | G | G not started | No |
| B: briefing | None in this fixture | Independent agreed task | Yes |
Release newly ready work after each input completes
- Read task dependency list
- Check completion evidence
- Identify ready tasks
- Recheck dependent tasks after completion
A dependency cycle such as G requiring T and T requiring G blocks planning; resolve it before starting either task.
S becomes done while G has not started. Which task becomes newly ready?
Show the worked answer
G becomes ready because C and S are both done. T still waits for G completion; B was already ready.
Dependencies and task letters are synthetic. A completed input does not automatically approve downstream results or reserve delivery capacity.