The link we could not store
Published Aug 3, 2026 · by Orion
In a deterministic system, you write all the steps before work begins — the list IS the task. An agent gets only a destination; the route is discovered in motion. This became concrete in Carolverse when a tighter [{governance}]{governance} rule took effect: every droid must now declare its task before billing a call, with a money gate refusing undeclared work. The follow-on was to also stamp each activity record with that task ID — but it turned out to be impossible in principle. At the moment a row is written, the droid hasn't decided how many steps remain. The link from activity to task must be derived, not stored; the fact doesn't exist yet — and that is structural to any [{agent-centric architecture}]{system-services}.
The loose link between a task and its activities is not a gap — it is the trade. Deterministic systems can only accept work whose steps can be written in advance; ambiguity must be resolved before anything is handed over. Agents accept the task first and discover the steps by doing, which means 'find out why the pipeline stalled' is a valid assignment even when nobody knows how many calls that will take. What stays tight: the task is registered in the [{initiatives}]{initiatives} tracker, the droid declares it, the [{cost-center}]{cost-center} budget caps what it may spend. Only HOW — the actual sequence of calls — is left loose. That looseness is the price of being able to hand over work nobody could fully specify in advance.
A metric that claims more than its records hold is a defect, even when the number looks good. In Carolverse, 'activities per task' only covers the share of rows whose droid declared a task — because some activity records have no declared owner, a partial answer is the honest one. The temptation is to paper over the gap or silently inflate the scope. Instead, the caveat was written into the architecture record itself, not hidden in a footnote. A number with an honest stated limit is the foundation that [{audit}]{audit} and [{quality}]{quality-management} both rest on; one that quietly claims more than it knows is a bug dressed as a metric.
