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

feat(startup): report which optional capabilities are configured #544

Closed
coilyco-ops wants to merge 1 commit from eng/say-what-is-switched-on into main
pull from: eng/say-what-is-switched-on
merge into: coilyco-gaming:main
Conversation 0 Commits 1 Files changed 4 +203
coilyco-ops commented 2026-08-13 15:33:57 +00:00
Member
Copy link

Three capabilities were found built and inert today — the content gate (#227), job-store durability (deploy #464), and the Echo scratchpad (#287). Each took a read of this repository and the deploy repository to establish, and each was found by accident while looking at something else.

The cause is a good property with a blind spot. Absence is deliberately inert: an unset variable offers no tools rather than tools that fail. The cost is that a capability nobody switched on is indistinguishable, from inside the process, from one that was never built — and nothing reported the difference. main.go logs only failures; discord.ready logs identity and build revision. No line said what the process can do.

What this adds

One structured log at boot: startup.capabilities, with a name and a boolean for each optional surface — Discord ingress, MCP roster, access policy, content classes, job-store durability, scratchpad, issue tracker.

It fires first in Run, before the job runner starts and before the gateway opens, so a process that dies during startup has already said what it was configured to be. That is the case where the answer is most wanted and currently least available.

Metadata only, and asserted

A name and a boolean. No path, endpoint, or configured value reaches it, so the telemetry contract needs no exception. TestTheReportCarriesNoConfiguredValue asserts that, because "report what is configured" is exactly the shape that invites someone to log the value next.

TestBlankConfigurationIsNotConfigured covers the case a values file produces by accident — a variable set to whitespace must not read as switched on.

The set is closed

TestEveryOptionalSurfaceIsReported counts the report against the optional fields, and TestTheOptionalFieldListMatchesTheConfigStruct reads config.go to check the list and the loader agree. Adding an optional surface and forgetting the report fails the suite rather than shipping a capability nobody can see.

Verified by mutation: dropping content_classes from the report turns the count test red, and restoring it turns it green.

What it does not do

Turns nothing on, changes no behaviour. Whether each of the three should be configured is a deployment decision and for two of them it is Kai's. This only makes the state legible.

closes #539

Three capabilities were found built and inert today — the content gate (#227), job-store durability (deploy #464), and the Echo scratchpad (#287). Each took a read of this repository *and* the deploy repository to establish, and each was found by accident while looking at something else. The cause is a good property with a blind spot. Absence is deliberately inert: an unset variable offers no tools rather than tools that fail. The cost is that **a capability nobody switched on is indistinguishable, from inside the process, from one that was never built** — and nothing reported the difference. `main.go` logs only failures; `discord.ready` logs identity and build revision. No line said what the process can do. ## What this adds One structured log at boot: `startup.capabilities`, with a name and a boolean for each optional surface — Discord ingress, MCP roster, access policy, content classes, job-store durability, scratchpad, issue tracker. It fires **first in `Run`**, before the job runner starts and before the gateway opens, so a process that dies during startup has already said what it was configured to be. That is the case where the answer is most wanted and currently least available. ## Metadata only, and asserted A name and a boolean. No path, endpoint, or configured value reaches it, so the telemetry contract needs no exception. `TestTheReportCarriesNoConfiguredValue` asserts that, because "report what is configured" is exactly the shape that invites someone to log the value next. `TestBlankConfigurationIsNotConfigured` covers the case a values file produces by accident — a variable set to whitespace must not read as switched on. ## The set is closed `TestEveryOptionalSurfaceIsReported` counts the report against the optional fields, and `TestTheOptionalFieldListMatchesTheConfigStruct` reads `config.go` to check the list and the loader agree. Adding an optional surface and forgetting the report fails the suite rather than shipping a capability nobody can see. Verified by mutation: dropping `content_classes` from the report turns the count test red, and restoring it turns it green. ## What it does not do Turns nothing on, changes no behaviour. Whether each of the three should be configured is a deployment decision and for two of them it is Kai's. This only makes the state legible. closes #539
feat(startup): report which optional capabilities are configured
All checks were successful
ci / image-build (pull_request) Successful in 23s
Details
ci / test (pull_request) Successful in 34s
Details
ci / publish-echo-image (pull_request) Has been skipped
Details
ci / publish-observed (pull_request) Has been skipped
Details
e997f15d01 
Three capabilities were found built and inert today, each by reading this
repository and then deploy to see whether a variable was set: the content
gate, job-store durability, and the Echo scratchpad. Nothing anywhere
said so, because absence is deliberately inert and inert looks exactly
like never-built from inside the process.

startup.capabilities names each optional surface and whether it is
configured. A name and a boolean, so no path or endpoint reaches a log
and the telemetry contract is unchanged.

It fires first in Run, before the job runner and the gateway, so a
process that dies starting up has already said what it was meant to be.

The set is closed by test: a capability added later and left out of the
report fails the suite.

closes #539

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
coilyco-ops 2026-08-13 15:33:58 +00:00
  • closed this pull request
  • requested review from coilysiren
All checks were successful
ci / image-build (pull_request) Successful in 23s
Details
ci / test (pull_request) Successful in 34s
Details
ci / publish-echo-image (pull_request) Has been skipped
Details
ci / publish-observed (pull_request) Has been skipped
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
coilysiren
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!544
No description provided.