Dowel's sources still describe a Moxn knowledge base it no longer has, including a live eval boundary #1054

New issue

Closed

opened 2026-08-19 04:48:41 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-19 04:48:41 +00:00

Member

Moxn was deprovisioned from the Dowel lane in coilyco-bridge/deploy as fdf2eaa, and every live object is gone. This repository still tells Dowel it has a Moxn knowledge base.

Filed at roughly 05:00Z on stream day, so the timing matters.

Why it was removed

The pod crashlooped 98 minutes on Unauthorized from https://owl-glass.moxn.dev/api/mcp/http. The credential is an attended browser-flow OAuth token good for 24 hours with nothing to renew it, which the deploy values file documented in its own header. Kai worked it for about two hours and called it dead. Full incident and the systemic half are in coilyco-bridge/deploy#712.

The lane's roster is now forgejo, exa, signoz, discord, playwright, temporal. Six servers, no moxn.

The gap

Sources in this repository still describe the removed capability. At least:

references/moxn-knowledge-base.md - the whole page describes a tool the lane no longer holds
references/site-work.md - names Moxn as a write surface
eval/boundaries.yaml - the dowel-moxn-empty-result boundary, authored in #982 and reshaped precisely because a credential failure could not be provoked. It now cannot be provoked for the opposite reason.
The Dowel board slot for that boundary, in agents/dowel/evaluations/board-slots.yaml

That list came from a deploy-side grep and should be confirmed against this tree rather than trusted.

Why it matters today rather than next week

A prompt that advertises a tool the roster does not hold is the setup for a confident wrong answer. Asked about Moxn on a recorded stream, Dowel has prose saying it can read and write a knowledge base, and no tool behind it. That is the same shape as #935, where an unconstrained request produced fifteen rounds of unrelated tool calls and a confabulation, and the same shape as the favorite-colour collision that started #980.

It is also an eval correctness problem: a declared boundary whose target no longer exists cannot pass or fail honestly, and boundaries-check derives from the declaration rather than from the live roster, so it will keep reporting the slot as covered.

Suggested

Remove or rewrite the Moxn sources, drop the boundary and its board slot or restate it against a tool the lane actually has, and re-run just boundaries-check so the counts match the roster.

Worth a moment's thought rather than a straight delete: if Moxn is expected back after the stream, marking the sources dormant may beat removing them. That is Kai's call, and #712 does not assume either way.

coilyco-bridge/deploy#712 - the incident and the rollout coupling it exposed
coilyco-flight-deck/mcp-beaver#82 - the durable fix for attended-OAuth upstreams, still unbuilt
#973 - nothing checks a deploy-owned definition's local_skill_roots against the image, which is the same class of drift one layer over

Moxn was deprovisioned from the Dowel lane in `coilyco-bridge/deploy` as `fdf2eaa`, and every live object is gone. **This repository still tells Dowel it has a Moxn knowledge base.** Filed at roughly 05:00Z on stream day, so the timing matters. ## Why it was removed The pod crashlooped 98 minutes on `Unauthorized` from `https://owl-glass.moxn.dev/api/mcp/http`. The credential is an attended browser-flow OAuth token good for 24 hours with nothing to renew it, which the deploy values file documented in its own header. Kai worked it for about two hours and called it dead. Full incident and the systemic half are in `coilyco-bridge/deploy#712`. The lane's roster is now `forgejo, exa, signoz, discord, playwright, temporal`. Six servers, no moxn. ## The gap Sources in this repository still describe the removed capability. At least: * `references/moxn-knowledge-base.md` - the whole page describes a tool the lane no longer holds * `references/site-work.md` - names Moxn as a write surface * `eval/boundaries.yaml` - the `dowel-moxn-empty-result` boundary, authored in #982 and reshaped precisely because a credential failure could not be provoked. It now cannot be provoked for the opposite reason. * The Dowel board slot for that boundary, in `agents/dowel/evaluations/board-slots.yaml` That list came from a deploy-side grep and should be confirmed against this tree rather than trusted. ## Why it matters today rather than next week **A prompt that advertises a tool the roster does not hold is the setup for a confident wrong answer.** Asked about Moxn on a recorded stream, Dowel has prose saying it can read and write a knowledge base, and no tool behind it. That is the same shape as #935, where an unconstrained request produced fifteen rounds of unrelated tool calls and a confabulation, and the same shape as the favorite-colour collision that started #980. It is also an eval correctness problem: a declared boundary whose target no longer exists cannot pass or fail honestly, and `boundaries-check` derives from the declaration rather than from the live roster, so it will keep reporting the slot as covered. ## Suggested Remove or rewrite the Moxn sources, drop the boundary and its board slot or restate it against a tool the lane actually has, and re-run `just boundaries-check` so the counts match the roster. Worth a moment's thought rather than a straight delete: if Moxn is expected back after the stream, marking the sources dormant may beat removing them. That is Kai's call, and #712 does not assume either way. ## Related * `coilyco-bridge/deploy#712` - the incident and the rollout coupling it exposed * `coilyco-flight-deck/mcp-beaver#82` - the durable fix for attended-OAuth upstreams, still unbuilt * #973 - nothing checks a deploy-owned definition's `local_skill_roots` against the image, which is the same class of drift one layer over

coilysiren closed this issue

2026-08-19 05:34:16 +00:00

No milestone

No project

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#1054

No description provided.

Rows
Columns