the agents should have 1st class knowledge of server rules

coilysiren commented

2026-08-13 01:48:12 +00:00

Owner

Echo should hold first-class knowledge of the server rules.

Resolved spec (design pass, 2026-08-15)

Source of truth - Echo reads the rules live from the rules channel. No versioned copy in repo config. A config-tracked verbatim copy and a copy-plus-drift-check hybrid were both rejected, because the rules channel is the canonical artifact and quoting a stale copy is a worse failure than occasionally not having the rules.

Cache TTL, was unresolved, now decided - 1 hour. Fetch on first need, serve from cache for an hour, refetch after. Per-request fetching was rejected as too chatty, and cache-until-restart as too stale.

Read-failure copy, was unresolved, now decided - name the failure and point at the channel:

I could not read the rules channel just now. It is at <#channel-id>.

Echo must not answer from memory, must not imply it checked, and must not silently serve a stale cache. Serving a labelled stale cache was considered and rejected, since it reintroduces the exact stale-quote failure that live reads were chosen to avoid.

Channel references carry IDs, not names. A curated entry written as #rules is rejected by ValidateGrounding as an invented channel and fails the turn with no repair. <#channel-id> passes both grounding and the identifier guard as of 0486de7. This binds the failure copy above and every channel any curated entry points at.

Blocked on - Discord MCP self-channel read, coilyco-bridge/deploy#387. Do not build the quoting work against a mock and call it done.

Acceptance

Echo quotes a rule verbatim from a live read and renders the rules channel as <#id>.
A rules edit in Discord reaches Echo's answer within one hour, with no restart and no deploy.
With the rules channel unreachable, Echo emits the failure copy above and zero rule text. A test asserts no rule content appears on that path.
No rules text is checked into repo config.

Paired - #210 covers the quoting and linking behaviour built on this source.

Echo should hold first-class knowledge of the server rules. ## Resolved spec (design pass, 2026-08-15) **Source of truth** - Echo reads the rules live from the rules channel. No versioned copy in repo config. A config-tracked verbatim copy and a copy-plus-drift-check hybrid were both rejected, because the rules channel is the canonical artifact and quoting a stale copy is a worse failure than occasionally not having the rules. **Cache TTL, was unresolved, now decided** - 1 hour. Fetch on first need, serve from cache for an hour, refetch after. Per-request fetching was rejected as too chatty, and cache-until-restart as too stale. **Read-failure copy, was unresolved, now decided** - name the failure and point at the channel: > I could not read the rules channel just now. It is at `<#channel-id>`. Echo must not answer from memory, must not imply it checked, and must not silently serve a stale cache. Serving a labelled stale cache was considered and rejected, since it reintroduces the exact stale-quote failure that live reads were chosen to avoid. **Channel references carry IDs, not names.** A curated entry written as `#rules` is rejected by `ValidateGrounding` as an invented channel and fails the turn with no repair. `<#channel-id>` passes both grounding and the identifier guard as of `0486de7`. This binds the failure copy above and every channel any curated entry points at. **Blocked on** - Discord MCP self-channel read, coilyco-bridge/deploy#387. Do not build the quoting work against a mock and call it done. **Acceptance** * Echo quotes a rule verbatim from a live read and renders the rules channel as `<#id>`. * A rules edit in Discord reaches Echo's answer within one hour, with no restart and no deploy. * With the rules channel unreachable, Echo emits the failure copy above and zero rule text. A test asserts no rule content appears on that path. * No rules text is checked into repo config. **Paired** - #210 covers the quoting and linking behaviour built on this source.

Rows
Columns

the agents should have 1st class knowledge of server rules #224

Resolved spec (design pass, 2026-08-15)

Design decision — rules source of truth

Dependency — this issue is blocked

Requirements once unblocked