examples/skills/ov-add-paper/references/ara-compiler-profile.md
This profile adapts the Agent-Native Research Artifact compiler pattern for OpenViking ingestion. It keeps the ARA compiler's epistemic structure, but the final deliverable is an OV resource directory.
Source reference: https://github.com/AmberLJC/Agent-Native-Research-Artifact
PAPER.md
logic/
problem.md
claims.md
concepts.md
experiments.md
related_work.md
solution/
constraints.md
src/
environment.md
trace/
exploration_tree.yaml
evidence/
README.md
figures/
tables/
Additional files are allowed only when the paper warrants them, such as logic/solution/algorithm.md, logic/solution/architecture.md, data/dataset.md, src/configs/, or evidence/proofs/.
Build an evidence ledger before writing claims:
Figure N and Table N in the paper, in order.evidence/README.md with the reason.Figure Markdown should include:
quantitative_plot, diagram, qualitative_sample, or mixedexact_from_labels, digitized_estimate, or visual_descriptionTable Markdown should include:
logic/problem.md should capture observations, gaps, key insight, and assumptions.
logic/claims.md should use C01, C02, ... headings. Each claim needs:
E01logic/experiments.md should use E01, E02, ... headings. It describes verification plans, not exact result numbers. Exact numbers belong in evidence files.
logic/concepts.md should define paper-specific concepts. Do not pad with generic terms.
logic/related_work.md should describe typed dependencies such as imports, extends, baseline, bounds, or refutes.
logic/solution/constraints.md is always required and should state boundary conditions, assumptions, and limitations.
src/environment.md is always required. Other src/ files should capture concrete artifacts only when they exist in the paper or provided source material.
Do not manufacture code stubs from prose-only methods. If code is included, mark whether it is transcribed from source or reconstructed from explicitly printed pseudocode/equations.
trace/exploration_tree.yaml records the research DAG:
explicit or inferredDo not invent failures or decisions. If the paper hides the process, use a smaller trace and mark reconstructed nodes as inferred.
Before validation, do up to three coverage passes:
The ARA compile phase is complete only when:
PAPER.md has a useful layer indexscripts/validate_ara.py