upstream-drift: hash store as its own designed issue (silent-revision near-miss evidence attached)

[claude]

Context

Signed-off decision Q10 of the context-engineering integration contract (2026-09-01): the
upstream-drift convention defers content hashing, and prescribes that on a trigger firing "a
hash store becomes its own designed issue, not an inline addition". The corpus pass produced
near-miss evidence recorded in that convention's CHANGELOG 1.6.3 (2026-09-01): the live
building-effective-agents page is silently revised while still datelined Dec 19, 2024 — the
failure class a stored hash would flag — but the deferral's trigger has NOT fired (no
committed stamp was involved). This item is the designed-issue placeholder the deferral asks
for, so the evidence has a durable home before the trigger ever fires.

Proposed work

• When (and only when) the deferral's recorded trigger fires, design the hash store here:
  scope (which stamped claims), serialization (adopt
  plugins/knowledge/reference/citation-shape.md's url + date + sha256 by reference),
  storage location, and verification cadence.
• Until then, accumulate near-miss evidence in comments on this item rather than editing the
  deferral.

Acceptance criteria

• No design work before the trigger fires; the deferral text stays as written.
• On firing: a design doc that reuses citation-shape's serialization by reference.

References

• docs/conventions/upstream-drift/CHANGELOG.md (1.6.3)
• docs/conventions/upstream-drift/README.md ("Drift signal — content hashing, deferred")
• plugins/knowledge/reference/citation-shape.md

---

Generated by Claude Code

[claude]

This was generated by AI during triage.

Decision-ready summary — nothing is actually awaiting a decision here

Lane: autonomous triage, instance vm-triage-202609050304. No labels changed.

The one thing a reader needs to know

This item's own acceptance criteria say:

• No design work before the trigger fires; the deferral text stays as written.
• On firing: a design doc that reuses citation-shape's serialization by reference.

So the correct action today is deliberately nothing. This is a dormant, trigger-gated placeholder whose entire job right now is to exist as a durable home for near-miss evidence. It is doing that job correctly.

The trigger has not fired. The recorded near-miss (upstream-drift CHANGELOG 1.6.3 — the live building-effective-agents page silently revised while still datelined Dec 19, 2024) is exactly the failure class a stored hash would flag, but the deferral's trigger is a committed stamp being involved, and none was.

Reference check

Every path this issue cites resolves in the current checkout, so the item is not rotted:

• docs/conventions/upstream-drift/CHANGELOG.md — present
• docs/conventions/upstream-drift/README.md — present
• plugins/knowledge/reference/citation-shape.md — present

That matters because the two sibling receipts filed the same day (#3565, #3568) both open by noting that the docs/topics/** paths they originally cited are gone. This one's references survived the topic-docs v3.0.0 prune intact.

The decision, with a recommendation

The only genuine question is a bookkeeping one: should an item that is correctly doing nothing carry status: needs-decision?

RECOMMENDED — confirm it as a dormant trigger-gated placeholder and remove status: needs-decision; keep the issue open as the evidence home.

Reasoning: status: needs-decision means awaiting a human or maintainer judgment call. Nothing is awaiting one. The design decision this item will eventually carry is blocked on an external event, not on a person's attention — and there is no judgment a maintainer could usefully make today that the deferral has not already made. Leaving the label on costs real attention: it puts a permanently-parked item in the queue of things a human is expected to clear, every cycle, forever.

Removing it does not weaken the item. It stays open, it keeps accumulating near-miss evidence in comments as instructed, and it re-enters the decision queue the moment the trigger fires.

Alternative a maintainer might prefer — keep the label. Defensible if status: needs-decision is being used here to mean "a design decision lives on this item" rather than "a human is blocked on this now." If that is the intended reading, say so on the issue, because the two readings pull the triage queue in opposite directions and this item is a clean example of the ambiguity.

Either way, one small addition is worth making now: record on this issue what the trigger concretely looks like when it fires — which stamp, in which file, observed how. The deferral names the condition, but a reader arriving in six months with a suspected silent revision should be able to tell from this issue alone whether they are looking at the trigger or at another near-miss. That is a two-line addition and it is the difference between a durable home and a note.

Why the gate was not lifted

There is no delegable work here to lift a gate toward. Marking this agent-ready would invite an autonomous lane to start designing the hash store, which is precisely what the acceptance criteria forbid. The recommendation above is a label correction, not a delegation, and it is left to the owner.

---

Generated by Claude Code

[kyle-sexton]

This was generated by AI during attend-queue.

Closing (operator-approved, 2026-09-27): closing as not planned. This issue is a placeholder whose acceptance criterion forbids design until the trigger fires. The evidence is in the upstream-drift CHANGELOG 1.6.3, and the deferral in the README already names the trigger, so reopen when it fires.