Two handover items existed only in a machine-local board — and one of them was wrong - #413
Open
syncytium2 wants to merge 4 commits into
Open
Two handover items existed only in a machine-local board — and one of them was wrong#413syncytium2 wants to merge 4 commits into
syncytium2 wants to merge 4 commits into
Conversation
…cal board That session closed clean but recorded its open items on ../bugarach-worktrees/SESSIONS.md, which is machine-local and not in git. A session on another machine -- or this one after the board is reaped -- finds nothing. Two of the four had no durable home at all: the authorship correction existed only in cross-session messages and a reserved branch name that was never cut, and the rail item only in the conversation. THE AUTHORSHIP ONE IS THE VALUABLE ONE and it is a re-statement of the repo's own record, not a new claim. detector_history.md says rate+context, CoactDetect and LoCo are Tony's designs, SPIKE-synch is a detector written here on Kreuz's measure, binned SCE is not a port, and locust is the only port. README.md:7 and :79 say "lifts six ... out of MATLAB" and "Six detector ports"; CITATION.cff's abstract says "Python ports of six" and is the machine-readable one GitHub renders and citation managers quote verbatim. An outside reader already concluded this repo was a re-typing of someone else's MATLAB and published it. Both files record that the work is NOT authorized by their own existence -- Tony pulled that session up for scope, and an unclaimed path is not permission. Filed, not started. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
… independence claim goes Tony, 2026-08-30: "we built the first version of loco and coact detect in matlab together." That corrects the 2026-08-29 block, which says rate_detect, coact_detect and loco_detect "are his". interface2 agrees and the dates are checkable. SpikyDetect 1-3, the synchrony lineage, are 2026-04-23/27/28 with no co-author trailer. SpikyDetect4 -> RateDetect is 2026-05-13, CoactDetect and detect_loco are both 2026-07-14, and all three carry one. The first Claude-assisted commit in interface2 is 2026-05-06: the synchrony work predates it, everything rate- and coordination-shaped comes after. Commit dates are a lower bound and Tony notes years of poor hygiene, so earlier uncommitted work is not ruled out -- what the record does settle is which commits are co-authored. THE BIGGER CHANGE is withdrawing "I was totally unaware when I designed them", on which the 08-29 block rests its "convergence, not a derivation" reading. That is real evidence from a human and is NOT available from a model co-builder, which has no introspective access to whether its output derives from CFAR-shaped training data. Tony on the lit search: "i think it surpised both of us" -- genuine, and consistent with independent convergence AND with unrecognised reconstruction. Surprise cannot separate them. Withdrawn as unsupportable, not as false. Replaced by a timeline that needs nobody's memory: built 2026-04 to 2026-07, CFAR found 2026-08-22 (ff1db4d), recognised then. That rules out deliberate derivation, which is the only charge worth pre-empting, and stops short of claiming independence from a literature this project has not searched (§7 already says so). It costs nothing that was being defended. Tony closed priority on 08-24 -- "most researchers would be kind of thrilled with the link" -- so the independence claim was never load-bearing. §5's list, port fidelity to 1e-9, the Cossart root and the Kreuz position are all untouched. Flags that docs/todo/2026-08-30-the-repo-underclaims-its-own-authorship.md predates this and overstates in its title; it must be re-read against this before anyone acts. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ot one Filed an hour ago as "the repo underclaims its own authorship". Tony then said "we built the first version of loco and coact detect in matlab together", which makes the lineage doc wrong in the OTHER direction -- and this file's title was pushing whoever picked it up toward a stronger sentence than the evidence carries. Renamed and rewritten. Corrections: - "five of six were not lifted [out of MATLAB]" was FALSE. They were lifted, mostly out of Tony's own MATLAB. The defect at README.md:7 is omission -- it never says WHOSE -- not error. The word "port" does two jobs, MATLAB->Python and someone-else's-method->this-lab, and the README conflates them. One detector is the second kind. - Every origin row now carries the caveat that must travel with it: rate/coact/ loco were AI-assisted, SPIKE-synch is explicitly "not novel either" with Kreuz's own lab having published the same two-knob detector, binned SCE's root is Cossart 2003 from Yuste's lab. Those were in detector_history.md and not in this file, which is how a fix gets written stronger than its source. - Points at detector_history.md's 2026-08-30 revision as the authority and says to read it first. What survives unchanged: the README/CITATION.cff half. CITATION.cff is still the highest-leverage line -- machine-readable, rendered by GitHub's cite widget, quoted verbatim by citation managers with no next paragraph beside it. Still filed, still not started, still not authorization. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
syncytium2
changed the title
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
2 participants
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.
bugarach-63closed clean, but recorded its four open items on../bugarach-worktrees/SESSIONS.md— machine-local, not in git. Another machine sees nothing; so does this one once the board is reaped. Two of the four had no durable home at all.Includes #414 (the
detector_history.mdcorrection), because the authorship todo is unreadable without it.The authorship item, rewritten after Tony corrected the record
Filed first as "the repo underclaims its own authorship." That title was itself an over-claim. Tony then said "we built the first version of loco and coact detect in matlab together" — so the repo is wrong in both directions:
README.md:7/:79andCITATION.cff:15say six ports of other people's MATLAB. One is.What was wrong in the first draft
It said "five of six were not lifted out of MATLAB." False — they were lifted, mostly out of Tony's own. The word "port" does two jobs: MATLAB→Python (a code path, true of nearly all) and someone-else's-method→this-lab (an intellectual path, true of one). The README conflates them; the defect is omission — it never says whose MATLAB — not error.
And every caveat now travels with its row
These were in
detector_history.mdand not in the todo, which is how a fix gets written stronger than its source:rate/coact/loco— AI-assistedSPIKE-synch— "not novel either"; Kreuz's own lab published the same two-knob detectorbinned SCE— root is Cossart 2003, Yuste's lab, predating CICADAlocust— the one true portSo the correction is narrow: say who wrote the MATLAB originals. Not "these are novel" — for two of six the record says otherwise.
CITATION.cffremains the highest-leverage line: machine-readable, rendered in GitHub's Cite this repository widget, quoted verbatim by citation managers where no next paragraph sits beside it.Also here
The rail's remaining ~97px — filed because the last trim isn't a trim: it needs collapsing two grid rows, which changes what the diagram asserts. Not a continuation of #411, which was cosmetic by construction.
Not authorization
Tony pulled that session up for scope — "address this critique does not mean run wild." Both files say their own existence isn't a go-ahead. Filed, not started.
🤖 Generated with Claude Code