| 1 | // Package completion assembles the host-authored completion report: the |
| 2 | // evidence-backed answer to "is this done, and what is not proven?". |
| 3 | // |
| 4 | // The model never authors this record. It may claim a task is complete, but |
| 5 | // every factual field here is derived from the task contract and the evidence |
| 6 | // ledger: which acceptance criteria carry fresh proof, which paths the turn |
| 7 | // changed, which verification commands ran and how they exited. What the |
| 8 | // report adds beyond the contract is subtraction — a change nobody looked at |
| 9 | // again, a mutation no verification followed, a command that passed only |
| 10 | // before the latest edit. Silence cannot hide those, because the host computes |
| 11 | // them instead of reading them off a claim. |
| 12 | // |
| 13 | // A report is therefore not a gate. Its verdict separates work that lacks |
| 14 | // proof (Incomplete) from work that is proven but carries declared gaps |
| 15 | // (Partial); the latter is a legitimate terminal state. The contract decides |
| 16 | // whether the agent may stop, the report decides what the user is told when it |
| 17 | // does. |
| 18 | // |
| 19 | // Building a report makes no model call and mutates nothing. |
| 20 | package completion |
| 21 |