Structure reader

not run open awaiting approval

What is the paper's argument structure?

for Computational modelling identifies key determinants of subregion-specific dopamine dynamics in the striatum · 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.

Not run for this paper

What would fill it:

python3 scripts/pipeline.py run ejdrup-2026-dopamine structure-reader

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.

extract/prompts/structure-reader.mdthe prompt it runs undernot in the repository

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.

extract/prompts/contract/vocabulary.mdthe prompt it runs undernot in the repository

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.

extract/prompts/contract/schema-candidate.mdthe prompt it runs undernot in the repository

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.

Artifacts

  • runs/ejdrup-2026-dopamine/structure-reader.output.json · not produced
This layer across the corpus

Across the corpus

9 not run · 1 stale·a paper links to its own cell, where this layer's output for it is rendered

Inputs and outputs

Reads, besides its dependencies
Produces
  • runs/{paper}/structure-reader.output.json

One per paper — the table above links each one that exists.

Views
  • list — rendered above, over the 10 claims in the artifact
  • table — rendered above, over the 10 claims in the artifact
  • comparison — on the cell page, two versions aligned by the matcher, wherever the ledger holds more than one

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> structure-reader

Underneath, that runs cd extract && python3 -m claim_graphs.cli structure-reader --paper {paper}.