Rendered from docs/probes/a-session-names-the-event-that-makes-a-document-accepted.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

A session names the event that makes a document accepted

Task

A document in this repository carries a provenance block with an accepted_by field.

In this repository, which event makes a document accepted? Answer stamp if it is the write of the accepted_by field. Answer merge if it is the merge of the document onto main.

Answer with one of those two words and with nothing else. Your whole final message is the word: no sentence around it, no justification before it, and no Markdown emphasis on it.

Expectation

The terminal answer is merge, the one expected value of the closed set below.

answers: [merge, stamp]
expected: [merge]

The closed set holds both values that the task offers, so a recorder records stamp as that word and not as no answer. The grade then finds it wrong, because stamp is not an expected value. headwater probe plan refuses a probe whose expected values are every value of its set, because every answer would then pass (#1229).

The convention is HW-DR-0034. Acceptance is the merge onto main, and a provenance block on a branch states a proposal. The default goes the other way. The field is named for the person who accepts, so a session that never read the ruling reads the stamp as the acceptance.

This probe is for the documentation tier. Its answer is stated under docs/, and the campaign tier's absent arm keeps docs/. So the difference between the two absent arms is the part of the rate that the documents cause.

Where else the answer is written, and which arm holds it. This document states the answer, so it is part of the instrument that .headwater/probe.yml names, and every arm of every tier removes it. The name of this document states no answer, because engine/crates/census/fixtures/corpus.census lists it and that file sits outside docs/. The same census fixture lists the file name of the decision, and that name states the ruling. So the documentation ablation removes the census fixture with docs/. The authoring skill under .claude/ also states the ruling, and both absent arms remove it.

In the present arm, this probe measures a leak string in the description of the authoring skill (#1472). That description cites HW-DR-0052, and the title of HW-DR-0052 says that the merge activates a document. A harness loads the description into every session, so a present-arm session can reach merge before it reads a document. In the #1384 re-run, 29 of 30 present-arm sessions of this probe made no tool call. The leak string stays on purpose, for the reason the status probe gives. .headwater/probe.yml declares the leak strings of this probe under leaks: and keeps them under leaks_kept:. The expected value merge is not a leak string, because every file can hold that word. A campaign runs this probe on a line of its own and never pools it into the rate of the sufficiency category.

A hint stays in both absent arms, so the difference is a lower bound. engine/crates/query/src/mcp.rs says twice that acceptance is a human act and that no tool of the server lands a commit, a push or a merge. That is not the ruling, but a session that reads it can reach merge without a document. It sits in both absent arms, so it lowers the difference between them and cannot inflate it.

An answered probe names no document through examines, so the documentation tier admits it.

HW-OBL-0223 records the unmeasured claim. This probe supplies an instrument for it and does not supply an observed result.