akmon bundle export

Documented for Akmon 2.0.0.

Who this is for

Teams exporting a portable, verifiable session artifact for handoff, audit, or archive.

What you will have at the end

  • A .akmon bundle generated from one journal session.
  • Optional JSON metadata for automation.

Prerequisites

  • Source session UUID.
  • Access to source journal and write permission for output path.

Steps

akmon bundle export <session-id> [OPTIONS]

akmon bundle export <session-id> \
  [--output <path>] \
  [--journal <path>] \
  [--format <human|json>]
  1. Export with defaults:
akmon bundle export <session-id>
  1. Export to explicit path:
akmon bundle export <session-id> --output /path/to/audit.akmon
  1. Use JSON in CI:
akmon bundle export <session-id> --format json

Exit codes

CodeMeaning
0Bundle written successfully
1Reserved (not currently emitted)
2Usage error (for example, output path already exists)
3I/O or environment error (journal/session not found, missing object in store, write failure)

Verification

akmon bundle export <session-id> --format json | jq '.output_path'

Expected result: output path is returned and command exits 0.

Bundle format

An .akmon bundle is a tar.zst archive containing:

  • manifest.json
  • events.bin
  • objects/<hex>

Troubleshooting

  • If export fails with output-exists error, choose a new --output path.
  • If export fails with session/journal errors, verify UUID and --journal location.
  • Export does not replace integrity checks; run akmon verify before export when required.

See also