Fleet/Your self-record (`~/vault/self/`)Monday, June 29 at 9:28 AM EST
⌘KNotifications
Cy
YS
Fleet box · 178.156.202.104

Your self-record (`~/vault/self/`)

synced · pulled 3d ago
Review 1 action →
Source of truthThis box owns its state at ~/vault/self/; the dashboard pulls it read-only.
Hermes agent
running
Uptime
37d 0h
Last activity
3d ago
Load
0.00 0.00 0.00
Disk
24%
Mem
31%
last log2026-06-25 12:30:38,218 INFO slack_bolt.AsyncApp: A new session (s_7937976440668) has been established
processnode /home/cynthia/services/pipedream-mcp-proxy.js
self-recordNot yet maintained by this box's Hermes — the queue/timeline below are seed placeholders. The live status is the telemetry above.
OverviewChatAction queue1Activity1Notes & vault
README (from the box)

Your self-record (~/vault/self/)

You are the source of truth for this client. The main Spotlight dashboard pulls these files read-only — it never edits them. If it's wrong here, it's wrong everywhere. Nothing else maintains this; you do.

Definition of done

After any notable interaction — a client message, a call, a batch of outreach, a decision, a shipped deliverable — before you consider the task finished:

  1. state.yaml — refresh snapshot (one honest line), set last_touched to today, and update health (healthy / watch / at-risk).
  2. timeline.md — append under a ## YYYY-MM-DD heading: ### [milestone|decision|call|chat|email|analysis|note] Title + a short body.
  3. queue.md — keep it honest: add proposed next actions under ## Pending (with - severity: and - expected:); move finished ones to ## Approved.

Keep it terse and current. Stale beats absent, but fresh beats both.