# Step 13 — Implementation Detail Built on 2026-10-07. 1. `DeliverableSpec.reads_in_full` names the earlier Deliverables a Specialist reads whole. Left unset it is the Deliverables it depends on. 2. `dependencies_for(kind, deliverables)` gives every other input as its data file alone: `requirements.json`, `components.json` and so on. Those ids are all the Requirements chain checks need, so submission checks are unchanged. 3. Two overrides. The IaC author reads nothing whole: the code is written from `target-architecture.json`. The packager reads everything whole, since the guide is assembled from every Deliverable's prose. 4. A Deliverable given as data can be read whole with `read_deliverable(kind)`, offered only when something was trimmed. Differs from the plan: the plan said "summaries". The data file is used instead. It already exists, is exact, and costs no model call to produce. **Unmeasured:** the plan's acceptance is that describer tokens fall against the step 8 baseline. No evaluation has run. Tests: `tests/execution/test_working_copy.py`, "each Specialist reads what it works from".