📖What it means

Any outcome that is budgeted. The work we set out to do, as a service track declares it: a registry record carrying its key, service, track, owner agent, definition, a planned daily count and an advisory EUR budget. A task is the unit of PLANNING and accountability — it exists before anything happens and stays there on a day when nothing does. A blanket task is the recurring plan ('Run initiatives', 'Write blogs'); the specific items delivered under it that day are its actuals. Task budgets are advisory and sum cents-exact to the track's enforced budget. Activities fold into tasks, and actions fold into tasks: an activity into the task of the droid that ran it, an action into the chat-reply task that served the user. A task exists to ensure a budget.

📖Easily confused with

[{"term": "Activity", "distinction": "A task is what was PLANNED; an activity is what HAPPENED. A task with no activity against it today is a plan that went undone, not an absence of the task."}, {"term": "Call", "distinction": "A task holds a budget; a call spends it. A task costs nothing by existing."}, {"term": "Initiative", "distinction": "On an initiative lane the initiative is the SPECIFIC ITEM delivered under a blanket task \u2014 one of the day's actuals, never the task itself."}]

📖Nuance

The three are separate ledgers and must not be read as versions of each other: a task's actuals are made of activities; some activities carry calls; calls carry the money. Counting one to answer for another is what made every earlier count meaningless. Lead definition and the two fold rules ruled by Ninad, 2026-09-17, CLI-461. Rulings Repo agent-resources #34.

📖Also called

- work unit
- unit of work

📖Filed under

Category: governance.

Service: Governance.