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

Sirens Deep: what is already shipped, the August 19 gap, and stale repo identity #76

New issue
Closed
opened 2026-08-07 18:38:13 +00:00 by coilyco-ops · 3 comments
coilyco-ops commented 2026-08-07 18:38:13 +00:00
Member
Copy link

Corrections

Two earlier claims in this issue were wrong, both from reasoning off issue text and commit subjects instead of reading the tree.

  1. "sirens-deep exists nowhere in the portfolio." Wrong. A sirens-deep workload is deployed and its profile is on main.
  2. "PR #77 is a prerequisite." Wrong, and backwards. See the diff analysis on #73. That branch adds role-intent routing, which #67 and #68 deliberately removed, and merging it would revert the profile architecture.

A third statement needs tightening. This issue previously described Sirens Deep as "the social-persona response profile on a DeepSeek backend." That is imprecise on both halves.

What Sirens Deep actually is on main

agent/sirens-deep.yaml, schema coilyco-harness.agent.v1:

  • identity: CoilyCo
  • audit_role: general
  • response_style: social
  • channel: ""
  • local_skill_roots: [.agents/skills/coilyco-general]
  • mcp_servers: []

docs/response-profiles.md states that the filename "remains the stable deployment selection used by the existing sirens-deep workload," and that the profile is HTTP-only, has no MCP roster, and has no automatic issue tracker.

So sirens-deep is a deployment selector name, and the profile behind it is now the CoilyCo general-purpose social profile, repurposed by bcc5998 on 2026-08-06. It is not a Sirens community persona.

The DeepSeek association is a deployment fact, not a repository fact. The definition names no model. main reads the model tag from AGENT_PROXY_MODEL at runtime. The name traces to 5704293, "refactor: name the DeepSeek profile Sirens Deep," on 2026-08-05.

The real August 19 gap

The demo in coilysiren/inbox#324 needs a Discord agent with tools that talks to other agents and can be evaluated on identity. Measured against agent/sirens-deep.yaml as it stands:

Already there

  • A deployed sirens-deep workload with a stable deployment selector.
  • Deployment-selectable profiles and YAML harness definitions.
  • A social response style.
  • DeepSeek reasoning preserved across tool turns, f869390.

Not there

  • Discord binding. The profile is HTTP-only with channel: "". The demo is a Discord channel.
  • MCP roster. mcp_servers: []. coilysiren/inbox#334 wants tools on this agent.
  • The social media manager persona. The prep call named that specific persona. The current profile is CoilyCo general-purpose, which is adjacent but not the same thing.
  • Agent-to-agent recognition. Kai stated on the call that her agents do not recognize other agents. The demo shape is agents interacting in a shared channel.
  • The identity eval covering itself, other humans, and other agents.

None of that is a refactor. It is profile configuration, a channel binding, an MCP roster, and the eval.

Stale repository identity

The Forgejo description still reads:

Sirens Echo Community harness for the Sirens Discord.

That is already inaccurate. The repository ships two selectable profiles, one of which is a general-purpose CoilyCo harness that is not the Sirens Discord community agent at all. Candidate replacement:

Model-opaque harness for the Sirens Discord and CoilyCo deployments, shipping the Sirens Echo community and Sirens Deep general-purpose profiles.

Kai owns the final wording. The Forgejo repository description is instance metadata rather than a tracked file, and the MCP surface available to agent sessions exposes no repository-edit tool, so that line is a Kai or authorized ops action.

README.md and docs/FEATURES.md were touched by the profile commits and may already be current. Check them in the same pass rather than assuming.

Member-data boundary, unchanged

The August 19 demo runs on Abhay's small purpose-made Discord, not the Sirens community server, so no real member data is in scope for the stream.

Open only if a profile is ever pointed at the real community server on a hosted backend: retention and training terms, whether the community is told which backend answers them, and whether any channel class is excluded. Issue #55's telemetry body-safety contract is unaffected either way.

## Corrections Two earlier claims in this issue were wrong, both from reasoning off issue text and commit subjects instead of reading the tree. 1. **"sirens-deep exists nowhere in the portfolio."** Wrong. A `sirens-deep` workload is deployed and its profile is on `main`. 2. **"PR #77 is a prerequisite."** Wrong, and backwards. See the diff analysis on #73. That branch adds role-intent routing, which #67 and #68 deliberately removed, and merging it would revert the profile architecture. A third statement needs tightening. This issue previously described Sirens Deep as "the social-persona response profile on a DeepSeek backend." That is imprecise on both halves. ## What Sirens Deep actually is on main `agent/sirens-deep.yaml`, schema `coilyco-harness.agent.v1`: * `identity: CoilyCo` * `audit_role: general` * `response_style: social` * `channel: ""` * `local_skill_roots: [.agents/skills/coilyco-general]` * `mcp_servers: []` `docs/response-profiles.md` states that the filename "remains the stable deployment selection used by the existing `sirens-deep` workload," and that the profile is HTTP-only, has no MCP roster, and has no automatic issue tracker. So `sirens-deep` is a **deployment selector name**, and the profile behind it is now the CoilyCo general-purpose social profile, repurposed by `bcc5998` on 2026-08-06. It is not a Sirens community persona. The DeepSeek association is a **deployment fact, not a repository fact**. The definition names no model. `main` reads the model tag from `AGENT_PROXY_MODEL` at runtime. The name traces to `5704293`, "refactor: name the DeepSeek profile Sirens Deep," on 2026-08-05. ## The real August 19 gap The demo in https://forgejo.coilysiren.me/coilysiren/inbox/issues/324 needs a Discord agent with tools that talks to other agents and can be evaluated on identity. Measured against `agent/sirens-deep.yaml` as it stands: **Already there** * A deployed `sirens-deep` workload with a stable deployment selector. * Deployment-selectable profiles and YAML harness definitions. * A social response style. * DeepSeek reasoning preserved across tool turns, `f869390`. **Not there** * **Discord binding.** The profile is HTTP-only with `channel: ""`. The demo is a Discord channel. * **MCP roster.** `mcp_servers: []`. https://forgejo.coilysiren.me/coilysiren/inbox/issues/334 wants tools on this agent. * **The social media manager persona.** The prep call named that specific persona. The current profile is CoilyCo general-purpose, which is adjacent but not the same thing. * **Agent-to-agent recognition.** Kai stated on the call that her agents do not recognize other agents. The demo shape is agents interacting in a shared channel. * **The identity eval** covering itself, other humans, and other agents. None of that is a refactor. It is profile configuration, a channel binding, an MCP roster, and the eval. ## Stale repository identity The Forgejo description still reads: > Sirens Echo Community harness for the Sirens Discord. That is already inaccurate. The repository ships two selectable profiles, one of which is a general-purpose CoilyCo harness that is not the Sirens Discord community agent at all. Candidate replacement: > Model-opaque harness for the Sirens Discord and CoilyCo deployments, shipping the Sirens Echo community and Sirens Deep general-purpose profiles. Kai owns the final wording. The Forgejo repository description is instance metadata rather than a tracked file, and the MCP surface available to agent sessions exposes no repository-edit tool, so that line is a Kai or authorized ops action. `README.md` and `docs/FEATURES.md` were touched by the profile commits and may already be current. Check them in the same pass rather than assuming. ## Member-data boundary, unchanged The August 19 demo runs on Abhay's small purpose-made Discord, not the Sirens community server, so no real member data is in scope for the stream. Open only if a profile is ever pointed at the real community server on a hosted backend: retention and training terms, whether the community is told which backend answers them, and whether any channel class is excluded. Issue #55's telemetry body-safety contract is unaffected either way.
coilyco-ops changed title from Record sirens-deep as a second deploy variant of this harness to sirens-deep: DeepSeek deploy variant, committed for the August 19 Temporal demo 2026-08-07 18:49:48 +00:00
coilyco-ops changed title from sirens-deep: DeepSeek deploy variant, committed for the August 19 Temporal demo to Update repository identity for the Sirens Deep profile already on main 2026-08-07 19:11:18 +00:00
coilyco-ops changed title from Update repository identity for the Sirens Deep profile already on main to Sirens Deep: what is already shipped, the August 19 gap, and stale repo identity 2026-08-07 19:15:11 +00:00
coilyco-ops commented 2026-08-12 11:54:38 +00:00
Author
Member
Copy link

Repository description: already fixed, close that part

Direction from Kai, 2026-08-12 session.

The issue records the description as stale:

Sirens Echo Community harness for the Sirens Discord.

That is no longer what the instance carries. The current description on coilyco-gaming/sirens-echo reads:

A discord community agent harness - home of sirens echo and sirens deep

Which is accurate about both profiles and needs no further wording decision. That item is done — no Kai or ops action is outstanding on it.

What remains here

The issue body itself flags it: README.md and docs/FEATURES.md were touched by the profile commits and may already be current. Check them rather than assuming. That is the only open work item left in this issue that belongs to the engineer.

The August 19 gap, restated against current status

The "Not there" list has moved since this was written. Current disposition of each:

Gap Status
Discord binding #135 — deploy change, engineer opens the PR, Kai merges and verifies
MCP roster Landed. sirens-deep-mcp-roster.yml carries forgejo and steam
The social media manager persona #98 — unblocked as of 2026-08-12, top of queue
Agent-to-agent recognition Still unbuilt. The piece #81's matrix most depends on
The identity eval #81 — now four axes, disclosure added

Agent-to-agent recognition remains the genuinely unbuilt one, and per #81 it is the axis carrying the three-model sweep. Worth naming plainly: it is the item most likely to miss August 19.

Member-data boundary

Unchanged and still correct. The demo runs on Abhay's small purpose-made Discord, not the Sirens community server.

## Repository description: already fixed, close that part Direction from Kai, 2026-08-12 session. The issue records the description as stale: > Sirens Echo Community harness for the Sirens Discord. That is no longer what the instance carries. The current description on `coilyco-gaming/sirens-echo` reads: > A discord community agent harness - home of sirens echo and sirens deep Which is accurate about both profiles and needs no further wording decision. **That item is done** — no Kai or ops action is outstanding on it. ## What remains here The issue body itself flags it: `README.md` and `docs/FEATURES.md` were touched by the profile commits and may already be current. **Check them rather than assuming.** That is the only open work item left in this issue that belongs to the engineer. ## The August 19 gap, restated against current status The "Not there" list has moved since this was written. Current disposition of each: | Gap | Status | | --- | --- | | Discord binding | #135 — deploy change, engineer opens the PR, Kai merges and verifies | | MCP roster | Landed. `sirens-deep-mcp-roster.yml` carries `forgejo` and `steam` | | The social media manager persona | #98 — unblocked as of 2026-08-12, top of queue | | Agent-to-agent recognition | Still unbuilt. The piece #81's matrix most depends on | | The identity eval | #81 — now four axes, disclosure added | Agent-to-agent recognition remains the genuinely unbuilt one, and per #81 it is the axis carrying the three-model sweep. Worth naming plainly: it is the item most likely to miss August 19. ## Member-data boundary Unchanged and still correct. The demo runs on Abhay's small purpose-made Discord, not the Sirens community server.
coilyco-ops commented 2026-08-12 12:42:09 +00:00
Author
Member
Copy link

Status refresh against main at 06a86a0

This issue's inventory has moved a lot, so here it is re-measured rather than remembered. Two of its statements are now stale in the useful direction, and one was fixed by someone else already.

Already there, updated

The original list still holds, and gains:

  • A composed identity. #98 is closed. Deep composes a real Agent Compose role bundle with the personality meld, ValidateSystemPrompt inverts per profile so Echo still carries none of it, and all eight roster roles bake so SIRENS_DEEP_ROLE selects one with no rebuild.
  • Knowledge of its own authority. #122 is closed. A skill generated from the deployed guardfile, stating deny-by-absence, inside Deep's local skill roots.
  • It cannot claim to be a person. #148 is closed. A shared prompt rule plus a validator that binds every response style, since the social profile previously had no deterministic reply check at all.
  • Durable work. #143 through #147 are closed: a job record with a state machine, async submit and poll and cancel, job-scoped telemetry, structured commands with a schema treated as an authority boundary, and thread-to-job binding.

Two entries in "Not there" are now inaccurate

MCP roster. mcp_servers: [].

The field no longer exists. e90e34b moved the roster to a deployment-owned YAML file named by SIRENS_ECHO_MCP_ROSTER, so a definition cannot carry one. Whether Deep has tools is a deploy fact, and per the roster comments quoted in #137 it does have the Forgejo MCP.

Discord binding. The profile is HTTP-only with channel: "".

channel: "" is still true and no longer means HTTP-only. It is the prompt's boundary label, not the routing key: admissionPolicy renders no channel sentence when it is empty, and routing comes from the access policy. Deep is on Discord today through the DM lane, and per my comment on #135 the guild path needs no code either.

The stale repository description is fixed

The Forgejo description still reads: Sirens Echo Community harness for the Sirens Discord.

It now reads "A discord community agent harness - home of sirens echo and sirens deep". Whoever changed it, that bullet is done.

What is genuinely still not there

Exactly one item from the original list survives re-measurement:

  • Agent-to-agent recognition. Nothing in the tree recognizes a counterpart as an agent rather than a person. #81 records it as the axis most worth a three-model sweep and the one most likely to break under a weaker model.

The identity eval is partially built: agent/board-deep.yaml is a human-graded board that emits a dataset and reports no verdict, and evaluation-deep.yaml is the deterministic gate. Neither covers the three recognition axes yet, which is #81's scope.

Suggested disposition

This issue did its job as the durable record of the gap. Everything in it is now either closed, reassigned to a live issue, or fixed. I would close it and let #81 carry the remaining recognition work, but it is labelled consult and the call is yours.

The member-data boundary at the end is unchanged and still correct.

## Status refresh against `main` at `06a86a0` This issue's inventory has moved a lot, so here it is re-measured rather than remembered. Two of its statements are now stale in the useful direction, and one was fixed by someone else already. ### Already there, updated The original list still holds, and gains: * **A composed identity.** #98 is closed. Deep composes a real Agent Compose role bundle with the personality meld, `ValidateSystemPrompt` inverts per profile so Echo still carries none of it, and all eight roster roles bake so `SIRENS_DEEP_ROLE` selects one with no rebuild. * **Knowledge of its own authority.** #122 is closed. A skill generated from the deployed guardfile, stating deny-by-absence, inside Deep's local skill roots. * **It cannot claim to be a person.** #148 is closed. A shared prompt rule plus a validator that binds every response style, since the social profile previously had no deterministic reply check at all. * **Durable work.** #143 through #147 are closed: a job record with a state machine, async submit and poll and cancel, job-scoped telemetry, structured commands with a schema treated as an authority boundary, and thread-to-job binding. ### Two entries in "Not there" are now inaccurate > **MCP roster.** `mcp_servers: []`. The field no longer exists. `e90e34b` moved the roster to a deployment-owned YAML file named by `SIRENS_ECHO_MCP_ROSTER`, so a definition cannot carry one. Whether Deep has tools is a deploy fact, and per the roster comments quoted in #137 it does have the Forgejo MCP. > **Discord binding.** The profile is HTTP-only with `channel: ""`. `channel: ""` is still true and no longer means HTTP-only. It is the prompt's boundary *label*, not the routing key: `admissionPolicy` renders no channel sentence when it is empty, and routing comes from the access policy. Deep is on Discord today through the DM lane, and per my comment on #135 the guild path needs no code either. ### The stale repository description is fixed > The Forgejo description still reads: Sirens Echo Community harness for the Sirens Discord. It now reads "A discord community agent harness - home of sirens echo and sirens deep". Whoever changed it, that bullet is done. ### What is genuinely still not there Exactly one item from the original list survives re-measurement: * **Agent-to-agent recognition.** Nothing in the tree recognizes a counterpart as an agent rather than a person. #81 records it as the axis most worth a three-model sweep and the one most likely to break under a weaker model. The identity eval is partially built: `agent/board-deep.yaml` is a human-graded board that emits a dataset and reports no verdict, and `evaluation-deep.yaml` is the deterministic gate. Neither covers the three recognition axes yet, which is #81's scope. ### Suggested disposition This issue did its job as the durable record of the gap. Everything in it is now either closed, reassigned to a live issue, or fixed. I would close it and let #81 carry the remaining recognition work, but it is labelled `consult` and the call is yours. The member-data boundary at the end is unchanged and still correct.
coilyco-ops commented 2026-08-12 17:13:17 +00:00
Author
Member
Copy link

Decision: close it

Direction from Kai, 2026-08-12 session. The consult label made this her call, and the recommendation in the status refresh is accepted.

This issue did its job. It was the durable record of the August 19 gap, it corrected two of its own claims along the way, and every line in it is now closed, reassigned to a live issue, or verified fixed.

Where the remaining work lives

Was in this issue Now
Discord binding #135 — deploy-gated, the last demo blocker
MCP roster Landed. Field no longer exists; roster is deployment-owned
Social media manager persona #98 — closed
Agent-to-agent recognition #153 — built as the "nothing at all" slice; Kai has since called for disclosure + register
The identity eval #81 — four axes, disclosure added
Stale repository description Fixed
README.md / docs/FEATURES.md check Carried to #81's preparation work rather than left here

On the re-measurement

Two corrections in the status refresh are worth keeping visible, because both were things this issue asserted and the tree disproved:

  • mcp_servers: [] — the field no longer exists at all. Whether Deep has tools is a deploy fact.
  • channel: "" — still true, and it does not mean HTTP-only. It is the prompt's boundary label, not a routing key.

That is the second time this issue has been corrected by reading the tree rather than the issue text, and it is the reason closing it is right: a stale inventory left open invites someone to read it as current.

Unchanged and still correct

The member-data boundary. The August 19 demo runs on Abhay's small purpose-made Discord, not the Sirens community server, so no real member data is in scope. That constraint outlives this issue — if a profile is ever pointed at the real community server on a hosted backend, retention, disclosure of which backend answers, and channel-class exclusions all become live questions. Worth re-filing standalone if that day comes.

## Decision: close it Direction from Kai, 2026-08-12 session. The `consult` label made this her call, and the recommendation in the status refresh is accepted. This issue did its job. It was the durable record of the August 19 gap, it corrected two of its own claims along the way, and every line in it is now closed, reassigned to a live issue, or verified fixed. ## Where the remaining work lives | Was in this issue | Now | | --- | --- | | Discord binding | #135 — deploy-gated, the last demo blocker | | MCP roster | Landed. Field no longer exists; roster is deployment-owned | | Social media manager persona | #98 — closed | | Agent-to-agent recognition | #153 — built as the "nothing at all" slice; Kai has since called for disclosure + register | | The identity eval | #81 — four axes, disclosure added | | Stale repository description | Fixed | | README.md / docs/FEATURES.md check | Carried to #81's preparation work rather than left here | ## On the re-measurement Two corrections in the status refresh are worth keeping visible, because both were things this issue asserted and the tree disproved: * `mcp_servers: []` — the field no longer exists at all. Whether Deep has tools is a deploy fact. * `channel: ""` — still true, and it does not mean HTTP-only. It is the prompt's boundary label, not a routing key. That is the second time this issue has been corrected by reading the tree rather than the issue text, and it is the reason closing it is right: a stale inventory left open invites someone to read it as current. ## Unchanged and still correct The member-data boundary. The August 19 demo runs on Abhay's small purpose-made Discord, not the Sirens community server, so no real member data is in scope. That constraint outlives this issue — if a profile is ever pointed at the real community server on a hosted backend, retention, disclosure of which backend answers, and channel-class exclusions all become live questions. Worth re-filing standalone if that day comes.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
aos/claude/sj87-entity-attribute
aos/claude/sj87-challenge
aos/claude/turn-duration-buckets
aos/claude/turn-stages-over-cap
aos/claude/turn-stages-hold-doc
aos/claude/turn-iteration-cap
book-leads-the-glyphs
science-and-web-culture-packs
record-lane-role-voice-pairings
catalogue-stage-phrase
progress-rows-one-knob
skill-read-worklog-detail
librarian-lookup-first
librarian-person-package
feat/dowel-no-boundaries
aos/claude/gh1035-no-blank-posts
aos/claude/gh1036-harness-thread-name
fix/thread-names
feat/trajectory-completes
fix/prompt-budgets
aos/claude/docs-cut-2
aos/claude/ka54-thread-ownership
aos/claude/admission-bound
aos/claude/gh1025-roster-reexport
aos/claude/docs-strip-archaeology
feat/temporal-mcp
aos/claude/dowel-board-moxn-write-boundaries
aos/claude/ue65-moxn-write-framing
aos/claude/progress-backoff
aos/claude/bound-scratch-search-2
aos/claude/unblock-main
aos/claude/tool-breaker
fix/roster-core-eager
aos/claude/finish-dowel-rename
fix/971-skill-contract
aos/claude/model-answered-not-unavailable
aos/claude/mcp-singular-command
task/moxn-and-temporal-skills
aos/claude/ue65-temporal-brand
task/dowel-site-work-tier
aos/claude/ue65-roster-drift
fix/dropped-turn-always-speaks
aos/claude/folded-ask-coverage
aos/claude/dowel-board
aos/claude/dowel-pronouns
feat/trajectory-keyed-on-the-message
aos/claude/coalesce-discord-lane
task/derive-shipped-profiles
fix/ship-the-dowel-skill-root
aos/claude/eval-context
fix/bundle-references-reachable
aos/claude/eval-docs-one-page
aos/claude/dowel-engineer-suite
fix/catalogue-clone-cache
feat/engineer-role-graph
task/free-the-config-numbers
aos/claude/dowel-site-work
aos/claude/dowel-prose
aos/claude/mx76-derive-knobs
issue-859-on-demand-skill-reads
issue-651-ship-well-formed-replies
issue-852-filing-validity
issue-916-calculator-tool
issue-854-feature-flag-table
issue-866-role-mention-summons
issue-858-grounding-bound-per-server
issue-899-progress-keeps-updating
issue-900-rollup-mirrors-worklog
issue-901-raise-progress-cadence
issue-904-thread-title-length
issue-905-http-reachability
issue-855-turn-clock
issue-895-silent-turn
issue-873-mcp-tool-span-error
issue-878-settle-dropped-jobs
aos/claude/aw85-se-bands
aos/claude/hs68-model-rejected
aos/claude/hs68-effect-telemetry
aos/claude/hs68-temporal-mirror
aos/claude/hs68-prompt-commands
aos/claude/hs68-model-idle-timeout
aos/claude/hs68-prompt-command-intent
aos/claude/hs68-consult-label-name
aos/claude/hs68-grant-denial-403
aos/claude/hs68-queued-jobs-dropped
aos/claude/hs68-knob-guard
aos/claude/bk79-agent-folders
aos/claude/bk79-own-instructions
aos/claude/ym96-docs-band
aos/claude/bk79-server-instructions
aos/claude/aw85-mcp-beaver-doc
aos/claude/bk79-session-workspace
aos/claude/yt58-org-relationship
aos/claude/bk79-numeric-config
aos/claude/xu59-just-boundaries
aos/claude/xu59-eval-board
aos/claude/bk79-phrase-telemetry
aos/claude/bk79-object-emoji
aos/claude/xh55-otlp-logs
aos/claude/aw85-thread-prefill
aos/claude/wy58-thread-prefill-always
aos/claude/wy58-thread-prefill
aos/claude/xh55-move-to-repo
aos/claude/wy58-thread-title-length
aos/claude/xh55-filing-trigger
aos/claude/yt58-worklog-embed
aos/claude/aw85-relative-brevity
aos/claude/xh55-reasoning-roundtrip
aos/claude/yt58-clock-rotation
aos/claude/yt58-unbreak-main
aos/claude/bk79-test-build-break
aos/claude/yt58-partial-refusal
aos/claude/aw85-turn-failure-classify
aos/claude/aw85-outbound-spill
aos/claude/xh55-budget-spent-cause
aos/claude/wy58-bundles-not-content
aos/claude/wy58-refusal-reason
aos/claude/yt58-role-snapshot-gate
aos/claude/xh55-docker-probe
aos/claude/bk79-grounding-tools
aos/claude/az59-gate-span
aos/claude/az59-pg-jobstore
eng/roster-request-headers
eng/roster-headers
eng/list-the-mcps
aos/claude/mg96-fm
eng/name-echos-seat
eng/unpin-the-card-wording
olaf/remove-irl-physical
aos/claude/mg96
eng/echo-composes-ops
quail/two-rows-not-four
fix/two-failures-two-verdicts
feat/an-emitted-message-is-not-emitted-twice
quail/partial-coverage-outcome
feat/ten-minutes-or-ten-messages
feat/a-waiting-turn-says-how-long
feat/a-job-may-emit-content
quail/round-fanout-unbounded
quail/adversarial-reply-ceiling
docs/list-the-open-pull-requests
quail/principal-id-stays-out-of-the-prompt
fix/every-label-in-a-wildcard-prefix-is-a-label
docs/the-battery-assumes-two-checks-it-does-not-run
fix/a-rest-failure-keeps-its-status
quail/retag-label-rows
quail/adjacency-guard-row
test/pin-names-the-issue-that-owns-it
test/pin-points-at-a-live-issue
quail/job-outcome-discarded
fix/repair-exhaustion-is-not-an-outage
quail/reasoning-omitempty-pin
docs/label-id-silently-drops
quail/gating-pack-markup-gap
fix/instance-name-reads-identity
docs/indistinguishable-542-resolution
fix/instance-name-not-a-live-service
quail/unwired-capability-guard
fix/repair-path-reasoning-content
quail/indistinguishable-values-recurrence
quail/identity-short-form-rows
quail/repair-path-reasoning-content
docs/verify-a-write-landed-claude
quail/host-label-shape-corpus
docs/a-deploy-owned-file-has-two-shapes-claude
fix/a-roster-path-must-name-servers-claude
fix/every-label-before-the-suffix-claude
fix/a-first-label-must-exist-claude
feat/tune-the-timeouts-from-deployment-claude
qa/protocol-limits-are-not-dials
feat/a-wildcard-is-not-a-suffix-claude
feat/retry-what-fails-fast-claude
fix/name-the-deliberate-hold-claude
test/the-access-check-exit-codes-claude
build/ship-the-access-check-claude
qa/callers-not-reachability
qa/pin-the-unwired-thread-binding
feat/an-offline-access-policy-gate-claude
test/the-notice-detaches-twice-claude
docs/say-what-the-job-thread-does-claude
fix/a-notice-does-not-thread-claude
fix/one-invocation-is-a-phrase-claude
fix/a-moment-ago-is-this-turn
fix/main-is-red-on-the-adverb-row
fix/an-adverb-does-not-break-the-auxiliary
qa/score-the-575-fix
feat/a-reply-names-its-subject
eng/a-turn-is-not-the-past
fix/since-you-asked-is-this-turn
docs/a-default-that-reads-as-an-answer
fix/a-nameless-tool-is-not-the-server
qa/pin-the-outage-state
fix/a-session-lifetime-is-not-a-latency
fix/an-undated-passive-is-still-a-claim
fix/main-is-red-on-the-corpus
fix/an-undated-passive-is-a-claim
eng/a-session-is-not-a-request
fix/a-self-claim-in-the-simple-past
qa/extend-grounding-corpus
fix/a-tool-never-offered-is-not-a-tool-declined
eng/one-doc-for-the-tracker-surface
eng/say-what-is-switched-on
fix/evaluation-is-not-the-production-service
qa/pin-the-listing-attribute
eng/split-five-docs-off-the-cap
eng/concurrent-means-goroutines
eng/split-the-tracker-surface
test/the-first-label-of-a-hostname
fix/a-cache-hit-is-not-a-round-trip
qa/pin-the-budget-ladder
fix/the-first-label-of-a-hostname
eng/the-scratchpad-assumes-one-replica
fix/a-person-is-named-in-prose
docs/jobs-are-single-process
qa/enumerate-the-mention-positions
eng/split-the-response-inventory
fix/green-main-doc-cap-and-stale-characterizations
eng/main-is-green-again
eng/split-the-mention-scope
fix/mentions-doc-over-cap
qa/unredden-the-code-span-pin
qa/pin-the-code-span-collision
eng/code-spans-are-not-prose
feat/a-thread-title-says-what-it-is-for
fix/discord-markup-is-not-prose-either
eng/mark-the-turn-once
fix/a-name-in-a-url-is-not-a-person
qa/pin-every-reaction-is-emitted
eng/mentions-skip-link-spans
fix/one-step-owns-every-service-suffix
qa/pin-the-mention-url-collision
docs/the-roster-is-member-influenced
docs/what-a-mention-can-reach
qa/pin-the-documented-glyphs
feat/naming-someone-reaches-them
qa/pin-the-sandbox-label-wiring
qa/pin-the-truncated-receipt
feat/the-harness-labels-what-it-files
qa/compare-a-case-by-marshalling
fix/one-spelling-for-the-status-vocabulary
qa/declare-pack-divergence
fix/the-reactions-match-the-approved-vocabulary
fix/a-file-path-is-just-a-file-path
qa/pin-the-mapped-tailnet-form
fix/a-truncated-page-says-so
fix/the-extraction-case-detects-a-dump
docs/the-consult-label-tracks-the-thread
feat/the-eval-can-forge-a-turn
fix/refuse-the-tailnet-range
qa/pin-the-fail-heading-count
feat/a-bounded-fetch-tool
fix/preserve-the-longform-probe-pack
qa/pin-the-lane-gate
qa/preserve-the-longform-pack
fix/the-prompt-is-not-a-secret
fix/a-reference-never-loses-to-the-footer
qa/preserve-the-probe-packs
feat/a-trusted-caller-on-the-tailnet
fix/capability-tells-the-truth-about-the-scratchpad
qa/echo-battery-negative-control
fix/one-fail-block-not-two
feat/tool-call-footer
fix/guard-the-extraction-case
feat/canonical-phrases-by-key
fix/the-progress-line-is-a-reply-too
qa/pin-the-agent-recognition-case
qa/pin-the-tool-name-markup-guards
feat/five-second-buffer
fix/a-failing-case-shows-the-reply
fix/extraction-case-stops-penalising-compliance
fix/a-security-case-that-penalises-compliance
feat/deny-actually-denies
feat/job-refusals-reach-telemetry
fix/land-the-harness-refresh-on-main
feat/a-long-reply-gets-a-thread
feat/the-thinking-line-shows-it-is-working
feat/roster-hour-ttl-and-refresh
refactor/every-number-in-one-file
feat/agent-can-refresh-its-roster
fix/size-refusal-is-not-a-parse-error
fix/budget-base-above-the-reasoning-floor
fix/one-number-for-the-progress-cadence
fix/gate-sees-a-new-file
fix/one-meaning-for-channel-id
fix/look-up-verbs-cannot-match
feat/recognise-a-trace-lookup-request
feat/discord-identifiers-on-the-turn-span
fix/budget-failure-names-the-reasoning-spend
feat/notice-carries-the-trace-id
qa/cut-run-stops-calling
docs/merge-lane-closing-reference
eng/gate-knows-the-lane
eng/feature-inventory-catchup
fix/rate-dataset-survives-a-cut-run
test/consolidate-pack-coverage
pr-lane-318
fix/flip-unknown-field-rows
test/turn-unknown-fields
fix/rate-doc-over-cap
test/language-scope-characterization
fix/pronoun-case-cannot-fire
fix/main-red-again
fix/main-is-red-doc-cap
fix/gate-negated-accuracy-claim
fix/stale-skip-allowlist-note
test/definition-must-reject
test/gate-covers-every-pack
test/bucket-table-bound
test/compose-deny-offline
fix/symlink-test-skips-itself
test/build-revision
fix/eviction-corpus-green
test/eviction-corpus
test/duration-config
test/rune-boundary
test/send-bounds
test/reserved-path-spellings
test/data-borne-injection
test/scratch-partition-collision
test/capability-docs-all
test/injection-cases
docs/http-contract-retry-after
test/capability-reach
test/rate-cases-from-192
test/score-order
test/capability-doc-matches-code
test/grounding-action-claim-corpus
test/http-turn-contract
feat/require-rate-limit-on-open-guilds
fix/pr-image-build
fix/compose-stage-inputs
feat/sirens-deep-compose-wiring
fix/deep-forgejo-mcp
refactor/evaluation-pack-yaml
coilysiren-patch-1
feat/deep-steam-mcp
feat/drop-issue-envelope
fix/dm-needs-no-mention
fix/pronoun-defaults
chore/aos-precommit-v0.18-lint-backlog
fix/harness-attribution-and-forgejo-detail
fix/tool-inflated-completion-budget
feat/sirens-deep-compose
feat/banner-hires
feat/banner
feat/sirens-deep-mark
feat/sirens-deep-transparent
feat/prompt-snapshots
fix/policy-check-image-context
sirens-deep-admission-hardening
docs/drop-private-image-claim
feat/thread-scoped-replies
issue-67
feat/sirens-community-harness
No results found.
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#76
No description provided.