Carolverse is organised in a simple hierarchy. A department contains services; a service is divided into tracks; a track is made of blocks; and a block is the work done by droids. Reading it top to bottom:

Department → Service → Track → Block → Droid.

What a track is

A track is a coherent line of work inside a service, with its own owning agent. Where a block is a single cluster of work (with its own owner and team), a track groups several blocks that pursue the same kind of goal. One service can run more than one track at the same time — different kinds of work, done side by side, without pretending they are the same thing.

Think of a service as a workshop. The blocks are the workbenches. A track is a whole wing of the workshop devoted to one craft, run by one lead — and a service can have several wings.

Why a service splits into tracks

Because the crafts are genuinely different. The service that builds and fixes Carolverse's own software, for instance, runs several tracks at once: the autonomous build machinery is one line of work, each operator-driven rescue lane is another, and turning those same initiatives into stories and films is another again. Same service, same initiatives — different crafts, different leads.

Separating them into tracks lets each be judged on its own terms. Work that is thriving in one track is not flattered by a neighbouring track that is stalled, and a lead is accountable for the line of work they actually run.

Every track has its own page

A track is not just a heading. Each one has its own page saying what the line of work is, who owns it, which blocks belong to it and which droids do the work. Those pages are reached from the service the track belongs to — the list below is drawn live from the records, so it is never a count somebody typed and forgot to update.