Six spikes have never run: S3, S4, S5, S7, S8, S12 #48

New Issue

2026-09-05T16:20:22Z

dtourolle commented

2026-09-05 16:20:22 +00:00

Six spikes have never run, and several have acknowledgements in the code saying so.

S3, S4, S5, S7, S8 and S12 are each referenced only from the requirement text that asks for them. Two carry admissions in the source: dr-sync/src/upload.rs on S8, and dr-sync-nextcloud/src/lib.rs on S3.

The pattern worth stating

The spikes that ran are the ones whose subject was being built anyway. The ones that did not are the ones that would have said whether something should be built — which is the opposite of the order §9 asks for.

S1 and S14 have recorded results, and both were run alongside work that was happening regardless. S14's are the best evidence of any spike: a dedicated document, a measured pass over an 18,143-face library, a named device, a reproducible command. That is the standard.

Acceptance

For each of S3, S4, S5, S7, S8, S12: run it, or record a decision that it is not going to be run and what is being accepted instead.
Results recorded to S14's standard — named device, reproducible command, committed numbers.
The stale in-code acknowledgements updated once each is settled.

Filed as one

Six rows for six unrun spikes would say less than one row saying they share a cause. Split it if any single one is scheduled.

**Six spikes have never run, and several have acknowledgements in the code saying so.** S3, S4, S5, S7, S8 and S12 are each referenced only from the requirement text that asks for them. Two carry admissions in the source: `dr-sync/src/upload.rs` on S8, and `dr-sync-nextcloud/src/lib.rs` on S3. ## The pattern worth stating > The spikes that ran are the ones whose subject was being built anyway. The ones that did not are the ones that would have said whether something *should* be built — which is the opposite of the order §9 asks for. S1 and S14 have recorded results, and both were run alongside work that was happening regardless. S14's are the best evidence of any spike: a dedicated document, a measured pass over an 18,143-face library, a named device, a reproducible command. That is the standard. ## Acceptance - [ ] For each of S3, S4, S5, S7, S8, S12: run it, or record a decision that it is not going to be run and what is being accepted instead. - [ ] Results recorded to S14's standard — named device, reproducible command, committed numbers. - [ ] The stale in-code acknowledgements updated once each is settled. ## Filed as one Six rows for six unrun spikes would say less than one row saying they share a cause. Split it if any single one is scheduled. ## Related #23 (S6), #31 (S11), #38 (S13), #45 (S9), #47 (S2) are filed separately because each settles a specific requirement. See `docs/outstanding.md` §10.

dtourolle added the size:M spike labels 2026-09-05 16:20:22 +00:00

dtourolle commented

2026-09-05 16:20:57 +00:00

Filed as one because six rows would say less than one row saying they share a cause.
Separately filed: #23 (S6), #31 (S11), #38 (S13), #45 (S9), #47 (S2).

Filed as one because six rows would say less than one row saying they share a cause. Separately filed: #23 (S6), #31 (S11), #38 (S13), #45 (S9), #47 (S2).

dtourolle referenced this issue

2026-09-19 10:20:53 +00:00

FR-RAW-2 — A decoder trait, so that "without changing callers" is tested #57

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dtourolle/DarkRoom#48