ADR-323: A run can tell its inputs apart without keeping them
- Status
-
Accepted
- Date
-
2026-11-18
- Authors
-
Netresearch DTT GmbH
Context
A run records which skill versions each model call carried
(ADR-321), the evidence that applied to them
(ADR-322) and which model answered
(ADR-320). The third cause of a changed answer, a changed
input, was not recorded at the default privacy level. metadata keeps
counts, lengths and names of a step and drops its content
(Run), so two runs whose prompts, tool arguments or
tool results differ only in their text, at equal length, looked the same.
The completion request identity of ADR-271 did not fill the gap:
Completionreturned no identity for a message list holding a tool call or provider-native items, which is every request of an agent run after its first tool round.Request Identity:: fingerprint () - The tool-call terminal attached no request identity at all.
- The identity covers the whole request, so it cannot say which part changed, and it is an unkeyed SHA-256: stored with a run, it would let a reader confirm a guessed request without any key.
Decision
- Keyed digests of the dropped parts, opt-in. With the new setting
privacy.(off by default), a step filtered at theinput Digests metadatalevel keeps a digest of these parts of the content it drops:messages(one per message, with its role, in order),Sent Digests content(the answer),Digest tool,Arguments Digest toolandResult Digest request(item 3). A digest isDigest v1:and the HMAC-SHA-256 of the canonical form of ADR-298, keyed with the installation's encryption key joined with the purposenr_(llm. run. content Run,Content Digests Keyed). The key is never stored with the digests; an installation without an encryption key stores none.Digest - The same input gives the same digest. A message is digested without
the ids a provider generates (tool-call ids and the
tool_of a tool result) and without provider-owned items, and tool arguments are digested decoded, so the order of their keys does not count.call_ id - The request identity is widened and reaches a run only keyed.
Completionnow covers requests with tool calls or provider items, the requests that had no identity before. For them it follows item 2: a tool-call id and theRequest Identity:: fingerprint () tool_of the result answering it become the call's ordinal in the request, which keeps which result answers which call; tool arguments are taken decoded; provider items are left out. Every request that had an identity before keeps exactly its bytes, so ADR-271's benchmark identity is unchanged. The renumbering applies tocall_ id Chatobjects, which is how the extension builds every request; a caller passing raw message arrays with tool calls keeps their ids, and so gets an identity per run. The tool-call terminal attaches the identity of the request it sent, tool schemas included and the extension's ownMessage _-prefixed directives (_capture_) left out, because they are never sent (raw Llm). The answer step carries it asService Manager:: chat With Tools For Configuration () request; the privacy filter never stores it as it is, at any level,Identity fullincluded, and atmetadatawith the setting on stores its keyed digest (request).Digest - Only at the ``metadata`` level, and only of unmasked text.
nonekeeps nothing.redactedkeeps no digest: a digest of the unredacted text would confirm a credential the redactor masked.fullstores the step's text as before and no digest. A step written atredactedand filtered again atmetadata(a provider's stricter ceiling, ADR-270) gets no digest either: its text is masked and truncated, and digests of it would make different inputs equal. The filter marks such a step (content). A step filtered again at a stricter level loses its digests; switching the setting off removes no digest already stored, which goes with retention or a later tightening.Masked - Readable. The run timeline shows each digest by its first twelve hex
digits, messages as
role@digest.
Two departures from the draft that preceded this record: the draft also
digested at redacted (item 4 explains why not), and it recommended
against widening the request identity; it is widened, without what a
provider generates per run, and only the keyed digest of it is stored with
a run (item 3).
Consequences
●● With the setting on, two runs whose inputs differ show different digests for the part that differs, at the default level, without keeping the text (acceptance case 5 of the run-lineage analysis).
● The request identity is defined for tool rounds, so a later evaluation of tool-using requests can be identified by the same function.
◑ Off by default: an installation that does not opt in keeps the record it
had, except that a step stored at redacted carries the content
mark, which the timeline does not show. The step of a model call carries
request in memory and in the live playground, which shows the
full content anyway.
✕ With the setting on, anyone who can read a run and guesses a short or predictable input (a yes or no, a record uid, a templated prompt) can confirm the guess, because the key is the installation's. The setting's label and the data-retention page say so.
◑ Provider items are left out of the identity and the digests, so two requests that differ only in them (a provider's replay of its own earlier reasoning) look the same.
◑ A tool whose result carries a fresh random value differs on every run:
fetch_ fences the page with a per-call nonce, so its
tool and the digest of the message that carries it differ
for the same page.
◑ A step first stored at full and held to metadata later (a
provider's ceiling, a tightened run) has message, answer and tool digests
but no request: full does not store the identity it would be
computed from. Thinking, requested tool calls, tool artifacts and raw
provider bodies get no digest.
◑ A step stored at redacted before this change has no content
mark. If the setting is on and the run's level is later tightened to
metadata, it gets digests of its masked text.
◑ The unkeyed identity is on the response object of a tool round as it is on
a chat response (ADR-271), so a caller's idempotency cache
(Idempotency) holds it with the response, as it holds the
answer.
◑ A message whose text holds invalid UTF-8 (a legacy record read by a tool) has no canonical form, so its step keeps no message digests at all; the other parts are digested as usual.
◑ Digests compare within one installation only.