iiRecord
Agentic AI Atlas · run-journal-event:effect-resolved
run-journal-event:effect-resolveda5c.ai
II.
RunJournalEvent JSON

run-journal-event:effect-resolved

Structured · live

run-journal-event:effect-resolved json

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

File · catalog-meta/run-journal-events/effect-resolved.yamlCluster · catalog-meta
Record JSON
{
  "id": "run-journal-event:effect-resolved",
  "_kind": "RunJournalEvent",
  "_file": "catalog-meta/run-journal-events/effect-resolved.yaml",
  "_cluster": "catalog-meta",
  "attributes": {
    "eventName": "EFFECT_RESOLVED",
    "category": "effect-lifecycle",
    "terminal": false,
    "description": "Emitted when an effect's StoredTaskResult is committed to the run\ndirectory. The journal payload references the result by effectId\nand carries the status (`ok` | `error` | `cancelled`), startedAt /\nfinishedAt, optional resultRef / stdoutRef / stderrRef, and any\nerror metadata. Replay engines use EFFECT_RESOLVED records to\nshort-circuit redundant effect work.\n"
  },
  "outgoingEdges": [
    {
      "from": "run-journal-event:effect-resolved",
      "to": "journal-event:babysitter-effect-resolved",
      "kind": "aliases_journal_event"
    }
  ],
  "incomingEdges": []
}