The progress cadence is three constants that have to agree, and nothing makes them #359

New issue

Closed

opened 2026-08-13 10:59:00 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-13 10:59:00 +00:00

Member

Slice of #354 — the "less numbers to move around" half, which is separable from harness-level thread creation and lands on its own.

The defect

Three constants encode one cadence, and their relationship exists only in whoever remembers it:

the wait before a progress line posts: 3s
the beat every later message releases on: 6s
the window Kai describes as 3 + 6 + 6: 15s

Only the first two are written down, and the third is not written down anywhere. Changing the wait silently breaks the other two, and nothing in the suite would notice, because each constant is individually correct.

Scope

Express the beat as twice the wait and the window as the wait plus two beats. No value changes — 3, 6, and 15 remain 3, 6, and 15. This is arithmetic that was already true, written down.

Acceptance

One edit to the wait moves all three.
Today's values are pinned, so a change to the base reports exactly what it moved.
The derivation itself is pinned, because a derivation that quietly stopped deriving would look identical at today's numbers.
The doc says which number is the real one.

Out of scope

Harness-level thread creation, which is the rest of 354 and needs the window this provides.

**Slice of** https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/354 — the *"less numbers to move around"* half, which is separable from harness-level thread creation and lands on its own. ## The defect Three constants encode one cadence, and their relationship exists only in whoever remembers it: - the wait before a progress line posts: 3s - the beat every later message releases on: 6s - the window Kai describes as `3 + 6 + 6`: 15s Only the first two are written down, and the third is not written down anywhere. Changing the wait silently breaks the other two, and nothing in the suite would notice, because each constant is individually correct. ## Scope Express the beat as twice the wait and the window as the wait plus two beats. **No value changes** — 3, 6, and 15 remain 3, 6, and 15. This is arithmetic that was already true, written down. ## Acceptance - One edit to the wait moves all three. - Today's values are pinned, so a change to the base reports exactly what it moved. - The derivation itself is pinned, because a derivation that quietly stopped deriving would look identical at today's numbers. - The doc says which number is the real one. ## Out of scope Harness-level thread creation, which is the rest of 354 and needs the window this provides.

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-13 10:59:18 +00:00

refactor(progress): one number instead of three that had to agree #358

coilyco-ops referenced this issue

2026-08-13 11:00:01 +00:00

encourage the agent to use threads #354

coilyco-ops closed this issue

2026-08-13 11:02:38 +00:00