fix: the sirens-echo limits are rate limits, not spend limits #127

Merged

coilysiren merged 1 commit from fix/sirens-echo-rate-limits into main

2026-08-25 07:55:02 +00:00

coilyco-ops commented

2026-08-25 07:44:36 +00:00

Collaborator

The Open Source block claimed sirens-echo enforces "per-user and global spend limits". It does not. That is a factual overstatement on a career surface, and I introduced it.

What is actually true

From coilyco-gaming/sirens-echo docs/sirens-echo-admission.md:

SIRENS_ECHO_RATE_USER - 3/30s - one Discord account or identified HTTP caller
SIRENS_ECHO_RATE_CONTEXT - 10/10s - one guild or direct-message channel
SIRENS_ECHO_RATE_GLOBAL - 20/5s - the whole process
SIRENS_ECHO_EXECUTION_SLOTS - 8 - concurrent turns, with MAX_PENDING at 16 behind it

Requests per window and concurrency. Not cost. Neither "spend" nor "cost" appears anywhere in that repository's docs/FEATURES.md, and the only uses of "budget" there are a history budget and a send budget, neither of which is money.

Why it matters

"Spend limits" implies cost control over model inference, which is a different and more impressive claim than rate limiting. It reads as a specific engineering achievement that is not there.

How it got in

The phrase came from the work order in coilysiren/inbox#402, which specified the per-bullet claims. That same brief instructed the writing seat to anchor descriptions on published banner text and explicitly not to re-describe a repository from its README. The framing instruction was correct. It did not cover the underlying facts, and I wrote the claim through without checking it.

Found while pulling the four repositories for coilysiren/inbox#422, where Kai flagged that sirens-echo's README bullets were half wrong. They are, and one of them had already reached the resume.

The fix

Reworded to name all three tiers, which is both accurate and a stronger claim than the two-tier version it replaces.

static/resume.pdf regenerated from the same source, as every prior resume change has done.

Checks

just build-resume clean, PDF still two pages
No other claim in that bullet changed

Kai reviews and merges. Not merging this myself.

The Open Source block claimed sirens-echo enforces "per-user and global spend limits". It does not. That is a factual overstatement on a career surface, and I introduced it. ## What is actually true From `coilyco-gaming/sirens-echo` `docs/sirens-echo-admission.md`: - `SIRENS_ECHO_RATE_USER` - `3/30s` - one Discord account or identified HTTP caller - `SIRENS_ECHO_RATE_CONTEXT` - `10/10s` - one guild or direct-message channel - `SIRENS_ECHO_RATE_GLOBAL` - `20/5s` - the whole process - `SIRENS_ECHO_EXECUTION_SLOTS` - `8` - concurrent turns, with `MAX_PENDING` at 16 behind it Requests per window and concurrency. Not cost. Neither "spend" nor "cost" appears anywhere in that repository's `docs/FEATURES.md`, and the only uses of "budget" there are a history budget and a send budget, neither of which is money. ## Why it matters "Spend limits" implies cost control over model inference, which is a different and more impressive claim than rate limiting. It reads as a specific engineering achievement that is not there. ## How it got in The phrase came from the work order in `coilysiren/inbox#402`, which specified the per-bullet claims. That same brief instructed the writing seat to anchor descriptions on published banner text and explicitly not to re-describe a repository from its README. The framing instruction was correct. It did not cover the underlying facts, and I wrote the claim through without checking it. Found while pulling the four repositories for `coilysiren/inbox#422`, where Kai flagged that sirens-echo's README bullets were half wrong. They are, and one of them had already reached the resume. ## The fix Reworded to name all three tiers, which is both accurate and a stronger claim than the two-tier version it replaces. `static/resume.pdf` regenerated from the same source, as every prior resume change has done. ## Checks - `just build-resume` clean, PDF still two pages - No other claim in that bullet changed Kai reviews and merges. Not merging this myself.

coilyco-ops added 1 commit

2026-08-25 07:44:36 +00:00

fix: the sirens-echo limits are rate limits, not spend limits

Test and mirror to GitHub / test (pull_request) Successful in 2m35s

Details

Test and mirror to GitHub / test-e2e (pull_request) Successful in 2m10s

Details

Test and mirror to GitHub / mirror (pull_request) Has been skipped

Details

101486b26d

The Open Source bullet claimed "per-user and global spend limits". Checked
against docs/sirens-echo-admission.md: the mechanism is SIRENS_ECHO_RATE_USER
at 3/30s, SIRENS_ECHO_RATE_CONTEXT at 10/10s, SIRENS_ECHO_RATE_GLOBAL at
20/5s, and eight concurrent execution slots with a bounded queue. Requests per
window and concurrency, not cost.

Neither "spend" nor "cost" appears anywhere in the repository's FEATURES.md.
The claim came from the work-order brief in coilysiren/inbox#402 and I wrote it
through without checking it against the repository, which the same brief had
told me not to read. The framing instruction was right and did not cover the
facts.

Reworded to name all three tiers, which is the accurate and stronger claim.

Ref: coilysiren/inbox#422

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: devrel

coilyco-ops referenced this pull request from a commit

2026-08-25 07:51:57 +00:00

docs: correct the README behavior list and lead with the summon boundary