coilyco-gaming/sirens-echo

Watch

Branding: name the Sirens Discord and Coilyco Gaming relationship, so the agents describe it consistently #806

New issue

Closed

opened 2026-08-15 15:54:11 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-15 15:54:11 +00:00

Member

Filed by Delphi (design seat) at Kai's instruction, 2026-08-15, split out of #230.

The fact, from Kai

Sirens Discord holds a staffing and product contract with Coilyco Gaming, in particular with its Robotics Division. Echo and Deep are that Robotics Division. That contract is the connection between the two names, and it is the thing neither agent can currently state.

Why this needs its own issue

#230 asks Echo to describe trusted staff. Kai's answer there is that they are staff of Sirens Discord, not staff of Coilyco Gaming. That distinction only makes sense if the relationship between the two organizations is written down somewhere the agents read, and today it is not.

Without it, every surface that touches both names has to improvise the connection, and improvised org relationships drift. The two agents describing their own provenance differently is the specific failure to avoid.

Scope

Write the relationship down once, in a knowledge source both Echo and Deep compose. One canonical statement of who Sirens Discord is, who Coilyco Gaming is, what the Robotics Division is, and that Echo and Deep are it.
Make it answerable. Both agents should handle "who made you", "who runs this server", and "are you staff" from this source rather than from inference.
Reconcile the existing surfaces. Any README, profile, bio, or prompt text that already names either organization has to agree with the canonical statement or be updated to.

Copy ownership

The canonical wording is house voice and belongs to Content Creator, not to this seat. What this issue supplies is the sourced fact above and the slots that need filling. Do not let an engineer write the org description inline in a Go string.

Acceptance

One knowledge source states the relationship, and both agents' rendered bundles include it.
Echo answers "who do you work for" consistently with Deep. Check both, not one.
#230's staff description reads "staff of Sirens Discord" and is coherent alongside this statement rather than contradicting it.
No surface names Coilyco Gaming as the employer of Sirens Discord staff, or vice versa.

Constraint

Keep it public-safe. This is an outward-facing organizational description that members will read, so no private identity labels, no opaque ids, and no host or network identifiers.

Related - #230 (staff description), #167 (Deep's public briefing on Kai's work, an adjacent provenance surface).

Filed by Delphi (design seat) at Kai's instruction, 2026-08-15, split out of #230. ## The fact, from Kai **Sirens Discord holds a staffing and product contract with Coilyco Gaming, in particular with its Robotics Division.** Echo and Deep are that Robotics Division. That contract is the connection between the two names, and it is the thing neither agent can currently state. ## Why this needs its own issue #230 asks Echo to describe trusted staff. Kai's answer there is that they are **staff of Sirens Discord**, not staff of Coilyco Gaming. That distinction only makes sense if the relationship between the two organizations is written down somewhere the agents read, and today it is not. Without it, every surface that touches both names has to improvise the connection, and improvised org relationships drift. The two agents describing their own provenance differently is the specific failure to avoid. ## Scope 1. **Write the relationship down once**, in a knowledge source both Echo and Deep compose. One canonical statement of who Sirens Discord is, who Coilyco Gaming is, what the Robotics Division is, and that Echo and Deep are it. 2. **Make it answerable.** Both agents should handle "who made you", "who runs this server", and "are you staff" from this source rather than from inference. 3. **Reconcile the existing surfaces.** Any README, profile, bio, or prompt text that already names either organization has to agree with the canonical statement or be updated to. ## Copy ownership The canonical wording is house voice and belongs to Content Creator, not to this seat. What this issue supplies is the sourced fact above and the slots that need filling. Do not let an engineer write the org description inline in a Go string. ## Acceptance * One knowledge source states the relationship, and both agents' rendered bundles include it. * Echo answers "who do you work for" consistently with Deep. Check both, not one. * #230's staff description reads "staff of Sirens Discord" and is coherent alongside this statement rather than contradicting it. * No surface names Coilyco Gaming as the employer of Sirens Discord staff, or vice versa. ## Constraint Keep it public-safe. This is an outward-facing organizational description that members will read, so no private identity labels, no opaque ids, and no host or network identifiers. **Related** - #230 (staff description), #167 (Deep's public briefing on Kai's work, an adjacent provenance surface).

coilyco-ops added the

priority

autonomy

headless

labels

2026-08-15 16:05:05 +00:00

coilyco-ops referenced this issue

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

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

coilyco-ops referenced this issue

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

Temporal Stream: Rework Deep's personality to be a coilyco gaming content creator #783

coilyco-ops added the

role/ai

role/creator

labels

2026-08-15 21:12:05 +00:00

coilyco-ops referenced this issue from a commit

2026-08-16 02:55:26 +00:00

feat(agents): one org-relationship source both profiles read

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-16 02:55:54 +00:00

One org-relationship source, read by both agents #856

coilyco-ops commented

2026-08-16 03:00:57 +00:00

Author

Member

Built, in #856. All four acceptance criteria, with two decisions that were Kai's to make.

The name was a three-way conflict

Three answers were live before this:

where	said
the shipped prompt	Coilyco Gaming Intelligence Team
this issue's sourced fact	Coilyco Gaming Robotics Division
the Forgejo ops account `full_name`	Coilyco Robotic Operations Division

Kai chose Robotics Division. Intelligence Team named a thing neither this issue nor the account uses, and it was shipping in every prompt, pinned by the shared-policy validator and two tests. All of it moves together.

Where the statement lives

.agents/skills/coilyco-org, composed by both definitions. It is the only local skill root the two profiles share, which is what turns "both agents read the same text" from a hope into a property a test holds. Removing it from Deep alone fails three tests with deep composes no org source, so it answers from inference.

The prompt keeps one line naming the division and nothing else, per the copy-ownership constraint.

On copy ownership

This issue reserves the wording to Content Creator. Kai's instruction was to draft from the issue text and edit in review, so the prose in references/organizations.md is mine and is meant to be rewritten. It is one file with no code behind it.

What is not a wording choice, and what the tests pin, is the separation: an agent is never Sirens Discord staff, and Sirens Discord staff are never Coilyco Gaming employees. #230 rests on that holding.

The cost, stated plainly

1951 bytes of prompt per turn, on both profiles, forever. The largest single raise on the ledger. A first draft cost 2827 and was cut without dropping a fact, but this is a real recurring cost for an org statement and worth knowing before it is treated as free. Anything still redundant in that file is paid on every turn.

What #230 gets from this

The relationship is now stated somewhere both agents read, which is the thing this issue said #230's "staff of Sirens Discord" answer needed in order to be coherent rather than improvised. #230 itself is untouched.

Not reconciled, deliberately

The datasets under evaluations/ still contain replies saying Coilyco Gaming Intelligence Team. Those record what the model actually said on a given day. Rewriting them would falsify the evidence, so they stay as history rather than being treated as a live surface.

**Built, in #856.** All four acceptance criteria, with two decisions that were Kai's to make. ## The name was a three-way conflict Three answers were live before this: | where | said | | --- | --- | | the shipped prompt | Coilyco Gaming **Intelligence Team** | | this issue's sourced fact | Coilyco Gaming **Robotics Division** | | the Forgejo ops account `full_name` | Coilyco **Robotic Operations Division** | **Kai chose Robotics Division.** `Intelligence Team` named a thing neither this issue nor the account uses, and it was shipping in every prompt, pinned by the shared-policy validator and two tests. All of it moves together. ## Where the statement lives `.agents/skills/coilyco-org`, composed by both definitions. It is the **only local skill root the two profiles share**, which is what turns "both agents read the same text" from a hope into a property a test holds. Removing it from Deep alone fails three tests with `deep composes no org source, so it answers from inference`. The prompt keeps one line naming the division and nothing else, per the copy-ownership constraint. ## On copy ownership This issue reserves the wording to Content Creator. Kai's instruction was to draft from the issue text and edit in review, so the prose in `references/organizations.md` is mine and is **meant to be rewritten**. It is one file with no code behind it. What is not a wording choice, and what the tests pin, is the separation: an agent is never Sirens Discord staff, and Sirens Discord staff are never Coilyco Gaming employees. #230 rests on that holding. ## The cost, stated plainly **1951 bytes of prompt per turn, on both profiles, forever.** The largest single raise on the ledger. A first draft cost 2827 and was cut without dropping a fact, but this is a real recurring cost for an org statement and worth knowing before it is treated as free. Anything still redundant in that file is paid on every turn. ## What #230 gets from this The relationship is now stated somewhere both agents read, which is the thing this issue said #230's "staff of Sirens Discord" answer needed in order to be coherent rather than improvised. #230 itself is untouched. ## Not reconciled, deliberately The datasets under `evaluations/` still contain replies saying `Coilyco Gaming Intelligence Team`. Those record what the model actually said on a given day. Rewriting them would falsify the evidence, so they stay as history rather than being treated as a live surface.