Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖What it means
The droid that serves a task — the registered worker whose standing declaration says it is the one that performs this piece of declared work. A task with no task exec has nobody standing behind it: it may still be measured and still deliver, but nothing claims the work, so what it costs cannot be attributed to it unless the calls themselves carry its work ticket. A task may have several task execs, and one droid serves exactly one task.
⚖️What it is NOT
The neighbours this word is most often confused with, and the line between them.
Not: Doer vs Enabler
A DOER is a posture toward work — performing it rather than equipping someone else to. A TASK EXEC is a specific registry link: this droid serves that task. The words look alike and mean different things, which is exactly why this term was coined (Ninad, 2026-08-04).
Not: Work ticket
The task exec is a STANDING declaration on the droid; the work ticket is carried by a single CALL at the moment it is made. Where they disagree the ticket wins, because a call knows what it is for and a standing record only knows what is usual (P.01.03.07.04).
Not: Droid
Every task exec is a droid; not every droid is a task exec of the task you are looking at. 'Task exec' names the RELATIONSHIP, not the thing.
🧭The nuance
Coined by Ninad on 2026-08-04 (CLI-227) when the Task Tracker needed a word for it and 'doer' was borrowed from a term that already meant a posture. The estate had no name for the link at all, which is part of why 23 declared tasks were found with nobody behind them and no way to say so plainly.
🗣️Also called
task executorserving droidthe droid behind a task