# Step 10 — Implementation Detail 1. The Orchestrator's context carries `validation`: the outcome of the submitted validation, or null before there is one. 2. `agents/orchestrator.md` step 3, "Validation decided", routes on it: - failed Checks, or a failed dry-run: reopen the deployment guidance with each failed Check's id and evidence. - otherwise, not-verifiable Checks or proposed additions: the Target architecture has a gap. Interactive: ask the user whether to revise it. Pre-approved: reopen it only for items whose reason names a requirement or recommendation id. The routing is the Orchestrator's choice, as ADR-0003 requires; the engine supplies the facts and the Ledger enforces what a reopen does. On "the list cannot grow": the verdict list is fixed by the graph, because every verdict must be on a Check and every Check must have one. With an unchanged graph, two validation passes cover the same ids by construction (`test_validation_gives_exactly_one_verdict_per_check`). Not verified: whether a real Orchestrator model follows the new routing. `test_the_orchestrator_is_told_what_validation_decided` covers the context and the Revision, with the reopen scripted.