Your central operating layer

Say what you need.
Kevin OS routes the rest.

Use ChatGPT or Codex as the conversation. This home gives you one simple place to see connections, approvals, current work, and the systems behind it.

Open ChatGPT · Ask Kevin OS Open detailed work board

Connections

Loading routing policy…

Your portfolio

Every part of your work has a defined home and a boundary.

Right now

Loading the work queue…

Needs you

Only decisions or steps that genuinely require Kevin.

See all on the work board →

System queue

Work Claude, Codex, and the existing automations can advance.

See the full queue →

Everything else

Details when you want them, out of the way when you do not.

Work BoardClaude's queue, active priorities, and detailed status. Routing & ConnectionsWhich identities, domains, and mail lanes Kevin OS can use. ArchitectureHow ChatGPT, Claude, Manus, and the execution layer fit together. InventoryConnected systems and verified capabilities. The MoatThe strategy and defensibility behind the operating system. LinksDirect access to the few external systems you actually use.

Boundaries stay enforced. Invesco internal data and Papa Duffy's stock-picking work remain outside Kevin OS. Public career material is isolated to career/LinkedIn use, outside businesses are never exposed to Invesco, secrets remain references rather than values, and all existing Tier A/B/C plus HUMAN_ONLY gates remain in force.