# U14-4 card-contract route packet This page does not change the current public six-question batch. It makes only the fifth active row more explicit, so readers can see why `U14-4` still stays before `U14-2`, why `D01 Acquisition delay of wireless EEG` now stays only as a gated support entry point, and what the next public-safe artifact can honestly close. ## What still stays fixed after the 14:10 JST actual-pull reread on April 4, 2026 - An actual-pull recheck at `2026-04-04 14:10 JST` after `mind-upload@cafeab4bc2a5`, `EEG-DATA@e0695bcac83d`, and `auto-research-funds@a4852d89376c` still keeps `U14-4` fifth and still keeps `D01` only as the planned gated-support disclosure floor for this row. - The newest pulled deltas remain carry-forward rather than route replacement. `mind-upload` tightens glossary excitability and ionic terms on top of the earlier EEG foundation-model source-status split without widening the route, `EEG-DATA` still reports `30,930` merged-unique rows, `28,893` high-confidence rows, `24,909` immediate rows, and `24,539` high-confidence immediate rows after the newest metadata deep dives, and `auto-research-funds` adds `JELA Diakonia` scholarship cards without changing the practical shortlist. - None of those additions replaces the present rerun-entry structure. The newest carry-forwards do not change the fact that `D01` still sets only the latency / measurement floor, `D13` still stays the first public-open rerun support family, and `D08` still stays the validation-heavy support family kept one step later. - Browser-level live checks in this run still returned `HTTP/2 200` for the current public entry pages and this row packet with `Last-Modified: Sat, 04 Apr 2026 04:18:04 GMT`; the checked front-door pages already surfaced `2026-04-04 12:02 JST` wording while this row packet still surfaced `2026-04-04 09:05 JST` wording before this source sync. A fresh read-only Todoist audit still showed the existing funding-task coverage as sufficient (`items=206`, `projects=2`, `Kura=2`, `Nakatani family=11`, `Kashinome=2`, `Secom=3`, `Brain Science Foundation=8`, `Okawa=2`, `Japan Industrial Science Research Institute=1`, `Doumei=0`, `Kenkyu no Susume=0`), so no new Todoist item was justified for this row in this sync. ## What still stays fixed after the 09:05 JST actual-pull reread on April 4, 2026 - An actual-pull recheck at `2026-04-04 09:05 JST` after `mind-upload@e571567f017d`, `EEG-DATA@fbbb0d8c01e0`, and `auto-research-funds@d7f6fb9bc158` still keeps `U14-4` fifth and still keeps `D01` only as the planned gated-support disclosure floor for this row. - The newest pulled deltas remain carry-forward rather than route replacement. `mind-upload` now just carries the earlier `08:07 JST` route-hold sync on top of a recent pretraining-overlap audit, `EEG-DATA` still reports `30,929` merged-unique rows, `28,892` high-confidence rows, `24,909` immediate rows, and `24,539` high-confidence immediate rows after the `OpenNeuro ds007020` deep dive, and `auto-research-funds` adds deeply reviewed April 4 scholarship updates without changing the practical shortlist. - None of those additions replaces the present rerun-entry structure. The newest carry-forwards do not change the fact that `D01` still sets only the latency / measurement floor, `D13` still stays the first public-open rerun support family, and `D08` still stays the validation-heavy support family kept one step later. - Browser-level live checks in this run still returned `HTTP/2 200` for the current public entry pages and this row packet with `Last-Modified: Sat, 04 Apr 2026 00:11:41 GMT`; the checked front-door pages already surfaced `2026-04-04 08:07 JST` wording while this row packet still surfaced `2026-04-04 01:04 JST` wording before this source sync. A fresh read-only Todoist audit still showed the existing funding-task coverage as sufficient (`items=206`, `projects=2`), so no new Todoist item was justified for this row in this sync. ## What still stays fixed after the 01:04 JST actual-pull reread on April 4, 2026 - An actual-pull recheck at `2026-04-04 01:04 JST` after `mind-upload@9b6a8b971ba0`, `EEG-DATA@56d765da60b`, and `auto-research-funds@3c8569e28` still keeps `U14-4` fifth and still keeps `D01` only as the planned gated-support disclosure floor for this row. - The newest pulled deltas remain carry-forward rather than route replacement. `mind-upload` now carries the earlier `00:06 JST` route reread plus field-level artifact-stack disclosure tightening, `EEG-DATA` still reports `30,921` merged-unique rows, `28,884` high-confidence rows, `24,900` immediate rows, and `24,530` high-confidence immediate rows after deepening `Numbers` and `PRIOS`, and `auto-research-funds` adds current coverage for `同盟育成会` and `研究のすゝめ奨学金` without changing the practical shortlist. - None of those additions replaces the present rerun-entry structure. The newest carry-forwards do not change the fact that `D01` still sets only the latency / measurement floor, `D13` still stays the first public-open rerun support family, and `D08` still stays the validation-heavy support family kept one step later. - Browser-level live checks in this run still returned `HTTP/2 200` for the current public entry pages and this row packet with `Last-Modified: Fri, 03 Apr 2026 21:11:06 GMT`; the checked row packet still surfaced `Updated: 2026-04-02` before this source sync even though the front-door pages already surfaced the `2026-04-04 01:04 JST` basis. A fresh read-only Todoist audit still showed the existing funding-task coverage as sufficient (`items=206`, `projects=2`, `Kura=2`, `Nakatani family=11`, `Nakatani graduate scholarship=7`, `Kashinome=2`, `Secom=3`, `Brain Science Foundation=8`, `Okawa=2`, `Japan Industrial Science Research Institute=1`, `Keio graduate scholarship=2`, `G-7=1`, `ENEOS=1`, `同盟会=0`, `研究のすゝめ=0`), so no new Todoist item was justified for this row in this sync. ## What still stays fixed after the 23:08 JST actual-pull reread on April 2, 2026 - An actual-pull recheck at `2026-04-02 23:08 JST` after `mind-upload@f5d1d1dd1683`, `EEG-DATA@ee1463d28288`, and `auto-research-funds@ec24a355abbc` still keeps `U14-4` fifth and still keeps `D01` only as the planned gated-support disclosure floor for this row. - The newest pulled deltas remain carry-forward rather than route replacement. `mind-upload` clarifies the causal-versus-human-proxy bridge outside the current six, `EEG-DATA` now reports `30,896` merged-unique rows, `28,859` high-confidence rows, and `24,882` directly usable rows after candidate-curation refinement plus the `OpenNeuro ds007615` deep dive, and `auto-research-funds` adds `Geo-Kagaku` current cards without changing the practical shortlist. - None of those additions replaces the present rerun-entry structure. The latest carry-forwards do not change the fact that `D01` still sets only the latency / measurement floor, `D13` still stays the first public-open rerun support family, and `D08` still stays the validation-heavy support family kept one step later. - Browser-level live checks still returned `HTTP/2 200` for the current public entry pages with `Last-Modified: Thu, 02 Apr 2026 13:12:21 GMT`, and a fresh read-only Todoist audit still showed the existing funding-task coverage as sufficient, so this page only refreshes the row-specific route-hold wording. ## What still stays fixed after the 12:04 JST actual-pull reread on April 2, 2026 - An actual-pull recheck at `2026-04-02 12:04 JST` after `mind-upload@dceb8bc`, `EEG-DATA@04b7fda167e`, and `auto-research-funds@4442e348a` still keeps `U14-4` fifth and still keeps `D01` only as the planned gated-support disclosure floor for this row. - The newest pulled deltas remain carry-forward rather than route replacement. `mind-upload` syncs a spectroscopy front door outside the current six, `EEG-DATA` now reports `30,888` merged-unique rows, `28,851` high-confidence rows, and `24,506` immediate rows after `THINGS-EEG`, an OSF orientation route, and a rat ECoG deep dive, and `auto-research-funds` only refreshes repository stats. - None of those additions replaces the present rerun-entry structure. The newest visual, auditory, and animal carry-forwards do not change the fact that `D01` still sets only the latency / measurement floor, `D13` still stays the first public-open rerun support family, and `D08` still stays the validation-heavy support family kept one step later. - Browser-level live checks still returned `200` for the current public entry pages with `Last-Modified: Thu, 02 Apr 2026 02:37:04 GMT`, and a fresh read-only Todoist audit still showed the existing funding-task coverage as sufficient, so this page only refreshes the row-specific route-hold wording. ## What was rechecked for this row - `D01 Acquisition delay of wireless EEG` still fixes the intended latency-first wireless EEG measurement route, but the current IEEE DataPort page is subscription-gated and its visible package is still a latency/synchronization dataset with `README_en` plus device/run `.mat` files rather than a rerun benchmark by itself. - The current funding bridge remains narrow and unchanged: `Kura Fund` stays first, `Nakatani Foundation research grant` stays next-cycle watch, and `Secom General Research Grant` stays an urgency-watch route only. - The public six-question batch also stays unchanged: `U13-2 / U13-5 / U0-2 / U0-3 / U14-4 / U14-2`. ## Why `U14-4` still stays fifth - It is the disclosure-first row that should turn abstract reproducibility language into concrete card fields before the route asks for an operational split contract in `U14-2`. - If this row fails, broader reproducibility wording should stay blocked because the route would still be missing a concrete disclosure floor. - The row can close a narrow documentation artifact with EEG alone before any stronger standards or deployment language is attempted. ## Why `D01` stays in scope only as a gated support anchor | Candidate | What it helps with | Why it is not the first public anchor | |---|---|---| | `D01 Acquisition delay of wireless EEG` (`10.21227/dv1p-vq18`, subscription-gated support) | It still fixes the intended latency-first measurement route, which is enough to keep the disclosure-first rerun question in scope if access is available. | The current IEEE DataPort page is subscription-gated, and the visible package is still a latency floor rather than a rerun benchmark, so it no longer counts as an immediate public anchor in this run. | | `D13 A New Benchmark Dataset Towards Ubiquitous P300 ERP-based BCI Applications` (`10.17632/vyczny2r4w`, immediate) | It is the first required public-open rerun family once the first card fields have been fixed on a narrower latency route. | It is better as a rerun support family than as the first bounded disclosure anchor, so it stays secondary. | | `D08 Simultaneous human intracerebral stimulation and HD-EEG, ground-truth for source localization methods` (`10.21227/7may-9q56`, immediate) | It gives a stronger measurement-grounding example that may later help leak-audit or validation-field design. | It is too validation-heavy and not as direct a disclosure-first entry point as the current latency route, so it stays support rather than primary for `U14-4`. | The public-open rerun family and the validation-heavy family should not be read as interchangeable. `D13` is the first rerun-example support family this row would need next, while `D08` is better kept for grounded validation-field examples after the first card contract is already fixed. ## What the first artifact can honestly close now | Artifact piece | What it closes now | What still stays outside the claim | |---|---|---| | `Filled Model Card / Dataset Card examples` | A bounded example set showing how latency, measurement, and rerun fields should be filled for the current public batch. | Any statement that card completeness alone proves field-wide reproducibility or deployment readiness. | | `Disclosure-first rerun checklist` | A narrow operational checklist that links card fields to a rerun contract instead of leaving them as passive metadata. | Any claim that the checklist already functions as a broadly adopted standard. | | `Latency-field mapping note` | A public-safe explanation of why latency and measurement provenance must appear as concrete contract fields. | Any theory-level conclusion that goes beyond the present EEG artifact. | ## First-pass KPI bundle and stop rule | Item | Current row-level fixation | |---|---| | `First-pass KPI bundle` | `required-card fill rate`, `rerun success rate`, `leak-audit coverage` | | `Stop rule` | Do not widen this row if fuller cards do not improve rerun traceability or if leak-audit fields remain missing in negative-case examples. | ## Funding wording that still fits | Route | Submission wording that stays honest | Why it still fits this row | |---|---|---| | `Kura Fund` | `A disclosure-first reproducibility contract package for a bounded EEG verification route toward the mind-upload hypothesis` | The row still reads as a young-researcher disclosure package rather than a solved reproducibility claim. | | `Nakatani Foundation research grant` (`next-cycle watch`) | `Card-integrated rerun documentation for a bounded EEG verification route` | The row remains plausible only as a later-cycle reproducibility package once the current closed cycle reopens. | | `Secom General Research Grant` (`next-cycle watch only`) | `Latency-aware disclosure and rerun-contract audit for EEG verification artifacts` | The March 31, 2026 `12:00 JST` deadline has already passed in this run, so the route remains useful only as a carried-forward watch note rather than a live planning lane. | ## External dependency tasks that stay outside this session - `D13`-backed rerun examples are still needed before the row can support broader reproducibility wording. - Leak-audit exemplars are still needed before the route can move from disclosure discipline to stronger standards language. - Any field-wide reproducibility, standards-adoption, or deployment-readiness interpretation remains outside the present EEG-only route. ## What changed in this run - The public batch did not change. - The main change in this sync is that `U14-4` now carries the same `2026-04-04 09:05 JST` route basis as the latest front-door reading and records that the live row packet had still been stuck at the earlier `2026-04-04 01:04 JST` wording before this source update. - The row still records the anchor-choice rationale, one compact first-pass KPI bundle, and one explicit stop rule instead of leaving them implicit. - This is still a route-setting update, not a solved-claim update.