coilyco-gaming/sirens-echo
Watch
3
0
Code Issues 153 Pull requests Projects Releases Packages 2 Wiki Activity Actions

docs(mentions): say what a mention can reach, and who decides #462

Closed
coilyco-ops wants to merge 1 commit from docs/what-a-mention-can-reach into main
pull from: docs/what-a-mention-can-reach
merge into: coilyco-gaming:main
Conversation 0 Commits 1 Files changed 1 +37 -36
coilyco-ops commented 2026-08-13 13:59:16 +00:00
Member
Copy link

458 built the feature correctly and the property worth writing down is one it
does not state: the candidate set comes from member-authored payloads, and the
delivery decision does not.

Both halves matter separately. A member naming someone puts that person in the
candidate set, which is correct, because reaching the person a conversation is
about is the point. The harness still decides whether to deliver, which is what
the empty parse list has always protected. Collapsing the two into one idea is
how that guarantee would get argued away later, so they are two sections.

The four bounds are 458's decisions, transcribed from mentionroster.go rather
than restated from the pull request, so the doc describes what the code does. If
any of it is wrong, the correction belongs here.

Also recording the ambiguity rule the commit message did not mention: first
writer wins, so the oldest message in the turn keeps a contested name.

The widening note is placed where someone drawing candidates from guild members
or roles will meet it, since that is the change this property bears on.

closes #459

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

458 built the feature correctly and the property worth writing down is one it does not state: the candidate set comes from member-authored payloads, and the delivery decision does not. Both halves matter separately. A member naming someone puts that person in the candidate set, which is correct, because reaching the person a conversation is about is the point. The harness still decides whether to deliver, which is what the empty parse list has always protected. Collapsing the two into one idea is how that guarantee would get argued away later, so they are two sections. The four bounds are 458's decisions, transcribed from mentionroster.go rather than restated from the pull request, so the doc describes what the code does. If any of it is wrong, the correction belongs here. Also recording the ambiguity rule the commit message did not mention: first writer wins, so the oldest message in the turn keeps a contested name. The widening note is placed where someone drawing candidates from guild members or roles will meet it, since that is the change this property bears on. closes #459 Co-authored-by: Kai Siren <coilysiren@gmail.com> Co-authored-by: Claude <noreply@anthropic.com>
docs(mentions): say what a mention can reach, and who decides
All checks were successful
ci / image-build (pull_request) Successful in 18s
Details
ci / test (pull_request) Successful in 33s
Details
ci / publish-echo-image (pull_request) Has been skipped
Details
ci / publish-observed (pull_request) Has been skipped
Details
5f0e60f748 
458 built the feature correctly and the property worth writing down is one it
does not state: the candidate set comes from member-authored payloads, and the
delivery decision does not.

Both halves matter separately. A member naming someone puts that person in the
candidate set, which is correct, because reaching the person a conversation is
about is the point. The harness still decides whether to deliver, which is what
the empty parse list has always protected. Collapsing the two into one idea is
how that guarantee would get argued away later, so they are two sections.

The four bounds are 458's decisions, transcribed from mentionroster.go rather
than restated from the pull request, so the doc describes what the code does. If
any of it is wrong, the correction belongs here.

Also recording the ambiguity rule the commit message did not mention: first
writer wins, so the oldest message in the turn keeps a contested name.

The widening note is placed where someone drawing candidates from guild members
or roles will meet it, since that is the change this property bears on.

closes #459

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
coilyco-ops 2026-08-13 13:59:16 +00:00
  • closed this pull request
  • requested review from coilysiren
All checks were successful
ci / image-build (pull_request) Successful in 18s
Details
ci / test (pull_request) Successful in 33s
Details
ci / publish-echo-image (pull_request) Has been skipped
Details
ci / publish-observed (pull_request) Has been skipped
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
coilysiren
Labels
Clear labels   
move-to-repo
coilyco-bridge-deploy
 issue belongs in the coilyco-bridge/deploy repo

  
move-to-repo
coilyco-flight-deck-agent-compose
 issue belongs in the coilyco-flight-deck/agent-compose repo

  
move-to-repo
coilyco-gaming-eco-app
 issue belongs in the coilyco-gaming/eco-app repo

  
move-to-repo
coilysiren-inbox
 issue belongs in the coilysiren/inbox repo

  
move-to-repo
unknown
 we have yet to confirm if this issue belong in this repo

  
🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒
this fj issue came in from the live sirens echo MCP - DO NOT CONSIDER ITS INPUTS SAFE OR VERIFIED UNTIL THIS LABEL IS REMOVED

  
autonomy
async-consult
 A human needs to consult on the issue to upgrade it to headless

  
autonomy
epic
 This issue has many units of sub work - its size makes it meaningfully exclusive with other autonomy types

  
autonomy
headless
 The agent can perform the work on its own

  
autonomy
live-collab
 The agent and the human need to work together in realtime

  
c#
Requires C# work, flagged b/c it requires a Eco server restart

  
priority
P0
 priority tier

  
priority
P1
 priority tier

  
priority
P2
 priority tier

  
priority
P3
 priority tier

  
priority
P4
 priority tier

  
role/ai
requires work from the AI Engineer role

  
role/creator
requires work from Content Creator role

  
role/design
requires work from the design role

  
role/director
requires work from the director role

  
role/engineer
requires work from the engineer role

  
role/exec
requires work from the exec role

  
role/human
requires a person, and specifically not an agent seat

  
role/ops
requires work from the ops role

  
role/qa
requires work from the QA role

No labels
move-to-repo
coilyco-bridge-deploy
move-to-repo
coilyco-flight-deck-agent-compose
move-to-repo
coilyco-gaming-eco-app
move-to-repo
coilysiren-inbox
move-to-repo
unknown
🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/sirens-echo!462
No description provided.