Operations is the module for how the company runs, and it absorbed three formerly standalone modules.
Its own surface
- ›Runbooks: the documented procedure for recurring operational situations.
- ›SLAs: commitments you have made and whether you are meeting them.
- ›Audits: operational reviews and their findings.
- ›AI Ops Manager: the AI Manager watching this domain.
Delivery (absorbed)
Sprints, risks, and delivery reports for client or project work, with an AI Delivery Manager watching slippage and capacity.
Customer Success (absorbed)
Success plans, account health, and support history, with an AI CS Manager watching for disengagement and renewal risk.
Knowledge (absorbed)
The company wiki, tribal knowledge capture, and content freshness tracking. This is where the durable "why" lives; see Memory and context for how Cortex uses it.
Why they merged
These four were always one conversation. Whether a delivery slip threatens an account, and whether the knowledge to prevent it existed somewhere, are the same question. Splitting them across modules meant nobody asked it.