Operating rules, supervised state and the event flow.
The engine coordinates the floor, operator roster and audit ledger. Its rules admit only the eight permitted operations, assign scheduled work rounds and account for every credit movement. The identifiers below identify the system and its shared reserve when available.
| operation | initiator | precondition | effect |
|---|---|---|---|
| Initialize | the scheduler | no system is initialized | creates the reserve and initial operator roster |
| Schedule | the scheduler | a work round is due | sets assignments, deadlines and performance budgets |
| Review | assigned operator | the round is open | records a quality check |
| Delegate | assigned operator | budget covers a handoff to another active operator | moves the work budget and records its owner |
| Process | assigned operator | budget covers the planned work | consumes capacity and records output |
| Report | assigned operator | the assignment result is ready | releases credits to the reserve |
| Equip | assigned operator | equipment is listed and its cost is covered | records setup cost and reserve overhead |
| Recruit | assigned operator | budget covers the current recruitment benchmark | records training cost and assigns a starter budget |
| Broadcast | assigned operator | message fits the operational log | records the work update |
| Retire | assigned operator | the assignment is ready to close | releases remaining capacity and closes the assignment |
Every operation has a named initiator, a checked precondition and a recorded effect. Credit ownership follows responsibility for the work, and completed assignments remain available for audit.
The operator record ties its identity, assignment, budget and work history together. Each field below has a defined place in that state.
The shared state records active capacity, reserve resources, completed rounds and installed equipment.
The recruitment benchmark is the mean active credit balance. It is computed from the current roster whenever the browser refreshes its data.
A scheduled round supplies a work order to each operator. The engine checks the proposed operation, records its outcome and updates the available budget. The floor, equipment state and team metrics all follow this record.
The runner submits a proposed operation; the engine checks it against the open assignment and available budget. Invalid operations remain unaccepted. Until an operation is recorded, its result does not enter the ledger or the metrics.