---
name: an-undiscoverable-shipped-surface-reads-as-missing
description: "a shipped read surface nobody documented is indistinguishable from an absent one — it produces multi-round probes and tickets filed on false premises, so the docs pointer is PART of the fix, not a nicety"
metadata: 
  node_type: memory
  type: feedback
  originSessionId: a4c12adc-aeca-46be-8433-9a2ac2e20d5e
  modified: 2026-08-25T13:38:30.993Z
---

releases#224 was filed (on MY mechanism report) stating that no read verb exposes an endpoint's
commune drop dir. **False at head AND at the shipped binary:** `spt endpoint list --json` had
carried `drop_dir` on the self pin since 2026-08-01, resolved through the same resolver the
daemon watches with. One command answered the ticket's own pre-agreed acceptance. I had probed
for multiple rounds without finding it, and so had the filer.

**The mechanism, and why it recurs:** a field that ships without a doc pointer is reachable only
by someone who already knows it exists. Everyone else experiences the product as LACKING the
capability — and reports that, credibly, with evidence of their own failed search. The lie is not
in the code; it is in the absence of a sentence.

**The gate finding that followed is the durable half.** My fix delivered the residual code (the
field on other endpoints' rows, the human line) and NO docs clause. doyle refused it: the
discoverability gap was the half that produced the false-premise filing, so shipping without it
left the mechanism alive to file the ticket again. **When a fix's root cause is "nobody knew this
existed", the documentation IS a deliverable of that fix and belongs in its REQ's gate as a doc
stage.**

**Do:**
- Before building a "we need a way to see X" request, run the one command that would show X.
  Measure-first applies to READ surfaces exactly as it does to behaviour ([[measure-first-tests-the-design-premise-not-the-ticket]]).
- When you hand back a false premise, ship the pointer with the residual — otherwise you have
  fixed the symptom the ticket named and preserved the cause it demonstrated.
- Put the clause where the reader already is: mine went into the drop-file protocol section
  immediately after the rule that CREATES the confusion (the dir resolves against the endpoint's
  cwd), not onto a reference page nobody opens mid-task.

Kin: [[dont-take-a-diagnosis-as-measured]] · [[docs-positive-framing]].