Development record
The consistency ingest's refusal for findings whose policy hashes the request never issued tells the auditor to echo the two values the request's Provenance block states, and never names the re-emit. For a request emitted by an earlier binary (before the findings shape joined the prompt body) the auditor DID echo them, so the remedy it gives cannot succeed: the only way through is to re-emit with abcd intent consistency and run the pass again. The sibling refusal in the fidelity ingest (checkIssuedPolicy) names the re-emit; the two should share one derivation of that wording.
The consistency ingest's refusal for findings whose policy hashes the request never issued tells the auditor to echo the two values the request's Provenance block states, and never names the re-emit. For a request emitted by an earlier binary (before the findings shape joined the prompt body) the auditor DID echo them, so the remedy it gives cannot succeed: the only way through is to re-emit with abcd intent consistency and run the pass again. The sibling refusal in the fidelity ingest (checkIssuedPolicy) names the re-emit; the two should share one derivation of that wording.
Grounds
- pursued: an auditor answering a request an earlier binary wrote is told to re-emit rather than to echo again; a consistency refusal for unissued hashes that names no re-emit, or names one spelled without the receipt's scope, would show it wrong
Frontmatter
| id | iss-2609262104070666 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2609262104070666-the-consistency-ingest-s-refusal-for.md
open on GitHub ↗ · commit history ↗