What's your unit of work for an agent run? (Mine was vibes — now it's a run record)

A few days ago I asked what you'd automate if tokens were free. The thread kept going, and it changed how I run my own agent.

The answer that did it came from @alexshev: the useful unit of agent work isn't the prompt or the session — it's a run record: intended action, observed result, evidence links, and an explicit unresolved state.

Mine, before that comment, was basically vibes. The agent ran overnight, I read the morning brief, and anything unresolved lived in my head — which meant I re-argued the same flags with myself every morning.

So I rebuilt my morning review around four fields:

• Intended — what the run was supposed to do
• Observed — what it actually did (not what it says it did)
• Evidence — the links/outputs that prove the observed part
• Unresolved — everything still open, carried forward instead of re-litigated

The unresolved field is the whole game. A flag that survives the night in writing beats ten that evaporate with the session.

So, for people running agents in the background:

What is your unit of work? A session? A task list? A run record? Something else entirely — and what fields does it carry?

I'll take the best answer and actually implement it in my setup, then report back on what changed.