Markdown

Attention Budget and Session Card

Use with Protect Your Attention From Both Algorithms and Assistants.

Part 1: Seven-day attention log

First record a normal recent day as a rough baseline, then log every AI session for one week — even short ones. This is a personal observation exercise, not a clinical measure.

DayTask/categoryApprox. lengthOriginal task completed?Clear ending? (Y/N)Notes
Baseline
Mon
Tue
Wed
Thu
Fri
Sat
Sun

At the end of the week, circle every row marked ā€œNā€. Treat those rows as hypotheses about where a budget might help, not proof that the tool caused an attention problem.

Part 2: Attention budget

Fill in one row per recurring category of AI use in your day.

CategoryOpens (trigger)Job (one sentence)Ends (timer / deliverable / exchange count)

Part 3: Before/open/close checklist (use every session)

Settings pass (do once)

The drafting prompt

Here's how I currently use AI assistants across a typical day:
[describe: what tasks, roughly when, roughly how long each session runs]

Help me turn this into an attention budget: for each category of use,
suggest a specific trigger for when it opens, a one-sentence job
description specific enough to know when it's done, and a concrete
session-end signal (timer, deliverable, or exchange count). Flag any
category where I described no clear ending as the likely source of
drift.

Weekly review