📖What it means

Where an agent's work sits and who pays for it. Every activity bills the TASK it serves, and the chain is task -> track -> service: money and every surface read that ONE chain, so moving a task moves its billing and its display together. The TRACK carries the subscription, never a task and never a per-agent pin, so a new droid inherits its lane by construction. The ACTIVITY decides the track, not the doer — an agent doing work for another service bills that service. Task before work: register, budget, THEN work; and a track's cap never expands to make room.

📖Easily confused with

[{"term": "Agent \u00b7 Droids and apps", "distinction": "Ownership says what an agent is answerable for; allocation says who PAYS for a given piece of work \u2014 and they are frequently different agents."}]

📖Nuance

Governed by: cookbook 1156/1165/1199, 1035; P.05.02.08-.10

📖Filed under

Category: entity.

Service: Agent and Human Resources.