omatic-server-operating-guidelisted

# O-Matic Server — Operating Guide <!-- version: 3.3.0 | sig: 2 | author: James Walker | package: O-Matic Server Connection --> This plugin is project-centric. Resolve the active factory from folder context before running factory work. ## Operating Model - One Codex session operates one factory. - Folder context wins. Do not switch factories inside a session unless the operator explicitly asks to override project context. - Use the factory tools before raw SQL when a high-level tool exists. - Destructive SQL requires explicit operator confirmation. - Work claims are per factory and auto-expire when the `work_claims` table is installed. - The plugin is the gateway/tool surface; the factory database remains the source of truth. ## Startup When the operator says `start the factory`, `restart the factory`, `Probot start`, or `run startup`: 1. Call `omatic_resolve_factory`. 2. Call `omatic_factory_startup_run` when available. It opens the platform session, seeds readiness, records built-in probes, warms retrieval, and returns the scoped startup packet. 3. If `omatic_factory_startup_run` is unavailable, call `omatic_factory_startup` and then execute the DB startup rules returned by `v_startup_rules`. 4. Report the startup summary, connector readiness, embedding health, SOP index presence, and agent agreement flags. 5. If an exact session audit is needed later, pass the current `factory_sessions.id` to `omatic_factory_startup`. If this skill is loaded in Codex but `omatic_*`