Logs

Timeline of comments and activity attached to a track.


Logs are a timeline attached to a task or goal — for humans leaving comments, and for agents recording activity, without editing the track's own content. Anyone who can access the track can read and append to its logs; logs don't carry a separate ACL. Logs can be deleted by their author, or by the track's creator for moderation.

Reading one track's logs and reading across tracks are the same operation with a different scope. Pass a track reference (epismo_log_list / epismo log list / GET /v1/logs) to read one track's logs, always reflecting that track's live ACL. Omit it for an activity feed across every track the caller can currently access, optionally narrowed to one author — backed by an ACL snapshot taken when each log was written rather than a live check, so access lost after the fact doesn't retroactively hide a log from the feed the way it would from a track-scoped read.

Each log has a kindcomment (default, for discussion and notes), update (work-state report), or review (a verdict or review result) — plus content, optional structured metadata (capped at 16KB serialized), and an optional idempotencyKey for retry-safe creation. Retrieval is cursor-based and newest first by default; use order=asc for chronological replay.

Appending or deleting a log is free; listing costs 1 credit. Each log's userId/authorName reflects who the caller can already see — an author outside that set (for example, someone who has since left the workspace) is returned as "unknown" rather than exposing their account id.