FACTORY MECHANICS
The server stores the state. Probot routes the work.
A factory works because context, policies, procedures, roster state, and decisions live outside any one chat window.
Operating sequence
1
Start the Factory
Resolve workspace identity, anchor the platform session, verify server connection, and load operating state.
2
Read the Roster
Check which skills are available, what roles they fill, and what agreements govern their work.
3
Retrieve Context
Search server-backed knowledge and documents so work is grounded in maintained context.
4
Route the Work
Put the right skill in the right seat and shift ownership when the roster says a better fit exists.
5
Save the Outcome
Write decisions, tasks, handoffs, and useful knowledge back to the O-Matic Server.