MIRA export
step · paper openDeclaration 311acc3f5348 has not been accepted by anyone. · no paper read under it
What does the schema eLife reads carry, and what does it drop?
Mechanical: re-runnable from its declared inputs.
Part of Interchange — What survives when a claim tree leaves this format?
How it works
Writes two files and a gap report. cg: namespace carrying the structure MIRA has no vocabulary for; the gap report says what the strict file dropped, and why.
The split is the design rather than a compromise in it. MIRA can express roughly half of what a claim tree holds, and a single converted file either loses the other half quietly or emits something a strict reader rejects.
What it found · added 2026-09-09
913 of 916 relations reach the export, with 0 validation violations attributable to the encoding. The gaps that remain are specific: 3 paper-level scope relations the schema has no node for, and 197 verification records for which no interchange format has a node type at all.
Rests on
- claim-tree · step
- stance · feature
- relation-vocab · question
Feeds — a change here disturbs these
- formats-report · step
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.
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 the schema requires, how each role and relation maps onto it, whether the exports validate and what we would ask the MIRA authors is in the MIRA reference. This page is the layer that produces the files.
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/export_mira.py · declared, and not in the repository — it hashes to nothing, so it cannot make a run stale
- Produces
-
- exports/{paper}.mira.jsonld
- exports/{paper}.mira-extended.jsonld
- exports/{paper}.gap-report.md
One per paper — the table above links each one that exists.
- Views
-
- graph — on the paper page, as the claim graph
- table — 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> mira-export
Underneath, that runs python3 scripts/export_mira.py {paper}.