RAGit
Commands

timeline

Read the append-only collaboration event ledger for session, memory, harness, and ingest workflows

What It Does

timeline reads the append-only event ledger under .ragit/log/events/*.jsonl and projects the operational time axis for session materialization, artifact review, memory workflows, harness workflows, ingest completion, and security admission events. It intentionally does not summarize snapshot semantic state; that is log's job.

When To Use / When Not To Use

When to use it

  • You want to know what happened across collaboration workflows, not just what changed in snapshot history.
  • You want to trace a specific goalId, episodeId, or sessionId.
  • You want a compact operational audit trail before resuming work.

When not to use it

  • You want commit-ordered semantic snapshot deltas. Use log.
  • You want the current repository summary only. Use status.
  • You want direct retrieval hits for a question. Use query.

Syntax

pnpm ragit timeline [--goal <goalId>] [--episode <episodeId>] \
  [--session <sessionId>] [--kind <kind>] \
  [--since <iso>] [--until <iso>] [--max-count <n>] \
  [--view minimal|default|full] \
  [--format text|json|both] [--cwd <path>]

Arguments And Options

  • --goal <goalId>: Filter to one goal identifier.
  • --episode <episodeId>: Filter to one episode identifier.
  • --session <sessionId>: Filter to one source session identifier.
  • --kind <kind>: Limit results to session, artifact, memory, harness, ingest, or security.
  • --since <iso>: Lower bound for recordedAt.
  • --until <iso>: Upper bound for recordedAt.
  • -n, --max-count <n>: Limit the final number of emitted events.
  • --view minimal|default|full: Choose one-line scan output, structured event blocks, or richer provenance detail.
  • --format text|json|both: Choose human text, JSON, or both.
  • --cwd <path>: Run against another repository.

Input And Output Contract

  • There is no JSON payload input for timeline.
  • JSON output includes filters, summary, events, and redactionSummary.
  • Each event record includes eventId, eventType, recordedAt, goalId, episodeId, sessionId, sourceHeadSha, summary, artifactIds, relatedPaths, openLoops, nextActions, and provenance.
  • Event summaries and next actions are re-masked before output.

Examples

Scan the latest memory workflow events:

pnpm ragit timeline --kind memory --max-count 10

Inspect one session in JSON:

pnpm ragit timeline --session 20260410T090000Z-a1b2c3d4 --format json

Failures And Cautions

  • timeline is an event ledger reader, not a repair tool.
  • Dry-run commands do not write ledger events.
  • The ledger is append-only and operational. It complements log; it does not replace snapshot history.
  • If you need artifact-backed beliefs, open loops, and evidence for a commit, use log instead of timeline.