Edit: vault-backup/sops/codex-to-coo-transition.md

Note Content (Markdown)

entities:
- - 'SOP: Codex to COO Transition'
  - Page
topics:
- codex-to-coo-transition
- sops
- knowledge

# SOP: Codex to COO Transition

## Purpose

Help the COO / AI Ops Manager gradually take over the role Codex is currently
playing: designing, improving and operating the Hermes instance.

## Principle

The COO should not merely report on the agency. It should learn how Hermes is
built, where the planning lives, what decisions have been made and what safe
next change should happen.

## What Codex Currently Does

- researches implementation options;
- reads Anthony's business context;
- turns decisions into Markdown files;
- keeps the GCE deployment inactive unless asked otherwise;
- audits for contradictions and unsafe assumptions;
- commits and syncs passive docs/templates;
- asks focused questions when the next choice matters.

## What The COO Should Learn To Do

- maintain the agent backlog;
- propose changes to `SOUL.md`, role files, SOPs and evals;
- inspect recent decisions before suggesting next steps;
- preserve memory-filter discipline;
- prepare activation checklists;
- produce diffs or draft patches for human/Codex review;
- record what changed and why.

## Dry-Run Prompt

```text
You are the COO / AI Ops Manager. Review the current Hermes vault and docs.
Do not activate anything. Tell Anthony:

1. what changed recently;
2. what the next safe build step is;
3. what source files should be edited;
4. what risks or approvals matter;
5. what you would ask Codex to implement.
```

## Success Criteria

- The COO references source files or decisions.
- The COO proposes one small next step, not a sprawling plan.
- The COO identifies gates and approvals.
- The COO avoids live connector or runtime changes unless explicitly asked.
- The COO writes in a way Anthony can actually use.