Verification check

not run provisional awaiting approval

Does a re-run stand behind each claim, read beside its warrant?

for Spatially targeted inhibitory rhythms differentially affect neuronal integration · this layer across all papers · json

Provisional

This layer needs a corpus-scope decision that has not been ruled on yet, so what it produces would change if the decision changed. It waits on claim-format, relation-vocab.

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 headley-2026-inhibitory-rhythms verification-check

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.

extract/claim_graphs/verification_check.pythe script that runs itnot 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/headley-2026-inhibitory-rhythms/verification-check.output.json · not produced
This layer across the corpus

Across the corpus

8 not run · 1 stale · 1 blocked upstream·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}/verification-check.output.json

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

Views
  • table — rendered above, over the 25 checks 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> verification-check

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