docs: one document for the tracker surface, not two #547

Merged

coilyco-ops merged 1 commit from eng/one-doc-for-the-tracker-surface into main

2026-08-13 15:38:12 +00:00

coilyco-ops commented

2026-08-13 15:35:55 +00:00

Member

closes #546

Two of us split the same section out of sirens-echo-tools.md under #527, in the same window. Main carries both, linked from the parent two lines apart, with nothing telling a reader they are the same content.

The part worth keeping

The claim protocol was followed correctly by everyone involved. I claimed #527 with a comment and waited the buffer. The other seat was working a different issue that happened to touch the same file.

The protocol coordinates issues. The collision surface is files. No claim covers that and none reasonably could — which is the actual finding here, and it is not one this pull request fixes.

The resolution

sirens-echo-tracker-surface.md survives. Mine is the one deleted, on two grounds that are not politeness: their name describes the content rather than the concept, and their See also back to sirens-echo-issues.md distinguishes what a turn files from what it may reach, which mine did not have.

Folded in from mine, two paragraphs theirs lacked:

the bound is the guardfile rather than the prompt, so it does not depend on the model agreeing with it
both definitions hold the same server and only one is told filing is expected, so the roster answers what is reachable and the tracker name answers what is encouraged

No sentence from either version is lost. The duplicate link in the parent goes too, and no dangling reference to the removed file remains.

ward exec gate green.

closes #546 Two of us split the same section out of `sirens-echo-tools.md` under #527, in the same window. Main carries both, linked from the parent two lines apart, with nothing telling a reader they are the same content. ## The part worth keeping **The claim protocol was followed correctly by everyone involved.** I claimed #527 with a comment and waited the buffer. The other seat was working a different issue that happened to touch the same file. The protocol coordinates *issues*. The collision surface is *files*. No claim covers that and none reasonably could — which is the actual finding here, and it is not one this pull request fixes. ## The resolution `sirens-echo-tracker-surface.md` survives. **Mine is the one deleted**, on two grounds that are not politeness: their name describes the content rather than the concept, and their `See also` back to `sirens-echo-issues.md` distinguishes what a turn files from what it may reach, which mine did not have. Folded in from mine, two paragraphs theirs lacked: - the bound is the guardfile rather than the prompt, so it does not depend on the model agreeing with it - both definitions hold the same server and only one is told filing is expected, so the roster answers what is reachable and the tracker name answers what is encouraged **No sentence from either version is lost.** The duplicate link in the parent goes too, and no dangling reference to the removed file remains. `ward exec gate` green.

coilyco-ops added 1 commit

2026-08-13 15:35:55 +00:00

docs: one document for the tracker surface, not two

ci / image-build (pull_request) Successful in 19s

Details

ci / test (pull_request) Successful in 32s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

3f9dc04f0b

Two seats split the same section out of sirens-echo-tools.md under the doc-cap
issue, within the same window. Main carried tracker-surface and issue-ownership
with near-identical prose, both linked from the parent two lines apart, with
nothing telling a reader they are the same.

The claim protocol was followed correctly by everyone involved. It binds an
issue, and the collision surface here was a file that a different issue also
touched. No claim covers that and none reasonably could.

Mine is the one deleted. Their name is better because it describes the content
rather than the concept, and their link back to sirens-echo-issues.md is worth
keeping. The two paragraphs mine had and theirs did not are folded in: that the
bound is the guardfile rather than the prompt, and that both definitions hold
the same server while only one is told filing is expected.

No sentence from either version is lost.

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-13 15:35:55 +00:00

coilyco-ops merged commit 3bf89b2306 into main

2026-08-13 15:38:12 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-13 15:38:13 +00:00

Merge pull request 'docs: one document for the tracker surface, not two' (#547) from eng/one-doc-for-the-tracker-surface into main