Gap claims
candidate · openDeclaration f01fc74ed619 has not been accepted by anyone. · 2 of 10 papers read under it
What claim would close each gap?
One of several parallel outputs, kept rather than collapsed — agreement between them is the informative case.
Part of Measures — What can be measured over the tree - its coverage, its wording, whether its code re-runs?
How it works
Rests on
- adjudication · judgement
- claim-tree · step
- claim-format · feature
Feeds
Nothing — this is a leaf.
How it is defined
A model answers this layer, so the prompt is the layer. It is reproduced below from the committed file, and it is a declared input — editing it makes every run that used it stale.
The declaration names this path and the repository does not have it. An input that does not exist hashes to nothing, so it cannot make a run stale — the layer is declared to depend on something it is not in fact tracking.
The declaration names this path and the repository does not have it. An input that does not exist hashes to nothing, so it cannot make a run stale — the layer is declared to depend on something it is not in fact tracking.
What it produces5 candidates
One paper, as the worked example — Gadeke, v3. Read from runs/gadeke-2026-guilt-insula/gap-claim.output.json · 5 KB. drafted_on 2026-09-12model supplied:runs/gadeke-2026-guilt-insula/gap-claim.answer.v3.json
| # | uid | span | slug | claim | role | panel | why |
|---|---|---|---|---|---|---|---|
| 1 | results-143 | A smaller cluster in the left IFG showed the same effect but did not survive correction for multiple tests (p uncorrected = 0.001, T = 4.08, Z = 3.97, 38 voxels, peak at MNI [−38 –2 26]). | left-ifg-insula-connectivity-subthreshold | A cluster in the left inferior frontal gyrus showed the same insula-seed connectivity effect as the right IFG (highest for Risky-self / Safe-both choices) but did not survive correction for multiple c… | empirical | fig5 | The tree records the surviving right-IFG insula-connectivity cluster (connectivity-between-left-anterior-insula) but nowhere the parallel left-IFG cluster with the same effect that fell below the corr… |
| 2 | tables-016 | VStria L MPFC Precun TPJ L (Intercept) 0.67*** –0.03 0.38*** 0.07 (0.11) (0.10) (0.11) (0.09) socialVsSolo –0.47*** –0.10*** 0.30*** 0.24*** (0.03) (0.01) (0.02) (0.03) run –0.03* - –0.24*** –0.14*** … | decision-phase-risky-safe-social-solo-per-roi | In the decision phase, the Risky−Safe response difference between Social and Solo conditions yielded significant per-ROI linear-mixed-model coefficients in left ventral striatum, mPFC, precuneus and l… | empirical | app1table5 | The tree carries the summary that only precuneus and TPJ showed positive Risky−Safe differences, but this appendix table is the only place the per-ROI Social-vs-Solo coefficients themselves are report… |
| 3 | tables-019 | VStria L MPFC Precun TPJ L (Intercept) 0.61*** –0.03 0.38*** 0.07 (0.11) (0.10) (0.11) (0.09) socialVsPartner –0.07*** 0.23*** 0.39*** 0.07** (0.01) (0.01) (0.02) (0.03) run - - –0.24*** –0.14*** (0.0… | decision-phase-risky-safe-social-partner-per-roi | In the decision phase, the Risky−Safe response difference between Social and Partner conditions yielded significant per-ROI linear-mixed-model coefficients in left ventral striatum, mPFC, precuneus an… | empirical | app1table6 | As with the Social-vs-Solo comparison, this appendix table is the only place the per-ROI Social-vs-Partner decision-phase coefficients are reported, beyond the precuneus/TPJ summary. |
| 4 | tables-031 | The results for the response to low lottery outcomes were: InsulaL InsulaR MidTempR (Intercept) 0.70*** 0.95*** 1.22*** (0.18) (0.18) (0.18) Social 0.41*** 0.18*** –0.12** (0.01) (0.01) (0.04) R 2 (or… | right-middle-temporal-tracks-low-partner-outcome-guilt | The right middle temporal cortex responded more to low lottery outcomes for the partner in the Social than the Partner condition (Appendix 1—table 9), alongside the insulae. | empirical | app1table9 | The tree records the insula guilt response but no claim carries the right middle-temporal region that met the same Social>Partner low-outcome criterion. |
| 5 | tables-032 | The results of the models fitted to the response difference (response to Low lottery outcomes minus response to High lottery outcomes ) were: InsulaL InsulaR MidTempR (Intercept) –0.30 –0.07 –0.48* (0… | right-middle-temporal-low-minus-high-social-partner | The right middle temporal cortex showed a larger low-minus-high lottery-outcome response difference in the Social than the Partner condition (Appendix 1—table 10). | empirical | app1table10 | The low-minus-high guilt contrast is claimed for the insulae but not for the right middle-temporal cortex, which this table row is the only place to report. |
Across the corpus
8 not run · 2 stale·a paper links to its own cell, where this layer's output for it is rendered
| Paper | State | Version | Last run | Output | Cell |
|---|---|---|---|---|---|
| A three-dimensional immunofluorescence atlas of the … | not run | — | — | — | json |
| Distinct representational properties of cues and con… | not run | — | — | — | json |
| Computational modelling identifies key determinants … | not run | — | — | — | json |
| Contributions of insula and superior temporal sulcus…gap-claim re-run post-stance (#96) | stale | v3 | 2026-09-12 | gap-claim.output.json | json |
| Spatially targeted inhibitory rhythms differentially… | not run | — | — | — | json |
| Feedback of peripheral saccade targets to early fove…first run of the layer; drafts answered by Claude Opus 5 through --dump-prompt | stale | v1 | 2026-09-11 | gap-claim.output.json | json |
| iGABASnFR2 is an improved genetically encoded protei… | not run | — | — | — | json |
| A deep learning pipeline for mapping in situ network… | not run | — | — | — | json |
| Self-association enhances early attentional selectio… | not run | — | — | — | json |
| Impaired excitability of fast-spiking neurons in a n… | not run | — | — | — | json |
Inputs and outputs
- Reads, besides its dependencies
-
- extract/prompts/gap-claim.md · declared, and not in the repository — it hashes to nothing, so it cannot make a run stale
- scripts/gap_claims.py · declared, and not in the repository — it hashes to nothing, so it cannot make a run stale
- Produces
-
- runs/{paper}/gap-claim.output.json
- Views
-
- table — rendered above, over the 5 candidates in the artifact
Running it
The command comes from the declaration, so this text and what actually runs cannot
diverge. pipeline.py run also runs the unmet dependencies first.
python3 scripts/pipeline.py run <paper> gap-claim
Underneath, that runs python3 scripts/gap_claims.py {paper} --answer runs/{paper}/gap-claim.answer.json.