docs(mentions): the candidate set is member-influenced, the decision is not

coilyco-ops commented

2026-08-13 14:02:01 +00:00

Member

458's doc says the roster is the conversation and that widening to guild members
is a change of source. What it does not say is that two of the three sources are
member-authored, so a member naming someone puts that person in the candidate
set.

That is correct for the feature and it is not obvious from the section. Reaching
the person a conversation is about is the point, and the harness still decides
whether to deliver. The two are separate and the distinction is the whole of the
empty-parse guarantee: collapsing them into one idea is how that guarantee would
get argued away later.

Placed in the roster section rather than a new one, so someone reading about
widening meets it in the paragraph that invites the widening.

closes #459

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

458's doc says the roster is the conversation and that widening to guild members is a change of source. What it does not say is that two of the three sources are member-authored, so a member naming someone puts that person in the candidate set. That is correct for the feature and it is not obvious from the section. Reaching the person a conversation is about is the point, and the harness still decides whether to deliver. The two are separate and the distinction is the whole of the empty-parse guarantee: collapsing them into one idea is how that guarantee would get argued away later. Placed in the roster section rather than a new one, so someone reading about widening meets it in the paragraph that invites the widening. closes #459 Co-authored-by: Kai Siren <coilysiren@gmail.com> Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops added 1 commit

2026-08-13 14:02:01 +00:00

docs(mentions): the candidate set is member-influenced, the decision is not

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

Details

ci / test (pull_request) Successful in 34s

Details

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

Details

ci / publish-observed (pull_request) Has been skipped

Details

6802d4205e

458's doc says the roster is the conversation and that widening to guild members
is a change of source. What it does not say is that two of the three sources are
member-authored, so a member naming someone puts that person in the candidate
set.

That is correct for the feature and it is not obvious from the section. Reaching
the person a conversation is about is the point, and the harness still decides
whether to deliver. The two are separate and the distinction is the whole of the
empty-parse guarantee: collapsing them into one idea is how that guarantee would
get argued away later.

Placed in the roster section rather than a new one, so someone reading about
widening meets it in the paragraph that invites the widening.

closes #459

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

coilyco-ops requested review from coilysiren

2026-08-13 14:02:01 +00:00

coilyco-ops merged commit 677b154a36 into main

2026-08-13 14:03:00 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-13 14:03:02 +00:00

Merge pull request 'docs(mentions): the candidate set is member-influenced, the decision is not' (#464) from docs/the-roster-is-member-influenced into main

coilyco-ops referenced this pull request

2026-08-13 14:06:12 +00:00

A display name matching a URL component rewrites the URL, so naming a member breaks every link containing their name #465

coilyco-ops referenced this pull request

2026-08-13 15:33:57 +00:00

feat(startup): report which optional capabilities are configured #544

Rows
Columns

docs(mentions): the candidate set is member-influenced, the decision is not #464