Reconcile every harness doc and skill against the deployed state, and make capability drift a check rather than a discovery #1011

New issue

Open

opened 2026-08-19 01:47:13 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented 2026-08-19 01:47:13 +00:00

Member

Copy link

Filed after the fourth instance of the same defect in 24 hours. Each was found by accident, by a different reader, after the prose had already been wrong in production for hours. The pattern is worth fixing once rather than four more times.

The defect class

A capability moves in coilyco-bridge/deploy. Prose in this repository keeps describing the old one. Nothing notices, because nothing in CI compares a sentence to a deployed value.

It is worse than an ordinary stale doc, because most of this prose is inline: always, so a false capability claim is in the model's prompt on every single turn, and the model has no way to tell it from a true one.

The four instances

1. moxn-knowledge-base.md said "Four tools, all reads." coilyco-bridge/deploy#683 merged 2026-08-18T21:05Z and took the wrap to nine tools with readOnly: false, including delete under a bundled action argument. The doctrine told the lane it could not write for roughly four hours while it could write and destroy. Fixed in 3e177c3, along with the dowel-moxn-read-only boundary that would have graded the lane as failing for doing its job.
2. site-work.md named quire's verbs. quire was deleted; the file described set_page on a service that no longer existed. #977, fixed in a4c4d76.
3. capability.md states 6 tool rounds and 9 model calls. The Dowel definition sets tool_rounds: 12 and budget_raises: 2. #978, still open, and it is the one that will be wrong on camera if the lane is asked about its own limits.
4. The same number is now in four places. docs/sirens-echo-rate.md:31, docs/sirens-echo-tools.md:20, .agents/skills/coilyco-general/references/capability.md:31, and .agents/skills/sirens-echo-knowledge/references/capability.md:34 all hard-code six rounds independently. Four copies of one tunable that internal/community/config.go owns.

A fifth, of a different shape: two sources for one fact

#999 added standalone moxn and temporal skill roots so their own people can PR them, which is a good reason. But .agents/skills/moxn/SKILL.md now carries the product description, the name-collision rule, and the fetch-rather-than-recall rule, and .agents/skills/sirens-dowel/references/moxn-knowledge-base.md carries the same three things.

Only the second is in Dowel's local_skill_roots, so today they agree by coincidence and nothing makes them keep agreeing. The same split exists for temporal. Decide which is canonical and make the other point at it, rather than leaving two files that drift apart quietly.

Why the existing check did not catch any of this

just boundaries-check did catch instance 1, and it is the only thing that did. It failed on the missing anchor the moment the section was renamed, which is exactly what it is for.

Its reach is the limit. It verifies that a boundary's cited anchor still exists in a skill file. It cannot verify that the claim is true, and it only covers text a boundary happens to cite. Instances 2, 3, and 4 sit outside any boundary citation.

What would actually close it

Roughly in order of value per effort.

• Derive the numbers instead of restating them. ResolvedBudget already enumerates its fields for logging. The prompt could carry the lane's real ceilings, which ends instances 3 and 4 permanently and cannot drift again. This is the fix worth building.
• A drift check across the repository boundary. The authority for the tool surface is a values file in another repo. A check that reads sirens-dowel-moxn-mcp-values.yaml and fails when a skill file names a tool count or a read-only claim that disagrees would have caught instance 1 at the moment #683 merged. coilyco-bridge/deploy#693 is the same gap in the other direction and should be solved with it rather than separately.
• Ban the restated tunable. The estate rule already says tests must not re-encode configuration. The same argument applies to prose, and four independent copies of "6 tool rounds" is the proof.
• An inventory pass now, by hand, because none of the above lands before tomorrow. Every inline: always file, read against the deployed configmaps and values files, with each capability claim either verified or deleted.

Scope note

The inventory pass is the only part that should happen before the 2026-08-19 stream, and it is documentation-only, so it sits inside the freeze under the 2026-08-18 amendment on #929. The derivation work and the cross-repo check are after.

Related

• coilyco-bridge/deploy#683 - the widening that exposed this.
• #977, #978 - instances 2 and 3, #978 still open.
• coilyco-bridge/deploy#693 - the same class, catalogue direction.
• #971 and #1004 - the skill contract, which decides what inline: always means and therefore how much a wrong sentence costs.

**Filed after the fourth instance of the same defect in 24 hours.** Each was found by accident, by a different reader, after the prose had already been wrong in production for hours. The pattern is worth fixing once rather than four more times. ## The defect class A capability moves in `coilyco-bridge/deploy`. Prose in this repository keeps describing the old one. Nothing notices, because **nothing in CI compares a sentence to a deployed value.** It is worse than an ordinary stale doc, because most of this prose is `inline: always`, so a false capability claim is in the model's prompt on every single turn, and the model has no way to tell it from a true one. ## The four instances 1. **`moxn-knowledge-base.md` said "Four tools, all reads."** `coilyco-bridge/deploy#683` merged 2026-08-18T21:05Z and took the wrap to nine tools with `readOnly: false`, including delete under a bundled action argument. The doctrine told the lane it could not write for roughly four hours while it could write and destroy. Fixed in `3e177c3`, along with the `dowel-moxn-read-only` boundary that would have graded the lane as failing for doing its job. 2. **`site-work.md` named quire's verbs.** quire was deleted; the file described `set_page` on a service that no longer existed. #977, fixed in `a4c4d76`. 3. **`capability.md` states 6 tool rounds and 9 model calls.** The Dowel definition sets `tool_rounds: 12` and `budget_raises: 2`. #978, still open, and it is the one that will be wrong on camera if the lane is asked about its own limits. 4. **The same number is now in four places.** `docs/sirens-echo-rate.md:31`, `docs/sirens-echo-tools.md:20`, `.agents/skills/coilyco-general/references/capability.md:31`, and `.agents/skills/sirens-echo-knowledge/references/capability.md:34` all hard-code six rounds independently. Four copies of one tunable that `internal/community/config.go` owns. ## A fifth, of a different shape: two sources for one fact `#999` added standalone `moxn` and `temporal` skill roots so their own people can PR them, which is a good reason. But `.agents/skills/moxn/SKILL.md` now carries the product description, the name-collision rule, and the fetch-rather-than-recall rule, and `.agents/skills/sirens-dowel/references/moxn-knowledge-base.md` carries the same three things. Only the second is in Dowel's `local_skill_roots`, so today they agree by coincidence and nothing makes them keep agreeing. The same split exists for `temporal`. **Decide which is canonical and make the other point at it**, rather than leaving two files that drift apart quietly. ## Why the existing check did not catch any of this `just boundaries-check` **did** catch instance 1, and it is the only thing that did. It failed on the missing anchor the moment the section was renamed, which is exactly what it is for. Its reach is the limit. It verifies that a boundary's cited anchor still exists in a skill file. It cannot verify that the **claim** is true, and it only covers text a boundary happens to cite. Instances 2, 3, and 4 sit outside any boundary citation. ## What would actually close it Roughly in order of value per effort. * **Derive the numbers instead of restating them.** `ResolvedBudget` already enumerates its fields for logging. The prompt could carry the lane's real ceilings, which ends instances 3 and 4 permanently and cannot drift again. This is the fix worth building. * **A drift check across the repository boundary.** The authority for the tool surface is a values file in another repo. A check that reads `sirens-dowel-moxn-mcp-values.yaml` and fails when a skill file names a tool count or a read-only claim that disagrees would have caught instance 1 at the moment #683 merged. `coilyco-bridge/deploy#693` is the same gap in the other direction and should be solved with it rather than separately. * **Ban the restated tunable.** The estate rule already says tests must not re-encode configuration. The same argument applies to prose, and four independent copies of "6 tool rounds" is the proof. * **An inventory pass now**, by hand, because none of the above lands before tomorrow. Every `inline: always` file, read against the deployed configmaps and values files, with each capability claim either verified or deleted. ## Scope note The inventory pass is the only part that should happen before the 2026-08-19 stream, and it is documentation-only, so it sits inside the freeze under the 2026-08-18 amendment on #929. The derivation work and the cross-repo check are after. ## Related * `coilyco-bridge/deploy#683` - the widening that exposed this. * #977, #978 - instances 2 and 3, #978 still open. * `coilyco-bridge/deploy#693` - the same class, catalogue direction. * #971 and #1004 - the skill contract, which decides what `inline: always` means and therefore how much a wrong sentence costs.

coilyco-ops referenced this issue 2026-08-19 01:52:11 +00:00

The runtime image ships the eval material into the agent's working directory, so the agent's cwd contains its own test answers #1012

coilyco-ops referenced this issue 2026-08-19 01:52:35 +00:00

Follow-up docs pass after the stream: reconcile docs/ against what shipped, once main stops moving #1013

coilyco-ops added the

autonomy

epic

priority

P2

role/engineer

labels 2026-08-19 03:38:49 +00:00

coilyco-ops referenced this issue 2026-08-19 04:14:45 +00:00

capability.md hard-codes 6 tool rounds and 9 model calls, so the Dowel lane will misstate its own limits on camera #978

coilyco-ops referenced this issue from a commit 2026-08-19 04:24:43 +00:00

fix(skills): stop capability.md naming a round budget it does not own

coilyco-ops referenced this issue 2026-08-19 04:31:02 +00:00

Doctrine written for one surface leaks to every request, because inline prose carries no scope #1049

coilyco-ops referenced this issue from a commit 2026-08-19 04:41:12 +00:00

feat(skills): restore the member-location rule that #764 dropped

coilyco-ops referenced this issue 2026-08-19 04:42:18 +00:00

Evaluate if skills based progressive disclosure is actually working #968

coilyco-ops referenced this issue from a commit 2026-08-19 04:46:20 +00:00

feat(skills): describe the harness gates the model cannot see

coilyco-ops referenced this issue 2026-08-19 04:48:00 +00:00

Member physical-location disclosure has no rule since irl-physical was removed #766

coilyco-ops referenced this issue 2026-08-19 04:48:31 +00:00

Skill: inform the agent of its own classifier #908

coilyco-ops referenced this issue from a commit 2026-08-19 05:05:45 +00:00

fix(skills): realign the Dowel root with the roster it actually has

coilyco-ops referenced this issue 2026-08-19 05:06:06 +00:00

Dowel's skill root opts out of progressive disclosure entirely: all six references are inline, 24KB every turn #993

coilyco-ops referenced this issue 2026-08-19 16:19:12 +00:00

capability.md hard-codes 6 tool rounds and 9 model calls, so the Dowel lane will misstate its own limits on camera #978

coilyco-ops referenced this issue 2026-08-19 16:19:26 +00:00

capability.md tells both Deep lanes they have six tool rounds while deploy gives them twelve #953

coilyco-ops commented 2026-08-19 16:19:54 +00:00

Author

Member

Copy link

A fifth instance for the list, and it is the interesting kind: currently correct

Found while picking up #953 and #978 (both already fixed by 1f6e246, now closed). This one is not wrong today, which is exactly why it belongs here rather than in its own issue.

.agents/skills/sirens-echo-knowledge/references/capability.md, lines 34 to 36, inline: always, still reads verbatim:

At most 6 tool rounds. After the last one, the answer uses what they returned. A budget of 9 model calls also covers repairs and raises, so a request can run out of steps sooner.

1f6e246 removed those integers from coilyco-general's copy and did not touch this second copy.

Mapping roots to budgets across the three deployed definitions:

• sirens-echo - loads sirens-echo-knowledge - no model_budget, so it takes the defaults 6 and 9. Correct.
• sirens-deep - loads coilyco-general - tool_rounds: 12 - correct since 1f6e246
• sirens-dowel - loads coilyco-general - tool_rounds: 12 - correct since 1f6e246

So there is nothing to ship, and I did not edit it. Changing prose that currently matches its lane, during a freeze, to guard a hypothetical is the wrong trade.

Why it is still a data point for this issue

The four instances you catalogued were all discovered wrong. This one is correct by coincidence: the file hard-codes a per-deployment value and happens to name the default that the one lane reading it happens to take. Nothing holds that together. The day someone gives Echo a model_budget, this file is wrong in production on every turn with no test to notice, and it will present as a fifth accidental discovery.

That is worth something to the check this issue proposes. A check that only compares deployed values to prose would pass on this file today, so passing does not mean the coupling is sound. The stronger check is structural: an inline: always doc should not contain a literal that a definition can set, whether or not it currently agrees. That form catches this file now rather than after Echo's config moves.

Timely rather than theoretical: Echo's config is being actively changed today, with coilyco-bridge/deploy PR #734 enabling coalescing on that lane.

Two candidate shapes, both post-freeze:

1. Ban the literal. A test asserting no inline: always reference states an integer that Definition or ModelBudget can override. Cheap, no rendering cost, catches the latent case.
2. Shape 1 from #978 - render resolved ceilings at prompt build. Strictly better and more expensive, and it makes both copies of this paragraph unnecessary rather than merely checked.

Not proposing which. Flagging that the second capability.md exists at all is probably its own finding: two inline: always files describing the same bounds is the duplication that let one get fixed and the other not.

## A fifth instance for the list, and it is the interesting kind: currently correct Found while picking up #953 and #978 (both already fixed by `1f6e246`, now closed). This one is not wrong today, which is exactly why it belongs here rather than in its own issue. **`.agents/skills/sirens-echo-knowledge/references/capability.md`, lines 34 to 36**, `inline: always`, still reads verbatim: > At most 6 tool rounds. After the last one, the answer uses what they returned. A budget of 9 model calls also covers repairs and raises, so a request can run out of steps sooner. `1f6e246` removed those integers from `coilyco-general`'s copy and did not touch this second copy. Mapping roots to budgets across the three deployed definitions: * `sirens-echo` - loads `sirens-echo-knowledge` - **no `model_budget`**, so it takes the defaults 6 and 9. **Correct.** * `sirens-deep` - loads `coilyco-general` - `tool_rounds: 12` - correct since `1f6e246` * `sirens-dowel` - loads `coilyco-general` - `tool_rounds: 12` - correct since `1f6e246` So there is nothing to ship, and I did not edit it. Changing prose that currently matches its lane, during a freeze, to guard a hypothetical is the wrong trade. ## Why it is still a data point for this issue The four instances you catalogued were all **discovered wrong**. This one is **correct by coincidence**: the file hard-codes a per-deployment value and happens to name the default that the one lane reading it happens to take. Nothing holds that together. The day someone gives Echo a `model_budget`, this file is wrong in production on every turn with no test to notice, and it will present as a fifth accidental discovery. That is worth something to the check this issue proposes. **A check that only compares deployed values to prose would pass on this file today**, so passing does not mean the coupling is sound. The stronger check is structural: an `inline: always` doc should not contain a literal that a definition can set, whether or not it currently agrees. That form catches this file now rather than after Echo's config moves. Timely rather than theoretical: Echo's config is being actively changed today, with `coilyco-bridge/deploy` PR #734 enabling coalescing on that lane. Two candidate shapes, both post-freeze: 1. **Ban the literal.** A test asserting no `inline: always` reference states an integer that `Definition` or `ModelBudget` can override. Cheap, no rendering cost, catches the latent case. 2. **Shape 1 from #978** - render resolved ceilings at prompt build. Strictly better and more expensive, and it makes both copies of this paragraph unnecessary rather than merely checked. Not proposing which. Flagging that the second `capability.md` exists at all is probably its own finding: two `inline: always` files describing the same bounds is the duplication that let one get fixed and the other not.

coilyco-ops referenced this issue from a commit 2026-08-22 22:20:34 +00:00

fix(image): ship the lane definitions, not the eval material

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

Subscribe

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

No description provided.