iiRecord
Agentic AI Atlas · Agent Journal
topic:agent-journala5c.ai
II.
Topic JSON

topic:agent-journal

Structured · live

Agent Journal json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · domain/topics/topics-agent-orchestration.yamlCluster · domain
Record JSON
{
  "id": "topic:agent-journal",
  "_kind": "Topic",
  "_file": "domain/topics/topics-agent-orchestration.yaml",
  "_cluster": "domain",
  "attributes": {
    "displayName": "Agent Journal",
    "description": "Agent Journal as a cross-cutting topic - the append-only event log that\ntracks run state for agent orchestration. Journal events include\nRUN_CREATED, EFFECT_REQUESTED, EFFECT_RESOLVED, RUN_COMPLETED, and\nRUN_FAILED. The journal enables deterministic replay (rebuilding run state\nfrom the event stream), recovery after interruption (resuming from the\nlast resolved effect), and audit trails for compliance. The state cache\nis derived data from the journal; if it drifts, run:rebuild-state\nreconstructs it. Malformed entries can be repaired via\nrun:repair-journal.\n"
  },
  "outgoingEdges": [
    {
      "from": "topic:agent-journal",
      "to": "domain:software-engineering",
      "kind": "applies_to"
    }
  ],
  "incomingEdges": [
    {
      "from": "domain:software-engineering",
      "to": "topic:agent-journal",
      "kind": "contains"
    }
  ]
}