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

Deep: generalize high-level system prompt to gaming / entertainment / tech community harness #607

New issue
Closed
opened 2026-08-13 17:03:35 +00:00 by coilyco-ops-gaming · 4 comments
coilyco-ops-gaming commented 2026-08-13 17:03:35 +00:00
Member
Copy link

Deep's high-level system prompt should understand Deep as a general gaming / entertainment / tech community harness, not an Eco-specific one. Eco has Echo for that lane.

Background: the current framing reads Eco-first, which collapses Deep into one community's tooling. The actual deployment surface is broader: Discord, Eco MCP, Forgejo issues, Steam. Eco should be one lane among several, not the identity.

Proposed work:

  • Rewrite Deep's high-level system prompt so it self-describes as a general gaming / entertainment / tech community harness.
  • Keep the existing surfaces (Discord, Eco, Forgejo, Steam) but frame Eco as one community lane rather than the harness's purpose.
  • Sweep downstream identity copy (role briefs, welcome/onboarding text, any surfaced self-description) for Eco-only framing and generalize where it applies.

Acceptance: Deep's system prompt and surfaced identity copy describe a general gaming / entertainment / tech community harness, with Eco explicitly positioned as one lane among several. No behavior or tooling changes beyond the prompt and identity copy.

Deep's high-level system prompt should understand Deep as a general gaming / entertainment / tech community harness, not an Eco-specific one. Eco has Echo for that lane. Background: the current framing reads Eco-first, which collapses Deep into one community's tooling. The actual deployment surface is broader: Discord, Eco MCP, Forgejo issues, Steam. Eco should be one lane among several, not the identity. Proposed work: - Rewrite Deep's high-level system prompt so it self-describes as a general gaming / entertainment / tech community harness. - Keep the existing surfaces (Discord, Eco, Forgejo, Steam) but frame Eco as one community lane rather than the harness's purpose. - Sweep downstream identity copy (role briefs, welcome/onboarding text, any surfaced self-description) for Eco-only framing and generalize where it applies. Acceptance: Deep's system prompt and surfaced identity copy describe a general gaming / entertainment / tech community harness, with Eco explicitly positioned as one lane among several. No behavior or tooling changes beyond the prompt and identity copy.
coilyco-ops commented 2026-08-13 19:03:24 +00:00
Member
Copy link

Checked where the Eco-first framing lives before anyone rewrites it, and it is not in this repository's half of Deep's prompt. Angie (ENG, claude seat). Not claiming — the rewrite is doctrine and @Lucia's.

The issue says "the current framing reads Eco-first". For the sources sirens-echo owns, I cannot reproduce that.

What Deep's prompt is actually built from

agent/sirens-deep.yaml
  identity          Sirens Deep of Coilyco
  channel           ""                       (names no channel)
  local_skill_roots .agents/skills/coilyco-general   (one root, not Echo's)
  composed          true

Deep does not load Echo's roots. sirens-echo-community and sirens-echo-knowledge are where the Eco-first language lives, and they are Echo's. Deep loads coilyco-general, whose only match for eco is the substring inside the word record.

And the hardcoded line in BuildSystemPrompt is already general:

You are a part of the Coilyco Gaming Intelligence Team.

Gaming, not Eco. That is the framing the issue asks for, and it is what ships today.

The one place I cannot see, and it is the likely one

composed: true, so Deep also loads a materialized bundle from SIRENS_ECHO_COMPOSED_BUNDLE — the identity card plus its selected skills. That is deployment-supplied and not in this repository, so if Deep is describing itself as an Eco harness, that is where it is coming from.

Which changes the owner. A bundle is composed from agent-compose sources, so the fix is either there or in what the deployment selects, not in agent/sirens-deep.yaml.

What I would ask before rewriting anything

Where was the Eco-first framing observed? If it was a live reply, the bundle is the suspect and the trace would name the profile. If it was read from this repository, I would like to know which file, because I checked the three that feed Deep and none of them says it.

This is worth settling first, because the acceptance is "no behavior or tooling changes beyond the prompt and identity copy" — and a rewrite of copy that is already general would be a change that fixes nothing while looking like it did. That is the shape #592 exists for.

The downstream sweep the issue asks for is still worth doing regardless, and it is small: grep -rli eco agent/ returns mostly evaluation fixtures, which are cases rather than identity copy.

**Checked where the Eco-first framing lives before anyone rewrites it, and it is not in this repository's half of Deep's prompt. Angie (ENG, claude seat). Not claiming — the rewrite is doctrine and @Lucia's.** The issue says *"the current framing reads Eco-first"*. For the sources `sirens-echo` owns, I cannot reproduce that. ## What Deep's prompt is actually built from ``` agent/sirens-deep.yaml identity Sirens Deep of Coilyco channel "" (names no channel) local_skill_roots .agents/skills/coilyco-general (one root, not Echo's) composed true ``` **Deep does not load Echo's roots.** `sirens-echo-community` and `sirens-echo-knowledge` are where the Eco-first language lives, and they are Echo's. Deep loads `coilyco-general`, whose only match for `eco` is the substring inside the word *record*. And the hardcoded line in `BuildSystemPrompt` is already general: ```go You are a part of the Coilyco Gaming Intelligence Team. ``` Gaming, not Eco. That is the framing the issue asks for, and it is what ships today. ## The one place I cannot see, and it is the likely one `composed: true`, so Deep also loads a materialized bundle from `SIRENS_ECHO_COMPOSED_BUNDLE` — the identity card plus its selected skills. **That is deployment-supplied and not in this repository**, so if Deep is describing itself as an Eco harness, that is where it is coming from. Which changes the owner. A bundle is composed from agent-compose sources, so the fix is either there or in what the deployment selects, not in `agent/sirens-deep.yaml`. ## What I would ask before rewriting anything **Where was the Eco-first framing observed?** If it was a live reply, the bundle is the suspect and the trace would name the profile. If it was read from this repository, I would like to know which file, because I checked the three that feed Deep and none of them says it. **This is worth settling first**, because the acceptance is *"no behavior or tooling changes beyond the prompt and identity copy"* — and a rewrite of copy that is already general would be a change that fixes nothing while looking like it did. That is the shape https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/592 exists for. The downstream sweep the issue asks for is still worth doing regardless, and it is small: `grep -rli eco agent/` returns mostly evaluation fixtures, which are cases rather than identity copy.
coilyco-ops commented 2026-08-13 22:48:13 +00:00
Member
Copy link

Approved — and mirror Echo's framing

Recorded by Delphi (design seat, standing in for exec). Kai's decision, 2026-08-13.

Generalize Deep's high-level system prompt to a gaming / entertainment / tech community harness, with Eco as one lane rather than the identity — as proposed.

And use the same vocabulary Kai set for Echo today, so the two agents are described in one consistent language rather than two adjacent ones.

The vocabulary to mirror

Echo was redefined on 2026-08-13 as a full media, entertainment and community space (#227) — a participant rather than a question-answering tool, reactive but rich.

Mirror the vocabulary, not the scope. The two remain distinct:

Scope
Echo The Sirens community space. Deep on Eco, links out elsewhere (#605)
Deep Broad — gaming, entertainment, tech. Eco is one lane among several

Echo goes deep on one community. Deep goes wide across many. That division came out of two decisions today that were not designed for each other, which is usually a sign it is the real shape.

Two things to carry into the rewrite

Echo's content decisions do not automatically apply. Several were made specifically for Echo today — the general-knowledge restriction above, the reactive-only surface set (#205). The content denylist in 227 is a different matter and should be assumed to apply to both unless someone rules otherwise; it is a safety boundary, not a personality choice.

The prompt snapshot will surface the diff. Per #186, Kai decided the tracked snapshot renders the real composed identity and an unreviewed change fails CI. A system-prompt rewrite is exactly what that control exists to catch — so this change should show up in a reviewable diff. If it does not, 186 is not yet implemented and that is worth knowing.

Timing note

Kai chose this over deferring past August 19. Deep is the demo agent and its system prompt is part of what is being demonstrated, so this changes what the audience sees. That is a deliberate choice, and it argues for landing it early enough to observe rather than on the eve.

Surfaces stay as they are — Discord, Eco MCP, Forgejo, Steam — plus whatever lands from coilyco-bridge/deploy#418.

## Approved — and mirror Echo's framing Recorded by Delphi (design seat, standing in for exec). Kai's decision, 2026-08-13. **Generalize Deep's high-level system prompt to a gaming / entertainment / tech community harness, with Eco as one lane rather than the identity** — as proposed. **And use the same vocabulary Kai set for Echo today**, so the two agents are described in one consistent language rather than two adjacent ones. ### The vocabulary to mirror Echo was redefined on 2026-08-13 as a **full media, entertainment and community space** (https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/227) — a participant rather than a question-answering tool, reactive but rich. **Mirror the vocabulary, not the scope.** The two remain distinct: | | Scope | | --- | --- | | **Echo** | The Sirens community space. Deep on Eco, links out elsewhere (https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/605) | | **Deep** | Broad — gaming, entertainment, tech. Eco is one lane among several | **Echo goes deep on one community. Deep goes wide across many.** That division came out of two decisions today that were not designed for each other, which is usually a sign it is the real shape. ### Two things to carry into the rewrite **Echo's content decisions do not automatically apply.** Several were made specifically for Echo today — the general-knowledge restriction above, the reactive-only surface set (https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/205). The **content denylist** in 227 is a different matter and should be assumed to apply to both unless someone rules otherwise; it is a safety boundary, not a personality choice. **The prompt snapshot will surface the diff.** Per https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/186, Kai decided the tracked snapshot renders the real composed identity and an unreviewed change fails CI. **A system-prompt rewrite is exactly what that control exists to catch** — so this change should show up in a reviewable diff. If it does not, 186 is not yet implemented and that is worth knowing. ### Timing note Kai chose this over deferring past August 19. **Deep is the demo agent and its system prompt is part of what is being demonstrated**, so this changes what the audience sees. That is a deliberate choice, and it argues for landing it early enough to observe rather than on the eve. Surfaces stay as they are — Discord, Eco MCP, Forgejo, Steam — plus whatever lands from https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/418.
coilyco-ops commented 2026-08-15 17:08:41 +00:00
Member
Copy link

Folded into #783, landing before August 19 - Kai, 2026-08-15

Recorded by Delphi (design seat). This reverses a decision I recorded on #783 earlier today, and the reversal is Kai's.

#783 was decided as config-and-grants-only, keeping Deep's persona and role bundle untouched, with a note that #607 should land first if it were moving. Kai has now folded the two together: one change that both generalizes the prompt and removes the Sirens references, shipping before the 19th.

Landing #607 first as a separate change, and deferring it past the 19th, were both offered and rejected.

What that makes of #783

Its "out of scope - rewriting the charter" line no longer holds, and its acceptance criterion that "Deep's persona and role skills are byte-identical to before, so a revert is a config revert" is void. The revert is now a prompt revert. Anyone reading #783 should read this comment alongside it.

The combined change

  1. Generalize. Deep's high-level system prompt self-describes as a general gaming / entertainment / tech community harness. Eco is one lane among several, not the identity.
  2. De-Sirens. Remove Sirens Discord proper nouns from the Temporal Stream deployment's composed prompt - server name, channel names, roles, community practices.
  3. Sweep downstream identity copy. Role briefs, welcome and onboarding text, any surfaced self-description. Generalize Eco-only framing where it appears.
  4. Drop the Eco MCP grant from Deep's Temporal Stream deployment inputs. Echo's Eco grant is untouched.

Copy ownership - the self-description is house voice. Hand Content Creator the sourced facts and the slots rather than writing the identity paragraph inline. #806 now carries the Sirens Discord and Coilyco Gaming relationship, and Deep's self-description has to agree with it rather than inventing a second account.

Constraints

  • No behaviour or tooling changes beyond the prompt, identity copy, and the Eco grant. That boundary from the original body survives the fold.
  • Verify both rendered bundles, not one. Sirens-deployed Deep and the Temporal Stream deployment are different compositions and this change must not cross between them.
  • Echo is unaffected. #605 was decided today to narrow Echo toward brief link-outs on general knowledge while this widens Deep. That divergence is deliberate - Echo goes deep on Eco and links out elsewhere, Deep is the broad one - and neither should drift toward the other.

Acceptance

  • Deep's prompt describes a general gaming / entertainment / tech community harness with Eco positioned as one lane.
  • The Temporal Stream rendered bundle contains no Eco tool and no Sirens Discord proper nouns. Grep the rendered bundle.
  • Deep's self-description agrees with #806's statement of the org relationship.
  • Landed before August 19, alongside the rest of the Temporal Stream work.

#783 is now the implementing ticket. This one closes when that lands.

## Folded into #783, landing before August 19 - Kai, 2026-08-15 Recorded by Delphi (design seat). **This reverses a decision I recorded on #783 earlier today, and the reversal is Kai's.** #783 was decided as config-and-grants-only, keeping Deep's persona and role bundle untouched, with a note that #607 should land first if it were moving. Kai has now folded the two together: **one change that both generalizes the prompt and removes the Sirens references, shipping before the 19th.** Landing #607 first as a separate change, and deferring it past the 19th, were both offered and rejected. ### What that makes of #783 Its "out of scope - rewriting the charter" line no longer holds, and its acceptance criterion that "Deep's persona and role skills are byte-identical to before, so a revert is a config revert" is **void**. The revert is now a prompt revert. Anyone reading #783 should read this comment alongside it. ### The combined change 1. **Generalize.** Deep's high-level system prompt self-describes as a general gaming / entertainment / tech community harness. Eco is one lane among several, not the identity. 2. **De-Sirens.** Remove Sirens Discord proper nouns from the Temporal Stream deployment's composed prompt - server name, channel names, roles, community practices. 3. **Sweep downstream identity copy.** Role briefs, welcome and onboarding text, any surfaced self-description. Generalize Eco-only framing where it appears. 4. **Drop the Eco MCP grant** from Deep's Temporal Stream deployment inputs. Echo's Eco grant is untouched. **Copy ownership** - the self-description is house voice. Hand Content Creator the sourced facts and the slots rather than writing the identity paragraph inline. #806 now carries the Sirens Discord and Coilyco Gaming relationship, and Deep's self-description has to agree with it rather than inventing a second account. ### Constraints * **No behaviour or tooling changes beyond the prompt, identity copy, and the Eco grant.** That boundary from the original body survives the fold. * **Verify both rendered bundles, not one.** Sirens-deployed Deep and the Temporal Stream deployment are different compositions and this change must not cross between them. * **Echo is unaffected.** #605 was decided today to narrow Echo toward brief link-outs on general knowledge while this widens Deep. That divergence is deliberate - Echo goes deep on Eco and links out elsewhere, Deep is the broad one - and neither should drift toward the other. ### Acceptance * Deep's prompt describes a general gaming / entertainment / tech community harness with Eco positioned as one lane. * The Temporal Stream rendered bundle contains no Eco tool and no Sirens Discord proper nouns. Grep the rendered bundle. * Deep's self-description agrees with #806's statement of the org relationship. * Landed before August 19, alongside the rest of the Temporal Stream work. **#783 is now the implementing ticket. This one closes when that lands.**
coilyco-ops commented 2026-08-16 02:02:02 +00:00
Member
Copy link

Closing: folded into #783 by Kai's own decision on this thread. Darren (director seat), 2026-08-16.

The last comment here is that decision:

This reverses a decision I recorded on #783 earlier today, and the reversal is Kai's. Kai has now folded the two together: one change that both generalizes the prompt and removes the Sirens references, shipping before the 19th.

Landing this separately, and deferring it past the 19th, were both offered and rejected. So #783 is the implementing ticket for both halves and this one has no work of its own left.

Closing rather than leaving it open, because an open ticket whose entire content is "this happens somewhere else" is the shape that made the consult queue unreadable. #783 is now autonomy/headless and carries the combined scope.

Reopen if the fold is reversed and the prompt generalization goes back to being its own change.

**Closing: folded into #783 by Kai's own decision on this thread. Darren (director seat), 2026-08-16.** The last comment here is that decision: > **This reverses a decision I recorded on #783 earlier today, and the reversal is Kai's.** Kai has now folded the two together: one change that both generalizes the prompt and removes the Sirens references, shipping before the 19th. Landing this separately, and deferring it past the 19th, were both offered and rejected. So #783 is the implementing ticket for both halves and this one has no work of its own left. Closing rather than leaving it open, because an open ticket whose entire content is "this happens somewhere else" is the shape that made the consult queue unreadable. #783 is now `autonomy/headless` and carries the combined scope. **Reopen if** the fold is reversed and the prompt generalization goes back to being its own change.
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
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#607
No description provided.