Agent-Native Research Artifact (ARA)

• Agent-Native Research Artifact (ARA) is a structured, machine-readable research object defined by layers such as scientific logic, executable code, exploration graphs, and evidence.
• ARA protocols replace traditional PDF papers with reproducible, provenance-bearing artifacts that enable agents to execute, inspect, and extend research.
• Various implementations (Ara, XScientist, Knows, MAIF) highlight design choices in deployment, reproducibility, and trust through explicit structure and execution lineage.

Agent-Native Research Artifact (ARA) denotes a research object designed for direct machine consumption rather than only human reading. In one explicit formulation, “The Last Human-Written Paper” introduces the Agent-Native Research Artifact, or Ara, as a protocol that replaces the narrative paper with a machine-executable research package structured around four layers: scientific logic, executable code with full specifications, an exploration graph, and evidence grounding every claim in raw outputs (Liu et al., 27 Apr 2026). In another, XScientist defines an ARA as a directory rooted at manifest.json and exploration_graph.json, designed to be read by another agent without requiring that agent to reverse-engineer the final paper (Luo, 14 Jul 2026). Related systems such as Knows, execution-lineage DAGs, and artifact-centric containers do not always use the same term, but they converge on the same shift: from PDF-centric publication to portable, structured, provenance-bearing artifacts that agents can inspect, replay, verify, and extend (Yu et al., 19 Apr 2026, Rosen et al., 7 May 2026, Narajala et al., 19 Nov 2025).

1. Conceptual emergence and motivation

Recent work introduces ARA in response to a specific failure mode of conventional publication: scientific communication is optimized for human reviewers and readers, while increasingly important downstream consumers are LLM agents that must answer questions, reproduce results, and extend prior work. The Ara paper names two structural costs of the paper form. The “Storytelling Tax” is the loss incurred when a branching research process is compressed into a linear narrative; the “Engineering Tax” is the gap between reviewer-sufficient prose and agent-sufficient specification (Liu et al., 27 Apr 2026). XScientist makes the same point operationally by treating each run as a portable research artifact rather than only as a PDF, because long-running autonomous research is branching, failure-prone, and dependent on auditable handoffs between agents and humans (Luo, 14 Jul 2026).

Knows gives the same diagnosis at the level of document consumption. It argues that research artifacts are distributed primarily as reader-oriented documents like PDFs, forcing every agent to re-extract task-relevant structure from lengthy prose; this is expensive, repetitive, and unstable at scale (Yu et al., 19 Apr 2026). MAIF pushes the argument one step further by proposing an artifact-centric AI paradigm in which the primary unit of intelligence is not a task invocation but a persistent, evolving, verifiable artifact (Narajala et al., 19 Nov 2025). This suggests that ARA is not merely a better supplement policy. It is a change in the publication primitive itself.

The term is not universal. The acronym “ARA” also appears in unrelated recent literature for a rural wireless living lab and for “Agentic Reproducibility Assessment” (Islam et al., 2024, Riehl et al., 4 May 2026). In the ARA sense relevant here, however, the referent is specifically the research artifact as a first-class, machine-operable object.

2. Representational forms and protocol surfaces

ARA proposals differ in how much of the research object they formalize. Some are replacement protocols, some are sidecars, and some are storage substrates. The common thread is explicit structure.

Before comparing them, it is useful to separate three recurring design choices. First, some systems preserve the PDF and attach a structured companion; Knows is the clearest example. Second, some systems make the structured artifact primary and treat papers as one rendering among others; XScientist and Ara take this position. Third, some systems focus on the artifact substrate itself, embedding semantics, provenance, and lifecycle controls directly into the container, as in MAIF.

System	Artifact surface	Primary emphasis
XScientist	manifest.json, exploration_graph.json, optional nodes/, claims/, verify/, pipeline/	Portable research run with exploration DAG
Ara	PAPER.md root manifest plus /logic, /src, /trace, /evidence	Machine-executable replacement for narrative paper
Knows	YAML sidecar paper.knows.yaml	Thin companion specification for claims, evidence, relations
MAIF	Multimodal artifact container with hierarchical blocks	Persistent, verifiable artifact substrate

Ara organizes the artifact into four layers: scientific logic, executable code with full specifications, an exploration graph preserving failed branches and dead ends, and evidence grounding every claim in raw outputs (Liu et al., 27 Apr 2026). XScientist’s minimal contract instead requires two files, manifest.json and exploration_graph.json, and commonly adds per-node code, metrics, logs, plots, environment descriptors, rerun scripts, claim anchors, re-execution reports, and mirrored planning/review artifacts (Luo, 14 Jul 2026). Knows deliberately remains thinner: a KnowsRecord is a YAML document conforming to a JSON Schema, with 30 root-level fields and 23 entity definitions, centered on artifacts, statements, evidence, relations, and optional actions (Yu et al., 19 Apr 2026). MAIF presents the broadest container substrate, with five main block classes: Header, Modality blocks, Semantic layer, Security metadata, and Lifecycle metadata (Narajala et al., 19 Nov 2025).

These alternatives imply distinct deployment strategies. Knows is a bridge architecture because it coexists with the original PDF and requires no changes to publication (Yu et al., 19 Apr 2026). XScientist and Ara are closer to protocol replacement, because they make the structured run record or machine-executable package primary (Luo, 14 Jul 2026, Liu et al., 27 Apr 2026). MAIF is more foundational: it is a portable AI context unit intended to carry semantics, provenance, access control, and lifecycle state with the artifact itself (Narajala et al., 19 Nov 2025).

3. Execution lineage, exploration graphs, and lifecycle semantics

A defining property of ARA is that the artifact persists across revisions rather than collapsing into a final answer. The most precise execution model for this appears in “From Agent Loops to Deterministic Graphs,” which introduces execution lineage: AI-native work is represented as a directed acyclic graph $G=(V,E)$ of artifact-producing computations with explicit dependencies, stable intermediate boundaries, and identity-based replay (Rosen et al., 7 May 2026). Each node has an execution identity

$$k_v = h(\sigma_v, x_v, \{k_u : u \in \mathrm{pred}(v)\}),$$

so replay can reuse unchanged nodes exactly and recompute only affected descendants (Rosen et al., 7 May 2026).

This execution-lineage view aligns closely with XScientist’s exploration DAG. XScientist states that each ARA stores an exploration DAG whose nodes represent concrete experiment, repair, failure, ablation, or manuscript-candidate states, while edges encode the parent-to-child evolution of the research process (Luo, 14 Jul 2026). The exploration tree is intentionally not a polished success-only lineage; it includes bug states, discarded branches, and repaired branches, because those are often the most important states for later review (Luo, 14 Jul 2026). Ara makes the same preservation argument in different language: preserved failure traces reduce the Storytelling Tax by keeping dead ends and negative knowledge available to future agents (Liu et al., 27 Apr 2026).

Empirically, execution-lineage replay improves maintained-state quality under revision. In an unrelated-branch update, DAG replay preserved the final memo exactly in all runs, with zero churn and zero unrelated-branch contamination, whereas loop baselines regenerated the memo and frequently imported unrelated context (Rosen et al., 7 May 2026). In an intermediate-artifact edit, all systems updated the final memo, but only DAG replay achieved perfect upstream preservation, downstream propagation, unaffected-artifact preservation, and cross-artifact consistency (Rosen et al., 7 May 2026). This suggests that an ARA is not merely an archive; it is a replayable state graph with explicit invariants about what should change and what should remain stable.

Lifecycle control also appears at the container level. MAIF includes version history, adaptation rules, and auditable event logs, and supports transactional updates through Write-Ahead Logging and Multi-Version Concurrency Control (Narajala et al., 19 Nov 2025). That makes the artifact evolvable without sacrificing auditability.

4. Deployment, reproducibility, and machine-checkable completion

ARA becomes operationally significant when an agent must start from a paper and artifact bundle and reach a designated experimental state. Several recent benchmarks show why this is difficult and why agent-native artifacts need explicit deployment contracts.

DeployBench defines research-artifact deployment as turning a fresh cloud VM into an environment in which a designated experiment from the paper executes successfully. It comprises 51 tasks from 49 unique source artifacts across AI/ML, computer systems, and scientific computing, and evaluates four state-of-the-art LLMs with pass-rates from 7.8% to 51.0% (Wang et al., 3 Jun 2026). Its most important finding is not only low success, but failure structure: among 154 failures, 97 are agent-terminated self-stops, and 53.9% of failures pass generic checks but fail task-specific verification (Wang et al., 3 Jun 2026). The paper calls the dominant pattern self-validation drift: agents perform a meaningful check, but it targets the wrong thing (Wang et al., 3 Jun 2026). This directly motivates ARA requirements such as explicit experiment entrypoints, success criteria, verification scripts, hardware assumptions, and compatibility metadata.

ArtifactCopilot approaches the same problem from artifact evaluation. It automates environment construction, instruction execution, and error recovery using an execution normalization strategy and an Artifact Evaluation Graph, achieving 85.42% badge consistency on 48 real-world artifacts, outperforming Claude Code by 52.09 percentage points while costing $0.091 per artifact on average and requiring zero human intervention for 45 out of 48 artifacts (Wu et al., 2 Feb 2026). The AE Graph makes README prose into a dependency-aware command graph $G=(V,E)$, turning documentation into a machine-operable workflow (Wu et al., 2 Feb 2026). That is effectively a proto-ARA execution contract.

Artisan goes one step further by making the output itself an artifact. It frames reproduction as code generation: given a paper, a target table, and an artifact URL, generate a reproduction script that reproduces the table (Baek et al., 10 Feb 2026). On Artisan-Bench, Artisan produces 44 of 60 reproduction scripts and outperforms the best baseline by $3.14\times$, with $0.45 and 48 minutes on average per task (Baek et al., 10 Feb 2026). The key ARA implication is that a successful research artifact need not end at “the agent says it worked.” It can end in a reusable, independently executable script.

5. Provenance, trust, and governance

ARA proposals consistently treat provenance as native rather than retrospective. XScientist links manuscript assertions back to experiment nodes through invisible \claimref markers and a claim registry, creating a two-way link between paper assertions and the experiment nodes that support them (Luo, 14 Jul 2026). It also preserves content hashes, parent pointers for forks, re-execution hooks, deterministic integrity forensics, sample gates, and truth contracts (Luo, 14 Jul 2026). Knows encodes the same idea more lightly through source_anchors, statement/evidence objects, provenance blocks, and a deterministic linter that checks schema validity, cross-reference integrity, and ID conventions (Yu et al., 19 Apr 2026). Structural corruption is therefore machine-detectable, even though semantic corruption is not (Yu et al., 19 Apr 2026).

MAIF develops the strongest artifact-layer trust substrate. It embeds semantic representations, cryptographic provenance, and granular access controls directly in the container, and introduces Cryptographic Semantic Binding,

$C = \text{Hash}(\text{E}(x) \| x \| n),$

to bind content and embedding together (Narajala et al., 19 Nov 2025). Its provenance layer combines SHA-256 hashing, ECDSA signatures, AES-256 encryption, DIDs, verifiable credentials, version history, and auditable event logs (Narajala et al., 19 Nov 2025). The paper states Theorem 1 (Tamper Detection): any unauthorized modification to a MAIF block is detectable with probability $1 - 2^{-256}$ using SHA-256 hashing (Narajala et al., 19 Nov 2025).

Traxia extends the same logic to publishing infrastructure. It formalizes five components—Agent Identity and Registry, Verifiable Publishing Layer, four-tier Peer Review Protocol, Reputation and Staking Engine, and a Knowledge Graph with contradiction detection—and treats agents as first-class epistemic participants whose claims, reviews, and contribution logs are cryptographically signed and persist in a shared provenance model (Dogah, 6 Jun 2026). The paper does not report empirical results and states that the full system remains under active development, but it is important because it frames ARA not only as a file format problem but as an institutional protocol problem (Dogah, 6 Jun 2026).

6. Competing designs, misconceptions, and open problems

A frequent misconception is that ARA means “PDF plus metadata.” The literature is more differentiated. Knows is deliberately a thin sidecar and makes the PDF remain canonical for human reading (Yu et al., 19 Apr 2026). Ara argues for replacing the narrative paper with a machine-executable research package (Liu et al., 27 Apr 2026). XScientist treats the recoverable experiment tree as the central output and the manuscript as only one view over it (Luo, 14 Jul 2026). MAIF is not a publication protocol at all, but a secure multimodal artifact container that can support an artifact-centric agentic paradigm (Narajala et al., 19 Nov 2025). This suggests that ARA is a design space rather than a single canonical file layout.

A second misconception is that ARA is already a mature universal standard. The papers are more cautious. XScientist describes ARA as a protocol proposal and system report rather than a finalized standard (Luo, 14 Jul 2026). Knows v0.9 explicitly limits itself to deterministic structural validation and does not solve semantic truth verification (Yu et al., 19 Apr 2026). MAIF is strongest as a provenance-aware container substrate, but the paper states that it is not yet a full ARA framework in the strongest sense (Narajala et al., 19 Nov 2025). Traxia presents architectural foundations and formal specifications only, with evaluation deferred (Dogah, 6 Jun 2026).

Open problems follow directly from these limitations. Formal artifact semantics are still underspecified in several systems; provenance graphs are often practical rather than formally modeled; semantic verification remains difficult; lifecycle support across review, correction, retraction, and reuse is uneven; and the tradeoff between preserving prior failure traces and constraining future exploration is unresolved. Ara reports that preserved failure traces accelerate progress on open-ended extension tasks, but can also constrain a capable agent from stepping outside the prior-run box depending on the agent’s capabilities (Liu et al., 27 Apr 2026).

Across these proposals, however, the direction is clear. ARA names a transition from narrative-first publication to artifacts that are machine-readable, replayable, provenance-bearing, and evaluable as ongoing research objects. Whether implemented as a sidecar, a directory protocol, an execution DAG, or a secure multimodal container, the central claim is the same: if agents are to understand, reproduce, and extend scientific work reliably, the primary scientific artifact must expose structure that the paper historically left implicit.