Eckhund — declared empty slot
What This Record Is
A slot, not a product. The request asked that the vault include the information produced by the operator's Eckhund agent. That material was not supplied with the task and was not found in the file library or the workspace, so this record exists to hold the position open and to make the absence auditable.
No content is recorded here because none was available. Nothing in this vault paraphrases, summarises, reconstructs, or estimates what Eckhund produced.
Why an Empty Record Rather Than No Record
Because an absent component and a component that was never requested look identical in a finished vault. An empty slot with a stated reason distinguishes them: it tells a later reader that the vault is incomplete at a known point, by a known amount, for a known reason — rather than leaving a silent hole that a reader will fill with the assumption that the vault is whole.
This is the same discipline the citation register applies to unretrieved sources, applied to a missing input.
What Would Fill It
The Eckhund output itself, in whatever form it was produced — a report, a transcript, a set of findings. On receipt it would be admitted as an agent_product record with:
provenance— which agent, which run, when, on what prompt.admissibility— what it may be used for. An agent's output is evidence of what the agent produced, not evidence about the world; it does not inherit authority from the vault's primary corpus and must not be merged with it.- Cross-links to whichever of QST-001 through QST-004 it actually addresses.
The admissibility distinction is the reason the extension exists at all. Everything else in this vault is either the discussion's own reasoning or a cited source. An agent product is a third kind of object, and it would be admitted as such rather than quietly promoted to either of the other two.