Edge review

stale · v1 provisional awaiting approval

What does a claim added after induction depend on and support?

for Feedback of peripheral saccade targets to early foveal cortex · 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.

Out of date

These inputs changed after this ran:

  • claims/kammer-2026-foveal-feedback/parametric-effects-not-global-fluctuations.md

What it produced0

Read from runs/kammer-2026-foveal-feedback/edge-review.output.json · 855 B. reviewed_on 2026-09-12model supplied:runs/kammer-2026-foveal-feedback/edge-review.answer.json

0

Nothing on this page renders table for this file yet — the link above is the artifact itself.

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/edge-inference.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.

scripts/edge_review.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

Versions

From the run ledger. There is no changelog beside it to keep in step.

  1. v1 · 2026-09-12 · supplied:runs/kammer-2026-foveal-feedback/edge-review.answer.json

    first run of the layer

    python3 scripts/edge_review.py kammer-2026-foveal-feedback --answer runs/kammer-2026-foveal-feedback/edge-review.answer.json

This layer across the corpus

Across the corpus

8 not run · 2 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}/edge-review.output.json
Views
  • table — rendered above, over the 6 edges 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> edge-review

Underneath, that runs python3 scripts/edge_review.py {paper} --answer runs/{paper}/edge-review.answer.json.