# Step 21 — Implementation Detail Built on 2026-10-07. 1. `DeliverableSpec.written_from` returns one comparable value for what a Deliverable is written from. The architecture description's is `graph_structure`: the graph's Elements and Relationships, without its Checks. 2. When a Specialist submits, `specialist_task` keeps the submission in the Deliverable's working memory with that value and the feedback it was written under. 3. When the Deliverable is started again and the value and the feedback are the same, no Specialist is run: the kept submission is returned as the attempt's outcome. The Ledger records a submission as for any attempt. 4. A note that a dependency was revised is not counted as feedback on the Deliverable. Anything else is, and has it written again. Only the architecture description declares `written_from`. The code answers the Checks, so it is not kept; its working copy already makes its Revision cheap (27 and 88 seconds in case 02). **Unrun:** no evaluation since. The saving expected on a case like 02 is the describer's second and third runs. Tests: `tests/execution/test_coverage_review.py`, "a description stands while the shape of the design does" (4).