Work Logging

Orbitmap records two types of work logs: task logs (within a task) and vibes (ad-hoc work outside tasks).

Task Logs

Every task accumulates a log of work entries. These are written by agents during task execution and serve as persistent memory for future sessions.

Log types:

Type	Purpose
`code_change`	What code was written or modified
`decision`	Why a particular approach was chosen
`note`	General observations, resume points
`blocker`	Something preventing progress

terminal

~/my-project

❯ HAL, log that we decided to use Redis
  for session caching instead of the
  database driver

HAL: Logging decision...
✓ log_work(task_id='TS-r2d2x1',
  type='decision',
  content='Chose Redis over DB session
  driver for caching - better performance
  under concurrent connections, and Laravel
  Cloud recommends it for production.')

Decision logged on TS-r2d2x1.

When an agent resumes a task, it reads all prior logs - so it immediately knows what was done, what was decided, and where work left off.

Vibes - Ad-hoc Work Logs

Vibes capture work that happens outside the structured task system: exploration, discovery, quick fixes, experiments.

terminal

~/my-project

❯ vibe log, stardate 2026.3: explored the
  Supabase Edge Functions as an alternative
  to Laravel queues for webhook processing.
  Promising but not mature enough yet.

DATA: Recording vibe...
✓ log_work(type='discovery',
  content='Explored Supabase Edge Functions
  for webhook processing. Promising
  alternative to Laravel queues but too
  immature - missing retry logic and DLQ.
  Revisit in Q3.')

Vibe recorded. Stardate 2026.3 logged.

Vibe use cases:

Discovery sessions ("tried X, learned Y")
Quick fixes not tied to any task
Exploration of new tools or libraries
Notes from debugging sessions