Skip to main content
plog export produces self-contained .plog files that anyone can verify offline — no database or server access needed.

​
Creating an export

# Export all events for an agent
plog export --agent-id my-agent

# Export a time range
plog export --agent-id my-agent \
  --since 2026-02-01T00:00:00Z \
  --until 2026-02-17T00:00:00Z

​
Verifying an export

plog verify-export package.plog
Verification checks:
  1. Hash chain integrity — every event’s hash is correct and links are contiguous
  2. Merkle inclusion — each event is proven to belong to the original Merkle tree

​
Export package format

The .plog file is a self-contained JSON document: 
{
  "version": "1.0",
  "exported_at": "2026-02-17T12:00:00Z",
  "filter": {
    "agent_id": "my-agent",
    "since": "2026-02-01T00:00:00Z",
    "until": "2026-02-17T00:00:00Z"
  },
  "merkle_root": "abc123...",
  "tree_size": 500,
  "events": [
    { "id": "...", "agent_id": "my-agent", "hash": "...", "..." : "..." }
  ],
  "merkle_proofs": [
    {
      "event_id": "evt-123",
      "proof": {
        "leaf_hash": "...",
        "leaf_index": 42,
        "siblings": ["...", "..."],
        "tree_size": 500
      }
    }
  ]
}

​
Use cases

  • Auditor delivery — auditors receive files, not system access
  • Regulatory compliance — portable proof of agent behavior
  • Incident investigation — share a specific time range of events
  • Cross-organization trust — verify without shared infrastructure