Constrain what the architect may read when it designs a decision record, so the record's inputs are the ones the command actually gave it.
Meta
The command lists its inputs for the architect, but nothing stops the architect from reading further material off disk. A live run hit exactly this: a discovery folder was still present in the working tree, the architect read it directly, and the resulting record cited a decision that had never reached the epic issue as a comment. Nothing was contradicted, but the provenance could not be established, because the reasoning was available by two routes at once. In the ordinary lifecycle the folder is gone by the time the record is written, so this rarely bites. It is an input-discipline gap rather than a defect in any one stage, and it applies to every input the phase resolves, not only to discovery.
Constrain what the architect may read when it designs a decision record, so the record's inputs are the ones the command actually gave it.
Meta
The command lists its inputs for the architect, but nothing stops the architect from reading further material off disk. A live run hit exactly this: a discovery folder was still present in the working tree, the architect read it directly, and the resulting record cited a decision that had never reached the epic issue as a comment. Nothing was contradicted, but the provenance could not be established, because the reasoning was available by two routes at once. In the ordinary lifecycle the folder is gone by the time the record is written, so this rarely bites. It is an input-discipline gap rather than a defect in any one stage, and it applies to every input the phase resolves, not only to discovery.