Seats, labs, and cells
A seat is one member credential on one harness. [79] A lab is one vendor account family behind a set of seats. [116] A team member may hold seats on several vendors at once. [79]
Each launch runs in one docker cell with one claim. [112] The cell receives a per-launch throwaway database. [103] The engine drops that database when the launch ends. [103]
Usage truth
Each vendor pool is a row in the record. [156] An observation stores the used fraction and the reset time of the pool. [156] The usage_truth view derives the headroom of each pool. [156]
A pool with no read-back carries the mark unmetered. [116] The engine counts launches and lane-hours for an unmetered pool. [116] Routing reads the pool of the model that the seat will run. [130]
The Foreman rotation
The orchestrator seat is held by the member named fable. [15] A second seat named fable-shadow forms its own rulings from the record. [44] The shadow posts comparisons and never writes decisions. [44]
A handover moves the seat to a new session of the same member. [126] The outgoing seat writes the inventory before it stops. [126] The incoming seat reads the record and takes over. [126]