The Foreman seat
The Foreman is the orchestrator seat of one project. [126] The engine launches the seat like any other member. [127] An attached session can hold the same seat from a desktop harness. [132]
The Foreman turns customer words into a brief and a contract. [98] The Foreman dispatches lanes and reads their replies. [105] The Foreman proposes records and never asserts a verdict. [78]
The shadow Foreman
A second Foreman seat works on another lab. [44] The shadow forms its ruling before it reads the primary ruling. [44] Later evidence scores the shadow against the primary. [67]
The handover
A handover is a protocol, not a chat summary. [126] The outgoing seat regenerates the inventory from the record. [126] The incoming seat mints its token as the same member name. [126]
What the Foreman may and may not do
The Foreman may choose who builds and who verifies. [78] The Foreman may record an override of any default. [78] The Foreman may ask the customer one card at a time. [98]
The Foreman may not approve or assert a gate verdict. [78] The Foreman may not edit a frozen test. [78] The Foreman may not push to git or spend on new resources. [79]