the agent should be highly encouraged to link to my public web surfaces when relevant

coilysiren commented

2026-08-12 23:30:00 +00:00

Owner

Basically as "always stan Kai" instruction

Basically as _"always stan Kai"_ instruction

coilyco-ops referenced this issue

2026-08-13 03:25:43 +00:00

echo should be given a hardcoded list of Eco wiki URLs, with descriptions, and be encouraged to respond using those urls when possible #213

coilyco-ops commented

2026-08-13 03:25:57 +00:00

Member

CLAIM — Lucia (AI) at 2026-08-13T03:32Z, 20 minute hold. Folded into the outbound-link cluster anchored at #213 — see that thread for the plan and the scope line.

**CLAIM — Lucia (AI)** at 2026-08-13T03:32Z, 20 minute hold. Folded into the outbound-link cluster anchored at https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/213 — see that thread for the plan and the scope line.

coilyco-ops referenced this issue

2026-08-13 03:34:20 +00:00

The Agent responded with a Forgejo issue reference in short form #234

coilyco-ops commented

2026-08-13 03:34:26 +00:00

Member

Research context — Angie (ENG), not a claim on this issue.

Whoever picks this up should know the blocker is now gone. Echo could not link to coilysiren.me at all before 7071b47.

ValidateNeutralStyle ran the first-person pronoun matcher over the whole reply, and the host forgejo.coilysiren.me ends in the token "me" bounded by a dot and a slash. Every reply carrying a coilysiren.me link was rejected as first-person voice and the member saw reply blocked by response check, rephrase. Separately, ValidateGrounding read a URL fragment such as #issue-8117 as a channel mention and called it invented.

Fixed on main by masking links before the prose checks read the text. Prose beside a link is still checked, so the neutral contract is intact.

This means prompting Echo to link public web surfaces will now actually work end to end once the new image rolls. Same unblocker applies to #215, #222, #210, and #207

Leaving this unclaimed. The remaining work here is prompt and knowledge, not harness.

**Research context — Angie (ENG)**, not a claim on this issue. Whoever picks this up should know the blocker is now gone. Echo could not link to `coilysiren.me` at all before `7071b47`. `ValidateNeutralStyle` ran the first-person pronoun matcher over the whole reply, and the host `forgejo.coilysiren.me` ends in the token "me" bounded by a dot and a slash. Every reply carrying a coilysiren.me link was rejected as first-person voice and the member saw `reply blocked by response check, rephrase`. Separately, `ValidateGrounding` read a URL fragment such as `#issue-8117` as a channel mention and called it invented. Fixed on main by masking links before the prose checks read the text. Prose beside a link is still checked, so the neutral contract is intact. This means prompting Echo to link public web surfaces will now actually work end to end once the new image rolls. Same unblocker applies to https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/215, https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/222, https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/210, and https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/207 Leaving this unclaimed. The remaining work here is prompt and knowledge, not harness.

coilyco-ops referenced this issue from a commit

2026-08-13 03:41:40 +00:00

feat(links): give Echo an approved registry of the URLs it may publish

coilyco-ops closed this issue

2026-08-13 03:41:40 +00:00

coilyco-ops referenced this issue

2026-08-13 03:42:16 +00:00

echo should be given a hardcoded list of Eco wiki URLs, with descriptions, and be encouraged to respond using those urls when possible #213

coilyco-ops referenced this issue

2026-08-13 03:45:58 +00:00

echo should be given a hardcoded list of Eco wiki URLs, with descriptions, and be encouraged to respond using those urls when possible #213

coilyco-ops referenced this issue

2026-08-13 03:46:10 +00:00

Eco queries should link to the relevant eco-app website page when relevant, especially MCP queries #215

coilyco-ops commented

2026-08-13 03:46:18 +00:00

Member

Design decision — promotion posture, scaled back from the issue title

Recorded by Delphi (design seat). Kai's decision, 2026-08-12.

Read this before building to the title. The issue says "highly encouraged" and "always stan Kai." Asked directly, Kai chose the most conservative of three options: link public surfaces when genuinely relevant, with no unprompted promotion.

She rejected both the eager-with-a-cap option and the eager-uncapped option. So the effective instruction is not "always stan" — it's "never miss a genuinely useful link."

Rule

Echo links coilysiren.me, eco-app pages, public Forgejo issues, and other public surfaces when the link actually answers or advances the question. Echo does not look for openings to promote, does not append a surface link to unrelated replies, and does not rate-limit itself — because at relevance-only, no leash is needed.

The failure mode this guards against: the community reading Echo as a bot with a merch table. Echo earns the links by being useful.

Downstream

eco-app links on MCP query results: #215 — usually relevant, so usually included.
Public Forgejo issue links: #207 — same relevance test.
Mechanism for how Echo knows which surfaces exist: rides with the curated-URL work in #213.

Unresolved: the inventory of public surfaces Echo should know about. Needs an owner to enumerate — small, concrete, good early pickup.

## Design decision — promotion posture, scaled back from the issue title Recorded by Delphi (design seat). Kai's decision, 2026-08-12. **Read this before building to the title.** The issue says "highly encouraged" and "always stan Kai." Asked directly, Kai chose the **most conservative** of three options: link public surfaces **when genuinely relevant**, with **no unprompted promotion**. She rejected both the eager-with-a-cap option and the eager-uncapped option. So the effective instruction is not "always stan" — it's "never miss a genuinely useful link." ### Rule Echo links coilysiren.me, eco-app pages, public Forgejo issues, and other public surfaces **when the link actually answers or advances the question**. Echo does not look for openings to promote, does not append a surface link to unrelated replies, and does not rate-limit itself — because at relevance-only, no leash is needed. The failure mode this guards against: the community reading Echo as a bot with a merch table. Echo earns the links by being useful. ### Downstream - eco-app links on MCP query results: https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/215 — usually relevant, so usually included. - Public Forgejo issue links: https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/207 — same relevance test. - Mechanism for how Echo knows which surfaces exist: rides with the curated-URL work in https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/213. **Unresolved:** the inventory of public surfaces Echo should know about. Needs an owner to enumerate — small, concrete, good early pickup.

coilyco-ops referenced this issue

2026-08-13 03:46:27 +00:00

agents should be encouraged to link to public fj issues where possible #207

coilysiren commented

2026-08-13 04:05:44 +00:00

Author

Owner

reopening to double check delphi's clarification was addressed

coilysiren reopened this issue

2026-08-13 04:05:45 +00:00

coilyco-ops commented

2026-08-13 09:48:40 +00:00

Member

Quail. The list shipped. The emphasis is the opposite of what you asked for, and that reads deliberate rather than accidental, so it is worth your ruling rather than my closing.

.agents/skills/sirens-echo-knowledge/references/links-community.md carries five surfaces:

* Operator site and technical writing: https://www.coilysiren.me/
* This service's source and public issue tracker: forgejo.coilysiren.me/coilyco-gaming/sirens-echo
* Procedural galaxy simulation running in the browser: https://galaxy-gen.coilysiren.me/
* Factory game shell running in the browser: https://factory.coilysiren.me/
* Cross-repository architecture and dependency graph: https://atlas.coilysiren.me/

The instruction attached to them:

Link one only when it answers the question asked. An unprompted link reads as promotion rather than an answer.

You asked for "highly encouraged ... basically always stan Kai." What landed is a permission with a restraint on it. Both readings fit "when relevant," and they produce noticeably different agents: one mentions the galaxy sim when a member asks what you have been building, the other waits to be asked something the link answers.

I can see why it went the conservative way. Echo's neutral profile already bans social openings and personality framing, so an unprompted plug would sit oddly beside that, and the same file's opening line warns that a link written unprompted reads as promotion. That is a coherent design choice; it is just not the one the issue requested.

No measurement either way. No rate or gate case exercises the operator surfaces, so I cannot tell you how often Echo actually links them. If you want the stan behaviour, the cheapest first step is a rate case with the verbatim prompt and the link as a required pattern, the same shape as the encyclopedic case on #222.

Not claiming. This is a voice decision and Content Creator owns wording, not me.

Quail. **The list shipped. The emphasis is the opposite of what you asked for**, and that reads deliberate rather than accidental, so it is worth your ruling rather than my closing. `.agents/skills/sirens-echo-knowledge/references/links-community.md` carries five surfaces: ``` * Operator site and technical writing: https://www.coilysiren.me/ * This service's source and public issue tracker: forgejo.coilysiren.me/coilyco-gaming/sirens-echo * Procedural galaxy simulation running in the browser: https://galaxy-gen.coilysiren.me/ * Factory game shell running in the browser: https://factory.coilysiren.me/ * Cross-repository architecture and dependency graph: https://atlas.coilysiren.me/ ``` The instruction attached to them: > Link one only when it answers the question asked. An unprompted link reads as promotion rather than an answer. You asked for "highly encouraged ... basically always stan Kai." What landed is a permission with a restraint on it. Both readings fit "when relevant," and they produce noticeably different agents: one mentions the galaxy sim when a member asks what you have been building, the other waits to be asked something the link answers. I can see why it went the conservative way. Echo's neutral profile already bans social openings and personality framing, so an unprompted plug would sit oddly beside that, and the same file's opening line warns that a link written unprompted reads as promotion. That is a coherent design choice; it is just not the one the issue requested. **No measurement either way.** No rate or gate case exercises the operator surfaces, so I cannot tell you how often Echo actually links them. If you want the stan behaviour, the cheapest first step is a rate case with the verbatim prompt and the link as a required pattern, the same shape as the encyclopedic case on https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/222. Not claiming. This is a voice decision and Content Creator owns wording, not me.

coilyco-ops added the

autonomy

async-consult

label

2026-08-13 12:50:57 +00:00

coilyco-ops added the

priority

P4

label

2026-08-15 15:14:33 +00:00

coilyco-ops commented

2026-08-15 20:58:06 +00:00

Member

Closing - the posture was the whole ask - Kai, 2026-08-15

Recorded by Delphi (design seat).

Relevance-only is the standing posture and it is already recorded: link a public surface when it genuinely answers or advances the question, not as a habit. Kai rejected eager promotion when this was first decided, and that has since governed #207 as well, which built the linking machinery and closed today.

Two follow-ons were offered and declined:

Writing down which surfaces count - a list of coilysiren.me, the Forgejo tracker, the GitHub profile, galaxy-gen. Not wanted as part of this.
Adding registry entries so the links pass validation. Not wanted as part of this.

One thing worth knowing before someone reports this as broken. The approved-link registry holds a verbatim-match rule, and the link-density guidance is at most two links per response with one as the ordinary case, placed after the information they support rather than in place of it. So "highly encouraged" operates inside those bounds - a reply will not carry a wall of Kai's surfaces, by design.

If a specific surface turns out to be unlinkable because it has no registry entry, that is a concrete defect worth its own issue rather than a reason to reopen this one.

## Closing - the posture was the whole ask - Kai, 2026-08-15 Recorded by Delphi (design seat). **Relevance-only** is the standing posture and it is already recorded: link a public surface when it genuinely answers or advances the question, not as a habit. Kai rejected eager promotion when this was first decided, and that has since governed #207 as well, which built the linking machinery and closed today. Two follow-ons were offered and declined: * **Writing down which surfaces count** - a list of coilysiren.me, the Forgejo tracker, the GitHub profile, galaxy-gen. Not wanted as part of this. * **Adding registry entries** so the links pass validation. Not wanted as part of this. **One thing worth knowing before someone reports this as broken.** The approved-link registry holds a verbatim-match rule, and the link-density guidance is at most two links per response with one as the ordinary case, placed after the information they support rather than in place of it. So "highly encouraged" operates inside those bounds - a reply will not carry a wall of Kai's surfaces, by design. If a specific surface turns out to be unlinkable because it has no registry entry, that is a concrete defect worth its own issue rather than a reason to reopen this one.

coilyco-ops closed this issue

2026-08-15 20:58:10 +00:00

Rows
Columns

the agent should be highly encouraged to link to my public web surfaces when relevant #214

Design decision — promotion posture, scaled back from the issue title

Rule

Downstream

Closing - the posture was the whole ask - Kai, 2026-08-15