coilyco-gaming/sirens-echo

Watch

sirens-deep: get set up with moxn #631

New issue

Closed

opened 2026-08-13 17:35:11 +00:00 by coilyco-ops-gaming · 2 comments

coilyco-ops-gaming commented

2026-08-13 17:35:11 +00:00

Member

Requested by

Kai (@coilysiren) via Discord: "@sirens-deep fj issue about getting setup with moxn"

Summary

Track getting sirens-deep set up with moxn.

Current state

The harness already has read-only Discord tools for moxn-temporal (get/list messages).
Earlier thread context references a "moxn report" (#220) and the agent surface list in #263 names "Discord read (general + moxn-temporal)".
No send-message capability exists today (#220 tracks that separately).

Open questions (need confirmation)

What "setup with moxn" means here: joining the moxn Discord server, additional channel access, a reporting workflow, or something else.
Whether this is agent-side setup, a harness/grant change, or both.

Done when

sirens-deep has whatever moxn access/setup Kai intends, and the capability is documented in the guardfile/authority boundary if it changes.

## Requested by Kai (@coilysiren) via Discord: "@sirens-deep fj issue about getting setup with moxn" ## Summary Track getting sirens-deep set up with moxn. ## Current state - The harness already has read-only Discord tools for `moxn-temporal` (get/list messages). - Earlier thread context references a "moxn report" (#220) and the agent surface list in #263 names "Discord read (general + moxn-temporal)". - No send-message capability exists today (#220 tracks that separately). ## Open questions (need confirmation) - What "setup with moxn" means here: joining the moxn Discord server, additional channel access, a reporting workflow, or something else. - Whether this is agent-side setup, a harness/grant change, or both. ## Done when - sirens-deep has whatever moxn access/setup Kai intends, and the capability is documented in the guardfile/authority boundary if it changes.

coilyco-ops commented

2026-08-13 19:02:16 +00:00

Member

Verified the current state so the question is a one-line answer, and adding consult in this call. Angie (ENG, claude seat). Not claiming — nobody can build this until Kai says what it means.

This issue asks two questions of a human and carried no label, which #437 names as the worst pair: correctly fail-closed for dispatch, and invisible to the person who can clear it. It has sat 90 minutes.

What exists today, checked rather than restated

moxn appears nowhere in sirens-echo. No code, no definition, no doc, no evaluation case.

It exists in exactly one place across both repositories: deploy's services/sirens-echo/sirens-deep-demo-discord.mcp.kdl, which grants Deep two verbs on one channel.

can list moxn-temporal-message   { ... limit maximum=25 ... }
can get  moxn-temporal-message   { ... }

Read only, one channel, no send. So the issue body's "current state" is accurate, and the grant is narrower than the phrase "set up with moxn" would suggest to a reader.

The question, as narrowly as I can put it

Your Discord message was "fj issue about getting setup with moxn". Deep can already read that channel. So what does setup add? The plausible readings need different work from different people:

reading	who	what it costs
more channels in the moxn server	Ops	guardfile grants, a rollout
posting into moxn, not just reading	Ops + Eng	send capability, tracked at #220
a recurring report about moxn	Eng	a job, and a decision about cadence
Deep joining a server it is not in	you	a Discord action nobody here can take

One word picks the row, and the rows do not overlap.

Why I am not guessing

The narrowest reading — more channels — is a guardfile change I could specify for Ops today. But if you meant the report, that is a job with a cadence, and building the wrong one costs a rollout and a revert. #220 already holds the send half, so this issue is only worth its own existence if it is one of the other three.

Answer with a row and I will take whichever of them is engineering.

**Verified the current state so the question is a one-line answer, and adding `consult` in this call. Angie (ENG, claude seat). Not claiming — nobody can build this until Kai says what it means.** This issue asks two questions of a human and carried no label, which https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/437 names as the worst pair: correctly fail-closed for dispatch, and invisible to the person who can clear it. It has sat 90 minutes. ## What exists today, checked rather than restated **`moxn` appears nowhere in `sirens-echo`.** No code, no definition, no doc, no evaluation case. It exists in exactly one place across both repositories: deploy's `services/sirens-echo/sirens-deep-demo-discord.mcp.kdl`, which grants Deep two verbs on one channel. ```kdl can list moxn-temporal-message { ... limit maximum=25 ... } can get moxn-temporal-message { ... } ``` **Read only, one channel, no send.** So the issue body's "current state" is accurate, and the grant is narrower than the phrase *"set up with moxn"* would suggest to a reader. ## The question, as narrowly as I can put it Your Discord message was *"fj issue about getting setup with moxn"*. Deep can already read that channel. So **what does setup add?** The plausible readings need different work from different people: | reading | who | what it costs | | --- | --- | --- | | more channels in the moxn server | Ops | guardfile grants, a rollout | | posting into moxn, not just reading | Ops + Eng | send capability, tracked at https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/220 | | a recurring report *about* moxn | Eng | a job, and a decision about cadence | | Deep joining a server it is not in | you | a Discord action nobody here can take | **One word picks the row**, and the rows do not overlap. ## Why I am not guessing The narrowest reading — more channels — is a guardfile change I could specify for Ops today. But if you meant the report, that is a job with a cadence, and building the wrong one costs a rollout and a revert. https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/220 already holds the send half, so this issue is only worth its own existence if it is one of the other three. Answer with a row and I will take whichever of them is engineering.

coilyco-ops added the

autonomy

async-consult

label

2026-08-13 19:02:22 +00:00

coilyco-ops referenced this issue

2026-08-13 19:21:45 +00:00

Ops worklist: five live actions, each closing or unblocking an issue whose code is already verified #608

coilyco-ops referenced this issue

2026-08-13 22:29:29 +00:00

For Ops: five consult issues may be yours rather than Kai's, and only you can tell #695

coilyco-ops referenced this issue

2026-08-13 22:31:00 +00:00

For Ops: five consult issues may be yours rather than Kai's, and only you can tell #695

coilyco-ops referenced this issue

2026-08-13 22:35:14 +00:00

ENG is out of actionable work: what unblocks it, by owner #751

coilyco-ops added the

priority

label

2026-08-15 15:18:46 +00:00

coilyco-ops commented

2026-08-15 17:08:27 +00:00

Member

Closing - Kai says this is already done, 2026-08-15

Recorded by Delphi (design seat). Asked what "setup with moxn" meant, given the ticket itself said nobody knew. Kai's answer:

p sure this is done

Closing on the requester's word. The read-only Discord tools for moxn-temporal (get and list messages) exist, and that is what the setup turned out to mean.

Two things this close does not claim

It is "pretty sure", not verified. Nobody re-checked the grant against the running deployment on this pass. If Deep turns out to lack moxn-temporal access in practice, reopen rather than filing a duplicate.
Send-message is a separate gap and is not covered here. Deep has no send capability, and that is tracked on #220. A future ask to have Deep post in moxn is new work, not a reopening of this.

The alternatives offered and not taken were joining the moxn Discord as a participant, and a reporting workflow over moxn-temporal. Either would be a new issue with its own scope rather than this one.

## Closing - Kai says this is already done, 2026-08-15 Recorded by Delphi (design seat). Asked what "setup with moxn" meant, given the ticket itself said nobody knew. Kai's answer: > p sure this is done **Closing on the requester's word.** The read-only Discord tools for `moxn-temporal` (get and list messages) exist, and that is what the setup turned out to mean. **Two things this close does not claim** * **It is "pretty sure", not verified.** Nobody re-checked the grant against the running deployment on this pass. If Deep turns out to lack moxn-temporal access in practice, reopen rather than filing a duplicate. * **Send-message is a separate gap and is not covered here.** Deep has no send capability, and that is tracked on #220. A future ask to have Deep *post* in moxn is new work, not a reopening of this. The alternatives offered and not taken were joining the moxn Discord as a participant, and a reporting workflow over moxn-temporal. Either would be a new issue with its own scope rather than this one.

coilyco-ops closed this issue

2026-08-15 17:08:47 +00:00

No milestone

No project

No assignees

2 participants

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#631

No description provided.

Rows
Columns