Locust is not CICADA, and four things this session got wrong on the way there - #367
Merged
Conversation
…ay there The session record, written before compaction. Straight into docs/handoffs/ rather than the root: nothing here is half-done, and the root HANDOFF.md belongs to the 2026-08-27 session and is still honest — its five PRs (#304, would destroy a live signal. The finding it exists for: locust's derivation chain is validated only at its last link. gen_ref_cicada.m builds the 1e-9 parity fixture by running interface2's own generate_sce_cicada, so nothing anywhere compares anything to the Cossart source; both repos assert "faithful port" and neither tests it. It is also a documented partial port — the per-cell transient-detection step is skipped — and interface2 PARKED that function in f55643bf for over-detecting on this preparation's long SLOW transients. Established so nobody re-derives it: the port came from their CODE, not the paper (sce_stats_utils.py exists at the cited path with both named functions, and the rasterdur parameter confirms the duration model it replaces); the citation is correct (Zenodo 10041434, v1.0.3, five authors, 20 July 2020, CC-BY-4.0), checked deliberately because the lit shelf holds DeepCINAC by the same five authors in the same year; and the duration diagnosis has been in interface2's methods doc since July with the mechanism and the number. It also carries four self-corrections and the pattern they share — a claim true of one context asserted about another — because the pattern is more useful to the next session than the fixes. The worst was a todo proposing a bench run at onset_field="peak", which would have moved the detector in the direction the project deliberately came from; retracted the same day. And the hazard worth the most: a worktree's pytest imports the PRIMARY checkout's src, because the venv holds one editable install. It fails toward green, and it had already put "1454 passed, 16 skipped" into two PR messages when the true figure was 1498 passed, 3 skipped, 1 xfailed. Review scope is stated in the file: a single-pass claim check against git, the files and the live page, not an eleven-role murderboard. Said plainly because a handoff claiming more review than it had is the defect this repo files incidents about. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
syncytium2
force-pushed
the
session-handoff-0828
branch
from
August 28, 2026 18:45
ac364de to
e0ab830
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Locust is not CICADA, and four things this session got wrong on the way there
The session record, written before compaction. Straight into docs/handoffs/
rather than the root: nothing here is half-done, and the root HANDOFF.md
belongs to the 2026-08-27 session and is still honest — its five PRs (#304,
#292, #270, #53, #50) were each verified OPEN at writing time. Replacing it
would destroy a live signal.
The finding it exists for: locust's derivation chain is validated only at its
last link. gen_ref_cicada.m builds the 1e-9 parity fixture by running
interface2's own generate_sce_cicada, so nothing anywhere compares anything to
the Cossart source; both repos assert "faithful port" and neither tests it. It
is also a documented partial port — the per-cell transient-detection step is
skipped — and interface2 PARKED that function in f55643bf for over-detecting on
this preparation's long SLOW transients.
Established so nobody re-derives it: the port came from their CODE, not the
paper (sce_stats_utils.py exists at the cited path with both named functions,
and the rasterdur parameter confirms the duration model it replaces); the
citation is correct (Zenodo 10041434, v1.0.3, five authors, 20 July 2020,
CC-BY-4.0), checked deliberately because the lit shelf holds DeepCINAC by the
same five authors in the same year; and the duration diagnosis has been in
interface2's methods doc since July with the mechanism and the number.
It also carries four self-corrections and the pattern they share — a claim true
of one context asserted about another — because the pattern is more useful to
the next session than the fixes. The worst was a todo proposing a bench run at
onset_field="peak", which would have moved the detector in the direction the
project deliberately came from; retracted the same day.
And the hazard worth the most: a worktree's pytest imports the PRIMARY
checkout's src, because the venv holds one editable install. It fails toward
green, and it had already put "1454 passed, 16 skipped" into two PR messages
when the true figure was 1498 passed, 3 skipped, 1 xfailed.
Review scope is stated in the file: a single-pass claim check against git, the
files and the live page, not an eleven-role murderboard. Said plainly because a
handoff claiming more review than it had is the defect this repo files
incidents about.
🤖 Generated with Claude Code