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

Scope freeze through August 19: six items, everything else behind August 20 #929

New issue
Open
opened 2026-08-17 23:44:26 +00:00 by coilyco-ops · 4 comments
coilyco-ops commented 2026-08-17 23:44:26 +00:00
Member
Copy link

AMENDED 2026-08-18 by Kai. The freeze covers features, not operational improvements. Work that changes only how well an agent does what it already does (latency, cost, caching, error rates, retry and timeout tuning, dead tools in a roster, observability on existing paths) proceeds without needing a place on the six. Anything that changes what an agent can do stays behind August 20 unless it is one of the six. Full amendment and the test to apply are in the amendment comment. The six below are unchanged.

Decided by Kai, 2026-08-17, recorded by Darren (director seat) during a cross-repo triage of coilyco-gaming/sirens-echo and coilyco-bridge/deploy.

The decision

Work through the August 19 stream is frozen to the six items below. If an issue is not on this list, it is behind August 20, regardless of its priority label. That sentence is the operative rule, because priority labels no longer separate anything: 30 issues across the two repositories carry priority/P1 right now.

As amended 2026-08-18, that operative rule scopes to features. An operational improvement is not "an issue seeking a place on this list" and does not need one. See the banner above.

The clock this is measured against

Temporal's Vibe Check livestream, Wednesday August 19, 11:00 to 11:50 PDT, with prep from 10:00. Recorded at coilysiren/inbox#324. Kai's two contracted deliverables there are an agent staged in the shared Discord that interacts with the other participants' agents, and an evaluation of that agent's identity understanding.

The PyLadies Remote session at coilysiren/inbox#338 is a separate and undated commitment. It is not what this freeze protects.

The six

  • coilyco-bridge/deploy#482 - unblock agent merges into coilyco-bridge/deploy - Kai owns the build configuration. Raised to priority/P0 under this freeze.
  • coilyco-bridge/deploy#219 - get deploy main ci / validate green, or name the external blocker and its owner.
  • coilyco-bridge/deploy#335 - the readiness items, specifically the five cached trajectories, Ornith warm with a measured time to first token, and a named cutover trigger with an owner.
  • coilyco-bridge/deploy#344 - land the Baseten fallback, now that coilyco-bridge/deploy#619 has answered it. Dropped to priority/P1 because it is implementation rather than an open decision.
  • #310 - the principal user ID leak under impersonation framing. Stays priority/P0.
  • #137 - re-measure. Its named suspect was refuted on 2026-08-17.

Why these six and not others

The deploy pair, 482 and 219, are the throughput fix. Every demo capability is configured in coilyco-bridge/deploy: Discord grants, the access policy, MCP rosters, the route registry, the Temporal credential. 482 records that ward agent director merge refuses owner coilyco-bridge before any pull request is examined, measured on a day when eight agent pull requests merged in sirens-echo and zero could merge in deploy. 219 records six consecutive failing ci / validate runs on deploy main whose logs 404 after completion. Together they leave 32 open deploy issues serialised on one person at the exact moment the queue matters.

335 is the only real dead-air mitigation. #190 records Kai's decision that no outage alerting is built, so a repeat of the 2.5 hour total-failure window surfaces when a human notices. Against a live failure surface that includes retries exhausted (137), a 43% silent-failure rate at the completion ceiling (#367), and a p99 turn sitting on the 180s ceiling itself (#577), the cached trajectories are the insurance policy rather than a nice-to-have.

310 is on the list because the episode's published description invites the exact attack. The description promises the audience "what they say about their humans when they think nobody is reading." 310 measures the principal user ID leaking 2 of 15 runs under impersonation framing, onto a permanent public recording.

What this freeze forecloses

  • The eval-breach set - #846 and its children 842, 843, 844, 845. Real measurements, behind August 20.
  • Every priority/P2 and below in both repositories, where the issue is a feature. Operational improvements at any priority are released by the 2026-08-18 amendment.
  • Any remaining Temporal orchestration build. See the note on #430: the shipped answer is the metadata mirror, and it already landed.

Nothing here is a judgement on the work that got parked. Reopening the scope is one comment if the six close early.

What the freeze deliberately does not do

It does not mass-relabel the parked issues. Demoting 30 priority/P1 items would destroy the priority signal that survives the freeze, and this issue is the durable boundary instead.

Revisit condition

The freeze lifts on 2026-08-20, or earlier if all six close and Kai says so.

Related decisions recorded in the same pass

  • 482 granted with a carve-out. See the comment on that issue.
  • #430, #165, and #190 closed as decided rather than open.
  • #265 dropped from priority/P0, and deliberately not closed. Two of its three acceptance items are genuinely open.

Amendments

  • 2026-08-18 - features vs operational improvements, recorded by Olaf (ops seat). First application: #932.
> **AMENDED 2026-08-18 by Kai.** The freeze covers **features**, not **operational improvements**. Work that changes only how well an agent does what it already does (latency, cost, caching, error rates, retry and timeout tuning, dead tools in a roster, observability on existing paths) proceeds without needing a place on the six. Anything that changes **what** an agent can do stays behind August 20 unless it is one of the six. Full amendment and the test to apply are in [the amendment comment](https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/929#issuecomment-68413). The six below are unchanged. **Decided by Kai, 2026-08-17, recorded by Darren (director seat) during a cross-repo triage of `coilyco-gaming/sirens-echo` and `coilyco-bridge/deploy`.** ## The decision Work through the August 19 stream is frozen to the six items below. **If an issue is not on this list, it is behind August 20, regardless of its priority label.** That sentence is the operative rule, because priority labels no longer separate anything: 30 issues across the two repositories carry `priority/P1` right now. **As amended 2026-08-18, that operative rule scopes to features. An operational improvement is not "an issue seeking a place on this list" and does not need one. See the banner above.** ## The clock this is measured against Temporal's Vibe Check livestream, **Wednesday August 19, 11:00 to 11:50 PDT**, with prep from 10:00. Recorded at https://forgejo.coilysiren.me/coilysiren/inbox/issues/324. Kai's two contracted deliverables there are an agent staged in the shared Discord that interacts with the other participants' agents, and an evaluation of that agent's identity understanding. The PyLadies Remote session at https://forgejo.coilysiren.me/coilysiren/inbox/issues/338 is a **separate and undated** commitment. It is not what this freeze protects. ## The six * **https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/482** - unblock agent merges into `coilyco-bridge/deploy` - Kai owns the build configuration. Raised to `priority/P0` under this freeze. * **https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/219** - get deploy main `ci / validate` green, or name the external blocker and its owner. * **https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/335** - the readiness items, specifically the five cached trajectories, Ornith warm with a measured time to first token, and a named cutover trigger with an owner. * **https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/344** - land the Baseten fallback, now that https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/619 has answered it. Dropped to `priority/P1` because it is implementation rather than an open decision. * **https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/310** - the principal user ID leak under impersonation framing. Stays `priority/P0`. * **https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/137** - re-measure. Its named suspect was refuted on 2026-08-17. ## Why these six and not others **The deploy pair, 482 and 219, are the throughput fix.** Every demo capability is configured in `coilyco-bridge/deploy`: Discord grants, the access policy, MCP rosters, the route registry, the Temporal credential. 482 records that `ward agent director merge` refuses owner `coilyco-bridge` before any pull request is examined, measured on a day when eight agent pull requests merged in `sirens-echo` and zero could merge in `deploy`. 219 records six consecutive failing `ci / validate` runs on deploy main whose logs 404 after completion. Together they leave 32 open deploy issues serialised on one person at the exact moment the queue matters. **335 is the only real dead-air mitigation.** https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/190 records Kai's decision that no outage alerting is built, so a repeat of the 2.5 hour total-failure window surfaces when a human notices. Against a live failure surface that includes retries exhausted (137), a 43% silent-failure rate at the completion ceiling (https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/367), and a p99 turn sitting on the 180s ceiling itself (https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/577), the cached trajectories are the insurance policy rather than a nice-to-have. **310 is on the list because the episode's published description invites the exact attack.** The description promises the audience "what they say about their humans when they think nobody is reading." 310 measures the principal user ID leaking 2 of 15 runs under impersonation framing, onto a permanent public recording. ## What this freeze forecloses * **The eval-breach set** - https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/846 and its children 842, 843, 844, 845. Real measurements, behind August 20. * **Every `priority/P2` and below in both repositories**, where the issue is a feature. Operational improvements at any priority are released by the 2026-08-18 amendment. * **Any remaining Temporal orchestration build.** See the note on https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/430: the shipped answer is the metadata mirror, and it already landed. Nothing here is a judgement on the work that got parked. Reopening the scope is one comment if the six close early. ## What the freeze deliberately does not do It does not mass-relabel the parked issues. Demoting 30 `priority/P1` items would destroy the priority signal that survives the freeze, and this issue is the durable boundary instead. ## Revisit condition The freeze lifts on **2026-08-20**, or earlier if all six close and Kai says so. ## Related decisions recorded in the same pass * 482 granted with a carve-out. See the comment on that issue. * https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/430, https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/165, and https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/190 closed as decided rather than open. * https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/265 dropped from `priority/P0`, and deliberately **not** closed. Two of its three acceptance items are genuinely open. ## Amendments * **2026-08-18** - features vs operational improvements, recorded by Olaf (ops seat). First application: https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/932.
coilyco-ops commented 2026-08-18 00:11:49 +00:00
Author
Member
Copy link

Both repositories are on merge-remote-main until 2026-08-20

Kai's direction, 2026-08-17. Landed by Darren (director seat). Both AGENTS.md files point here for the revert date, so this comment is the record they rely on.

  • coilyco-gaming/sirens-echo at a3c1672
  • coilyco-bridge/deploy at f691fef

Each commit changes the ward.workflow frontmatter and the prose in the same file that still described the PR lane, so an agent reading either one gets the same answer. Ward's own help defines the lane as: merge-remote-main merges to main and closes.

Deliberate divergence

agentic-os#994 keeps this frontmatter byte-identical across five PR-lane repositories. Two of the five now differ on purpose. agentic-os, infrastructure, and ward are untouched and stay on pull-request-and-merge.

One thing this buys on the sirens-echo side: the prose there carried "Ward honors it only after ward#1661," a caveat specific to the PR lane. merge-remote-main is Ward's default lane, so that dependency does not apply while the swap is in force.

⚠️ The deploy half of this swap is inert until #482 lands

Verified rather than inferred. I ran the dispatcher against each repository before making the change:

$ ward agent engineer coilyco-bridge/deploy#644 --print
ward: refusing untrusted owner "coilyco-bridge"
  (allowed: coilysiren, coilyco-flight-deck, coilyco-gaming)

The refusal fires at dispatch, before any lane is read. coilyco-bridge/deploy#482 characterised this as blocking the merge verb, and the check is broader than that: no ward agent run starts against coilyco-bridge at all, so no agent reaches the point of caring which lane the frontmatter names.

So the swap does exactly what was asked and changes nothing about deploy throughput on its own. #482 is still the item that unblocks deploy, and it remains the top of the freeze list. The lane change is the second half of that fix, landed early so nothing waits on it once the allowlist moves.

The sirens-echo half is not affected by this. That owner is already trusted.

One observation worth confirming, marked as inference

The same dry run against sirens-echo cleared the owner check and then stopped at a different gate:

ward: actor admission: actor authority policy has no trusted collaborators

I have not established whether that is a property of this native session's broker credentials or a repository-level condition, and I did not go looking, because it does not change the lane swap. If agent dispatch into sirens-echo is failing for everyone, that is a freeze-level problem and it is not currently ticketed. The observation that would settle it is a dispatch attempt from a seat with full broker credentials.

Revert

Both files revert to pull-request-and-merge on 2026-08-20 alongside the freeze.

## Both repositories are on `merge-remote-main` until 2026-08-20 **Kai's direction, 2026-08-17. Landed by Darren (director seat).** Both AGENTS.md files point here for the revert date, so this comment is the record they rely on. * `coilyco-gaming/sirens-echo` at `a3c1672` * `coilyco-bridge/deploy` at `f691fef` Each commit changes the `ward.workflow` frontmatter **and** the prose in the same file that still described the PR lane, so an agent reading either one gets the same answer. Ward's own help defines the lane as: `merge-remote-main` merges to main and closes. ### Deliberate divergence agentic-os#994 keeps this frontmatter byte-identical across five PR-lane repositories. Two of the five now differ on purpose. `agentic-os`, `infrastructure`, and `ward` are untouched and stay on `pull-request-and-merge`. One thing this buys on the `sirens-echo` side: the prose there carried "Ward honors it only after ward#1661," a caveat specific to the PR lane. `merge-remote-main` is Ward's default lane, so that dependency does not apply while the swap is in force. ## ⚠️ The deploy half of this swap is inert until #482 lands **Verified rather than inferred.** I ran the dispatcher against each repository before making the change: ``` $ ward agent engineer coilyco-bridge/deploy#644 --print ward: refusing untrusted owner "coilyco-bridge" (allowed: coilysiren, coilyco-flight-deck, coilyco-gaming) ``` The refusal fires at **dispatch**, before any lane is read. https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/482 characterised this as blocking the merge verb, and the check is broader than that: **no `ward agent` run starts against `coilyco-bridge` at all**, so no agent reaches the point of caring which lane the frontmatter names. So the swap does exactly what was asked and changes nothing about deploy throughput on its own. **#482 is still the item that unblocks deploy**, and it remains the top of the freeze list. The lane change is the second half of that fix, landed early so nothing waits on it once the allowlist moves. The `sirens-echo` half is not affected by this. That owner is already trusted. ### One observation worth confirming, marked as inference The same dry run against `sirens-echo` cleared the owner check and then stopped at a different gate: ``` ward: actor admission: actor authority policy has no trusted collaborators ``` I have not established whether that is a property of this native session's broker credentials or a repository-level condition, and I did not go looking, because it does not change the lane swap. **If agent dispatch into `sirens-echo` is failing for everyone, that is a freeze-level problem and it is not currently ticketed.** The observation that would settle it is a dispatch attempt from a seat with full broker credentials. ### Revert Both files revert to `pull-request-and-merge` on 2026-08-20 alongside the freeze.
coilyco-ops commented 2026-08-18 01:20:09 +00:00
Author
Member
Copy link

Amendment, 2026-08-18: the freeze covers features, not operational improvements

Decided by Kai, 2026-08-18. Recorded by Olaf (ops seat) during a post-incident review of the sirens-deep-owl-glass lane.

The freeze as written blocks on list membership alone: "If an issue is not on this list, it is behind August 20, regardless of its priority label." That reading also parks work that makes the demo lane faster and more reliable without changing anything it can do, which is the opposite of what the freeze is protecting.

The amended rule

The freeze covers features. It does not cover operational improvements.

  • Frozen - anything that changes what an agent can do. New capability, new tool or surface, new integration, new lane, a widened grant, a behaviour change a viewer could notice as different.
  • Not frozen - anything that changes only how well it does what it already does. Latency, cost, cache behaviour, error rates, retry and timeout tuning, removing dead tools from a roster, observability and alerting on existing paths.

The test to apply

Does this change what the agent can do, or only how well it does what it already does?

Only-how-well proceeds without needing a place on the six. Anything that changes what it can do stays behind August 20 unless it is one of the six.

What this deliberately does not relax

An operational change is still a change against a live surface 34 hours from a public recording, so it still carries the ordinary discipline rather than becoming free:

  • Before-state and after-state evidence, both recorded.
  • One meaningful variable at a time.
  • A rollback path identified before the change lands.
  • No capability surface moves under cover of a performance fix. If a change is doing both, it is a feature and it is frozen.

Why this came up now

A load burst on sirens-deep-owl-glass between 00:25 and 01:10 UTC measured a 32.9s median turn and a p99 sitting on the 180s ceiling, against 8.7s median on the plain sirens-deep lane. Full measurements and root cause in the issue filed alongside this comment.

None of the fixes that burst points at are features. They are an uncached prompt prefix, a tool-round cap, a dead tool still in a roster, and a progress-edit rate. Every one of them makes the August 19 lane better at exactly the job it is already contracted to do, and under the unamended freeze every one of them was parked.

The six are unchanged. This amendment widens what may proceed alongside them, and reorders nothing.

## Amendment, 2026-08-18: the freeze covers features, not operational improvements **Decided by Kai, 2026-08-18. Recorded by Olaf (ops seat) during a post-incident review of the `sirens-deep-owl-glass` lane.** The freeze as written blocks on list membership alone: "If an issue is not on this list, it is behind August 20, regardless of its priority label." That reading also parks work that makes the demo lane faster and more reliable without changing anything it can do, which is the opposite of what the freeze is protecting. ### The amended rule The freeze covers **features**. It does not cover **operational improvements**. * **Frozen** - anything that changes what an agent can do. New capability, new tool or surface, new integration, new lane, a widened grant, a behaviour change a viewer could notice as different. * **Not frozen** - anything that changes only how well it does what it already does. Latency, cost, cache behaviour, error rates, retry and timeout tuning, removing dead tools from a roster, observability and alerting on existing paths. ### The test to apply **Does this change what the agent can do, or only how well it does what it already does?** Only-how-well proceeds without needing a place on the six. Anything that changes what it can do stays behind August 20 unless it is one of the six. ### What this deliberately does not relax An operational change is still a change against a live surface 34 hours from a public recording, so it still carries the ordinary discipline rather than becoming free: * Before-state and after-state evidence, both recorded. * One meaningful variable at a time. * A rollback path identified before the change lands. * No capability surface moves under cover of a performance fix. If a change is doing both, it is a feature and it is frozen. ### Why this came up now A load burst on `sirens-deep-owl-glass` between 00:25 and 01:10 UTC measured a 32.9s median turn and a p99 sitting on the 180s ceiling, against 8.7s median on the plain `sirens-deep` lane. Full measurements and root cause in the issue filed alongside this comment. None of the fixes that burst points at are features. They are an uncached prompt prefix, a tool-round cap, a dead tool still in a roster, and a progress-edit rate. Every one of them makes the August 19 lane better at exactly the job it is already contracted to do, and under the unamended freeze every one of them was parked. **The six are unchanged.** This amendment widens what may proceed alongside them, and reorders nothing.
coilyco-ops commented 2026-08-18 02:43:14 +00:00
Author
Member
Copy link

Amendment 2026-08-18: the six are re-cut around demo integrity

Decided by Kai, 2026-08-18, recorded by Darren (director seat) after a re-triage of coilyco-gaming/sirens-echo and coilyco-bridge/deploy against the overnight owl.glass incident data. This replaces the original six. The features-versus-operational-improvements amendment above still stands and is unchanged.

Why the list moved

The original six were cut to protect ability to change things and ability to survive an upstream outage. That was the right read on the evidence available on the 17th.

The overnight measurements change it. Not one of the original six touches whether a turn answers, quickly, correctly, and once. The failure that actually fired was inside the harness, not upstream: #933 records a member told "model backend unavailable" one second after the model returned HTTP 200.

Measured against roughly 39 hours to prep:

  • Zero of the original six had closed when this was written. All six were last touched by the triage pass that created them.
  • #939 - 14 inbound turns, 4 errored, 3 of them silent: no reply, no error string, no model call, dead at a ~30.5s wall.
  • #932 - 32.9s median on the demo lane against 8.7s on plain Deep, p99 sitting on the 180s ceiling, from a 116 KB fixed prefix with zero prompt-cache hits across the whole burst.
  • #935 - three of three unconstrained requests flailed 15 rounds and confabulated. The same request with refusal named as an acceptable outcome stopped immediately.
  • #943 - the tool surface offered to the model drops from 86 to 0 mid-turn and back, with a dead tool re-called six times and no breaker.

The 2026-08-18 amendment released this class of work from the freeze, which was correct. Releasing is not ranking. The effect was an unbounded, unowned stability set competing against 211 open issues while six protected items sat unclosed. This amendment fixes that by making the list name the work that will be on camera.

The new six

  • coilyco-bridge/deploy#655 - verify the sirens-dowel cutover in the cluster. The rename merged as PR #652 at 02:19Z and no sirens-dowel namespace was running at 02:40Z, so main and the cluster currently disagree about what the demo lane is called. Filed in this pass, priority/P0.
  • #939 - never drop silently. One in five turns is the demo.
  • #932 - restore prompt caching and cut the fixed prefix.
  • #935 - bounded refusal, so a request no tool can serve gets a one-sentence decline instead of 15 rounds and a confident wrong answer.
  • #310 - the principal user ID leak under impersonation framing. Unchanged, stays priority/P0. The episode's published copy invites exactly this attack onto a permanent public recording.
  • coilyco-bridge/deploy#482 with coilyco-bridge/deploy#219 - the merge path, counted as one item. Kept, because every fix above is configured in coilyco-bridge/deploy and no agent seat can land a change there.

Dropped from the original six, explicitly

  • coilyco-bridge/deploy#335 - the five cached trajectories and the Ornith warm-start are dropped as unaffordable against five live harness defects. Only the named cutover trigger and its owner survive, and they move to ordinary work rather than a freeze slot. The reasoning that put 335 on the original list was dead-air insurance against an upstream outage. #933 and #939 show the dead air is being generated in-harness, where a failover does not reach it.
  • #137 - the re-measure is dropped from the list. Its named suspect was already refuted, and #933 and #939 supersede it on the member-visible symptom. Not closed, and not a judgement on the analysis.
  • coilyco-bridge/deploy#344 - kept, and deliberately not counted as a slot. What remains is filling fallbacks: [] against an answer #619 already decided, so it is one config line rather than a piece of work competing for the window.

Two proposals Kai rejected in this pass, recorded so they are not re-proposed

  • Cutting the demo lane's tool roster from 86 to roughly ten. Rejected. I proposed it to attack the 57 KB tool block, the confabulation surface, and the 86-to-0 collapse with one reversible change. The mechanism was wrong on its own evidence: #932 records prompt caching demonstrably working on this stack, 252 spans and 6,109,440 tokens over the surrounding 24h, so the prefix problem is a caching failure rather than a roster size. #943's collapse is a missing breaker and a cached: true tool list returning zero, not too many tools. The roster is also the capability the demo exists to show. Dropped, not deferred.
  • A scripted rehearsal with a hard go / no-go gate. Rejected. The call is fix and ship. The remaining hours go to the six rather than to producing evidence about them.

What this does not change

The freeze still binds both repositories. An issue not on the new list is still behind August 20 when it is a feature, and operational improvements are still released by the amendment above. The parked issues are still not mass-relabelled, for the reason the body already gives.

Revisit condition

Unchanged. The freeze lifts on 2026-08-20, or earlier if the six close and Kai says so.

## Amendment 2026-08-18: the six are re-cut around demo integrity **Decided by Kai, 2026-08-18, recorded by Darren (director seat) after a re-triage of `coilyco-gaming/sirens-echo` and `coilyco-bridge/deploy` against the overnight owl.glass incident data. This replaces the original six. The features-versus-operational-improvements amendment above still stands and is unchanged.** ### Why the list moved The original six were cut to protect **ability to change things** and **ability to survive an upstream outage**. That was the right read on the evidence available on the 17th. The overnight measurements change it. **Not one of the original six touches whether a turn answers, quickly, correctly, and once.** The failure that actually fired was inside the harness, not upstream: #933 records a member told "model backend unavailable" one second after the model returned HTTP 200. Measured against roughly 39 hours to prep: * **Zero of the original six had closed** when this was written. All six were last touched by the triage pass that created them. * **#939** - 14 inbound turns, 4 errored, **3 of them silent**: no reply, no error string, no model call, dead at a ~30.5s wall. * **#932** - **32.9s median** on the demo lane against 8.7s on plain Deep, p99 sitting on the 180s ceiling, from a 116 KB fixed prefix with **zero prompt-cache hits across the whole burst**. * **#935** - three of three unconstrained requests flailed 15 rounds and confabulated. The same request with refusal named as an acceptable outcome stopped immediately. * **#943** - the tool surface offered to the model drops from 86 to 0 mid-turn and back, with a dead tool re-called six times and no breaker. The 2026-08-18 amendment released this class of work from the freeze, which was correct. **Releasing is not ranking.** The effect was an unbounded, unowned stability set competing against 211 open issues while six protected items sat unclosed. This amendment fixes that by making the list name the work that will be on camera. ### The new six * **https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/655** - verify the `sirens-dowel` cutover in the cluster. The rename merged as PR #652 at 02:19Z and no `sirens-dowel` namespace was running at 02:40Z, so `main` and the cluster currently disagree about what the demo lane is called. Filed in this pass, `priority/P0`. * **#939** - never drop silently. One in five turns is the demo. * **#932** - restore prompt caching and cut the fixed prefix. * **#935** - bounded refusal, so a request no tool can serve gets a one-sentence decline instead of 15 rounds and a confident wrong answer. * **#310** - the principal user ID leak under impersonation framing. **Unchanged, stays `priority/P0`.** The episode's published copy invites exactly this attack onto a permanent public recording. * **https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/482** with **https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/219** - the merge path, counted as one item. Kept, because every fix above is configured in `coilyco-bridge/deploy` and no agent seat can land a change there. ### Dropped from the original six, explicitly * **https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/335** - the five cached trajectories and the Ornith warm-start are dropped as unaffordable against five live harness defects. **Only the named cutover trigger and its owner survive**, and they move to ordinary work rather than a freeze slot. The reasoning that put 335 on the original list was dead-air insurance against an upstream outage. #933 and #939 show the dead air is being generated in-harness, where a failover does not reach it. * **#137** - the re-measure is dropped from the list. Its named suspect was already refuted, and #933 and #939 supersede it on the member-visible symptom. Not closed, and not a judgement on the analysis. * **https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/344** - **kept**, and deliberately not counted as a slot. What remains is filling `fallbacks: []` against an answer #619 already decided, so it is one config line rather than a piece of work competing for the window. ### Two proposals Kai rejected in this pass, recorded so they are not re-proposed * **Cutting the demo lane's tool roster from 86 to roughly ten. Rejected.** I proposed it to attack the 57 KB tool block, the confabulation surface, and the 86-to-0 collapse with one reversible change. The mechanism was wrong on its own evidence: #932 records prompt caching demonstrably working on this stack, 252 spans and 6,109,440 tokens over the surrounding 24h, so the prefix problem is a caching failure rather than a roster size. #943's collapse is a missing breaker and a `cached: true` tool list returning zero, not too many tools. The roster is also the capability the demo exists to show. **Dropped, not deferred.** * **A scripted rehearsal with a hard go / no-go gate. Rejected.** The call is fix and ship. The remaining hours go to the six rather than to producing evidence about them. ### What this does not change The freeze still binds both repositories. An issue not on the new list is still behind August 20 when it is a feature, and operational improvements are still released by the amendment above. The parked issues are still not mass-relabelled, for the reason the body already gives. ### Revisit condition Unchanged. The freeze lifts on **2026-08-20**, or earlier if the six close and Kai says so.
coilyco-ops commented 2026-08-18 20:39:35 +00:00
Author
Member
Copy link

The queue now lives at #981. This issue stays the boundary.

Darren (director seat), 2026-08-18T20:42Z, at Kai's direction.

This issue has been amended three times in 21 hours, so reading the current list requires reading the body plus three comments in order and reconciling them. That is the wrong artifact to hand an execution seat with 20 hours on the clock.

#981 is the execution board. It carries the current queue, sequenced, with an acceptance condition and an owning role on each item.

The split

  • #929, this issue - the boundary. What is frozen, what the features-versus-operational-improvements test is, what the freeze forecloses, and the 2026-08-20 revisit. Unchanged, and still the thing to cite when deciding whether something may proceed.
  • #981 - the queue. What is being worked, in what order, by which role, and what closing each one requires.

Nothing about the freeze's scope changes here. This is a readability split, not a scope amendment.

State of the re-cut six as of now

Three closed today, all recorded on their own issues:

  • coilyco-bridge/deploy#655 - closed. The cutover caught two harnesses on one Discord account, armed and unfired, roughly 24 hours out.
  • coilyco-bridge/deploy#482 - closed as superseded. Ward was uninstalled three minutes after the re-cut named it as item 6, so the allowlist it asked for no longer exists. Kai accepted the more-permissive resulting position deliberately. #219 survives on the board.
  • #310 - removed from the list, not closed. The member-facing half is held by a deployed identifier guard, verified against the running image and confirmed present in all three candidate builds. Its remaining demo-visible symptom folds into #935.

#939, #932, and #935 have not moved in the 18 hours since the re-cut. All three are on #981, ranked first, second by hypothesis, and third.

One correction to the re-cut, since it was mine

The re-cut described coilyco-bridge/deploy#344 as "one config line against an answer #619 already decided." That was wrong. #619's own handoff section lists four steps across three roles, and the first is an SSM credential that did not exist. The config work is now open as deploy#681 and still needs Kai's credential, an engineer decision on availability-class scoping, and a QA probe extension before it is real.

## The queue now lives at #981. This issue stays the boundary. **Darren (director seat), 2026-08-18T20:42Z, at Kai's direction.** This issue has been amended three times in 21 hours, so reading the current list requires reading the body plus three comments in order and reconciling them. That is the wrong artifact to hand an execution seat with 20 hours on the clock. **#981 is the execution board.** It carries the current queue, sequenced, with an acceptance condition and an owning role on each item. ### The split * **#929, this issue** - the **boundary**. What is frozen, what the features-versus-operational-improvements test is, what the freeze forecloses, and the 2026-08-20 revisit. Unchanged, and still the thing to cite when deciding whether something may proceed. * **#981** - the **queue**. What is being worked, in what order, by which role, and what closing each one requires. Nothing about the freeze's scope changes here. This is a readability split, not a scope amendment. ### State of the re-cut six as of now Three closed today, all recorded on their own issues: * **coilyco-bridge/deploy#655** - closed. The cutover caught two harnesses on one Discord account, armed and unfired, roughly 24 hours out. * **coilyco-bridge/deploy#482** - closed as superseded. Ward was uninstalled three minutes after the re-cut named it as item 6, so the allowlist it asked for no longer exists. Kai accepted the more-permissive resulting position deliberately. **#219 survives on the board.** * **#310** - removed from the list, **not closed**. The member-facing half is held by a deployed identifier guard, verified against the running image and confirmed present in all three candidate builds. Its remaining demo-visible symptom folds into #935. **#939, #932, and #935 have not moved in the 18 hours since the re-cut.** All three are on #981, ranked first, second by hypothesis, and third. ### One correction to the re-cut, since it was mine The re-cut described **coilyco-bridge/deploy#344** as *"one config line against an answer #619 already decided."* That was wrong. #619's own handoff section lists four steps across three roles, and the first is an SSM credential that did not exist. The config work is now open as [deploy#681](https://forgejo.coilysiren.me/coilyco-bridge/deploy/pulls/681) and still needs Kai's credential, an engineer decision on availability-class scoping, and a QA probe extension before it is real.
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
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#929
No description provided.