> ## Documentation Index
> Fetch the complete documentation index at: https://docs.merionlabs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ATIF and Harbor interoperability

> Exchange bounded trajectory evidence and audited evaluation tasks without replacing Merion's internal contracts.

# ATIF and Harbor interoperability

Merion can ingest observable external-harness evidence and export audited evaluation tasks without making either external format its internal source of truth.

## Import an ATIF trajectory

```bash theme={null}
merion interop atif-import ./trajectory.json \
  --workspace ./.merion \
  --id atif.my-run.1 \
  --json
```

Merion accepts exact ATIF v1.7 JSON, stores the raw file in the local content-addressed artifact store, and persists the normalized trajectory with payload provenance.

## Export an audited task to Harbor

```bash theme={null}
merion interop harbor-export task.my-eval \
  ./harbor-manifest.json \
  ./out/harbor-task \
  --workspace ./.merion
```

The task must have passed Merion's eight-check audit. The export creates a deterministic Harbor task bundle and requires a real environment and verifier from the manifest.

Exports are no-network by default, exclude every `solution/` path, and refuse to overwrite existing files.

## Import a Harbor result

```bash theme={null}
merion interop harbor-result-import ./result.json \
  --task-id task.my-eval \
  --expected-task-checksum checksum-from-harbor \
  --workspace ./.merion \
  --json
```

The checksum binds the result to the exact exported task. The imported record retains rewards, usage, timing, exception summaries, and source-payload provenance.

## Architectural boundary

ATIF is an evidence interchange format. Harbor is an executable task format. Merion retains its own governed `WorkEpisode`, `EvalTask`, verifier, environment, and `ExperimentSpec` contracts so an external tool cannot silently redefine the evidence or approval boundary.