# U7-2 timing-metric route packet This page does not change the current public six-question batch. It records one narrow row just outside that batch, so readers can see why `U7-2` is the cleanest adjacent packet after `U7-1`, why `D11` stays the strongest public-open anchor for this row, and what the first release-block timing artifact can honestly close. ## What was rechecked for this row - `D11 A multi-session simultaneous EEG-fMRI dataset with online experience sampling` still remains the strongest public-open first anchor for `U7-2`, because it exposes simultaneous multimodal runs, session structure, and BIDS-side provenance that make `offset`, `jitter`, and `reanalysis agreement` auditable inside one disclosed protocol family. - `D01 Acquisition delay of wireless EEG` still remains the cleanest device-delay support family once this row needs a separate floor for hardware-side acquisition latency rather than only event-log alignment. - `CastillosCVEP40 (MOABB)` remains a useful but secondary timing-stress family when the row needs an additional event-locked waveform check for peak-latency drift, but it still stays `check-needed` rather than a first public anchor. - The current public six-question batch still stays unchanged: `U13-2 / U13-5 / U0-2 / U0-3 / U14-4 / U14-2`. - The next-watch headline queue also stays unchanged: `U7-1 / U1-2 / U4-2 / U8-1`. This row is an adjacent support packet inside the same synchronization family, not a batch switch. - The practical funding bridge for this row still stays watch-first rather than current-public-six: `Okawa Foundation research grant` remains the cleanest fit, and existing Todoist watch tasks already cover that lane. ## Why `U7-2` is worth packetizing now - It is an `A` row: the main claim can stay inside `EEG-DATA` without needing theory, law, or identity overreading. - It is metric-first: the first artifact is not a broader multimodal standard claim but a release-block rule that maps `offset/jitter` into explicit pass/fail timing numbers. - It naturally follows `U7-1`. `U7-1` fixes what fields must exist; `U7-2` fixes which synchronization errors become operationally unacceptable once those fields exist. - It helps `U0` and `U14` without widening them. Identity-drift timing floors and rerun contracts both become easier to read when timing error already has a named metric bundle and a downgrade rule. ## Why `D11` stays the main public-open anchor | Candidate | What it helps with | Why it is not the first public anchor | |---|---|---| | `D11 A multi-session simultaneous EEG-fMRI dataset with online experience sampling` (`10.18112/openneuro.ds007216.v1.0.0`, immediate) | It gives `47 sessions`, `186 EEG runs`, simultaneous EEG-fMRI, run-level timing structure, and BIDS-side provenance, which makes it the strongest public-open route for mapping `offset median`, `jitter p95`, `peak-latency drift`, and `reanalysis agreement` inside one disclosed family. | None in this run. It is the strongest public-open first anchor for `U7-2`. | | `D01 Acquisition delay of wireless EEG` (`10.21227/dv1p-vq18`, immediate DOI route) | It is the clearest nearby support family once the row needs a separate hardware-side delay floor that is not reducible to BIDS logs alone. | It is a device-delay floor rather than the first multimodal reanalysis family, so it stays support rather than primary. | | `CastillosCVEP40 (MOABB)` (`check-needed`) | It is a useful event-locked stress family when the row needs an explicit waveform-side `peak-latency drift` check. | It is still catalog-style and check-needed on the present public route, so it stays secondary rather than primary. | ## What the first artifact can honestly close now | Artifact piece | What it closes now | What still stays outside the claim | |---|---|---| | `Timing-metric specification note` | A bounded rule that fixes the public metric bundle as `offset median`, `jitter p95`, `peak-latency drift`, and `reanalysis agreement` rather than leaving synchronization quality implicit. | Any statement that one metric bundle already establishes a field-wide synchronization standard. | | `Release-block threshold note` | A public-safe rule that keeps the row at warning-only whenever corrected event-alignment error `p95 > 15 ms` or `reanalysis agreement < 0.90` remains. | Any claim that one threshold generalizes across devices, loop classes, and all ERP families. | | `Device-versus-pipeline separation note` | A narrow distinction between acquisition-delay failure, event-log failure, and downstream pipeline failure so the route does not overread one error source as the whole explanation. | Any claim that one successful audit already resolves broader multimodal validity, identity continuity, or deployment readiness. | ## Funding wording that still fits | Route | Submission wording that stays honest | Why it still fits this row | |---|---|---| | `Okawa Foundation research grant` (`watch`) | `Metric-based synchronization audit and release-block thresholds for multimodal EEG reproducibility in the mind-upload route` | The row reads naturally as an information / standards / reproducibility package rather than a stronger neuroscience claim. | | `Kura Fund` (`secondary only`) | `A young-researcher timing-metric package for synchronization error control in public EEG verification` | It fits only as a bounded young-researcher infrastructure package, not as a batch switch or a stronger mind-upload claim. | ## External dependency tasks that stay outside this session - Cross-device truth for absolute latency still needs broader hardware validation beyond the present dataset family. - Wider community adoption of any release-block threshold still remains outside the present repository-level artifact. - Any interpretation that one timing metric bundle already resolves multimodal common-state, identity, or deployment questions remains outside the present route. ## What changed in this run - The public batch did not change. - The main change is that `U7-2` now has a public packet that records the strongest public-open anchor, the first metric bundle, and the watch-level funding bridge without widening the current public six or the next-watch headline queue. - This remains a route-setting update, not a solved-claim update.