diff --git a/TASKS.md b/TASKS.md
index a71202b..7e6c23a 100644
--- a/TASKS.md
+++ b/TASKS.md
@@ -130,59 +130,91 @@ Acceptance Criteria:
 - Prompt limits scope to one small implementation step
 - Add/update tests
 
-## TASK-012 — Agent telemetry foundation
+## TASK-012 — Telemetry foundation
 
 Status: Todo
 
 Goal:
-Create a minimal telemetry writer for future agent activity tracking.
+Create a minimal telemetry system that can record structured agent activity for future guardrail and analysis features.
 
 Implementation Gap:
-There is currently no persistent session log for recording agent activity. Guardrails infer behaviour from markdown and RUN_LOG.md instead of structured telemetry.
+
+The project currently infers agent behaviour from documentation, task files, and run logs.
+
+There is no structured event log showing what actions an agent actually performed during a session.
 
 Acceptance Criteria:
 
-- Add a telemetry module
-- Create `.rdb/session-log.jsonl` when recording an event
-- Record JSONL events with:
+- Create a telemetry module
+- Create `.rdb/session-log.jsonl` automatically when recording an event
+- Support recording events in JSONL format
+- Each event contains:
   - timestamp
   - event_type
   - target
   - details
-- Add tests for writing and appending telemetry events
-- Do not integrate telemetry into every CLI command yet
+- Provide a simple public function for writing telemetry events
+- Add/update tests
 
-## TASK-013 — Log CLI command execution
+Example Event:
+
+```json
+{
+  "timestamp": "2026-06-02T12:00:00Z",
+  "event_type": "command",
+  "target": "rdb prompt",
+  "details": {}
+}
+```
+
+Constraints:
+
+- Do not integrate telemetry into existing commands yet
+- Do not modify guardrails yet
+- Do not implement dashboards or reporting
+- Build the smallest useful telemetry foundation only
+
+Definition of Done:
+
+- Telemetry writer exists
+- JSONL file is created correctly
+- Events append correctly
+- Tests pass
+- Documentation updated if required
+
+## TASK-013 — Record CLI command execution
 
 Status: Todo
 
 Goal:
-Record rdb CLI command execution into telemetry.
+Record rdb CLI command execution using the telemetry system.
 
 Implementation Gap:
-Telemetry writer exists, but CLI commands do not yet record command execution events.
+
+Telemetry storage exists but no command activity is recorded.
 
 Acceptance Criteria:
 
 - Record command execution events
 - Include command name
-- Include success/failure where practical
+- Include timestamp
 - Add/update tests
 
-## TASK-014 — Use telemetry in guardrails
+## TASK-014 — Integrate telemetry with guardrails
 
 Status: Todo
 
 Goal:
-Make `rdb guardrails` use structured telemetry when available.
+Use structured telemetry data in guardrail analysis.
 
 Implementation Gap:
-Guardrails currently rely on markdown and file mtimes rather than `.rdb/session-log.jsonl`.
+
+Guardrails currently rely on heuristics and markdown files rather than actual activity records.
 
 Acceptance Criteria:
 
-- Read telemetry events when present
-- Detect repeated reads from telemetry
-- Detect repeated commands from telemetry
-- Fall back gracefully if telemetry is missing
+- Read telemetry events
+- Detect repeated commands
+- Detect repeated reads when available
+- Fall back gracefully when telemetry is absent
 - Add/update tests