Article
stale · v4 open awaiting approvalWhat does the paper itself say, section by section?
for Spatially targeted inhibitory rhythms differentially affect neuronal integration · this layer across all papers · json
Awaiting approval
Waiting for approval. That is a statement about the record, not about whether anyone has read this: people read the corpus without stamping what they read, and only a stamp leaves a trace. Approval is an operation on a version, not a step of its own — it is recorded against the version it was granted to, so running this layer again does not carry it forward.
What it produced
Read from site/src/data/article/headley-2026-inhibitory-rhythms.json · 180 KB. slug headley-2026-inhibitory-rhythmsdoi 10.7554/eLife.95562articleId 95562source https://cdn.elifesciences.org/articles/95562/elife-95562-v1.xmltitle Spatially targeted inhibitory rhythms differentially affect neuronal integrationyear 2026
Nothing on this page renders document for this file yet — the link above is the artifact itself.
How it is defined
What this layer reads besides its dependencies. Each is a declared input: its content is hashed into every run, so editing one makes those runs stale.
What it says it does
The article, as the site renders it: JATS-XML into one JSON file per paper.
`prepare` already fetches the JATS and keeps four flattened strings from it — abstract,
results, captions, methods — which is everything the three readers need and nothing a page
needs. `results_text` is one string with the section headings glued to the sentences that
follow them, so a site that wants to show the paper cannot recover where the sections were.
This keeps the structure instead: the section tree, each paragraph with its inline markup,
the figures with their captions, the tables with their rows. It calls no model and reads the
same cached XML `prepare` fetched, so it is free to re-run and its output is byte-stable —
nothing here stamps a date, which is what stops a rebuild from marking every paper stale.
python3 scripts/article_json.py gadeke-2026-guilt-insula
python3 scripts/article_json.py --allArtifacts
Versions
From the run ledger. There is no changelog beside it to keep in step.
-
v4 · 2026-09-13 · scripts/pipeline.py run
ran via scripts/pipeline.py
python3 scripts/article_json.py headley-2026-inhibitory-rhythms
-
v3 · 2026-09-13 · scripts/pipeline.py run
ran via scripts/pipeline.py
python3 scripts/article_json.py headley-2026-inhibitory-rhythms
-
v2 · 2026-09-12 · scripts/pipeline.py run
re-run after prepare.py changed
python3 scripts/article_json.py headley-2026-inhibitory-rhythms
-
v1 · 2026-09-11 · scripts/pipeline.py run
first run: the article as a document
python3 scripts/article_json.py headley-2026-inhibitory-rhythms
This layer across the corpus
Across the corpus
10 stale·a paper links to its own cell, where this layer's output for it is rendered
Inputs and outputs
- Reads, besides its dependencies
-
- scripts/article_json.py · 307 lines
- Produces
-
- site/src/data/article/{paper}.json
One per paper — the table above links each one that exists.
- Views
-
- document — declared, and this artifact is not the shape this view needs
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> article
Underneath, that runs python3 scripts/article_json.py {paper}.