Standard Operating Procedures
Benchmarked against: Anthropic — (No direct equivalent — SuperPortia operations feature)
Storage: Cloud UB + .claude/rules/ + .claude/skills/
Scope: Recurring procedures that all agents must follow
SOPs are the step-by-step playbooks for recurring operations. They ensure consistency across agents and sessions.
SOP index
Session management
| SOP | Trigger | Location | Description |
|---|
| Session Start | Every new session | AIP Section 1 + hooks | Heartbeat, mailbox, ask Captain |
| Compaction Recovery | After context compaction | compaction-recovery-protocol.md | Read summary, confirm context, resume |
| Session Handoff | Session ending | AIP Section 5b | Save todos to Cloud UB |
| Pre-Exit | Session ending | AIP Section 5 | Confirm ingestions, report summary |
Decision making
| SOP | Trigger | Location | Description |
|---|
| Pre-Flight Check | Before non-trivial tasks | Cloud UB: ub-a0914abf17a7 | 3D scoring: Blast Radius x Knowledge Freshness x Reversibility |
| 66s Review | Major decisions, specs | Skill: /66s-review | Six Hats + Six Shoes systematic analysis |
| HITL Decision | Captain approval needed | Constitution Section 11 | Q / Options / Recommendation / Captain reply |
| Pre-Decision Search | Before important decisions | AIP Section 2 | Search UB for precedents |
Knowledge management
| SOP | Trigger | Location | Description |
|---|
| Search-First Flow | Need information | Constitution Section 6 | UB first → delegate search → ingest → use |
| Correction Capture | Captain corrects agent | AIP Section 3 | Dual ingest: Memory MCP + UB |
| Discovery | Learn new fact | AIP Section 4 | Decide: personal vs team → appropriate store |
| Research-Before-Plan | Technical planning | AIP Section 6 | Classify knowledge → verify perishable → then plan |
Work orders
| SOP | Trigger | Location | Description |
|---|
| WO Creation | New task needed | WO System docs | Title convention, valid assignees, required fields |
| WO Completion | Work done | WO System docs | Summary + actual hours → submit for review |
| WO Blocking | Impediment found | WO System docs | Status update with mandatory notes |
SOP design principles
| Principle | Application |
|---|
| Triggerable | Every SOP has a clear trigger condition |
| Checkable | Steps can be verified for completion |
| Searchable | Stored in UB or docs (not just memory) |
| Enforceable | Hooks/gates enforce critical SOPs |
| Lean | Minimum steps needed |
SOP vs rule vs skill
| Type | Loading | Where | Example |
|---|
| Rule | Always | .claude/rules/ | Cost awareness |
| Skill | On /command | .claude/skills/ | 66s Review |
| SOP | Referenced | Cloud UB + docs | Pre-Flight Check |
| Guide | On demand | Docs site | Fleet Setup |
Creating a new SOP
- Identify the trigger — What event starts this procedure?
- List the steps — What must be done, in order?
- Define verification — How do you know it's done correctly?
- Choose storage — UB entry, rule file, skill file, or docs page?
- Add enforcement — Can a hook or gate enforce it?
- Ingest to UB — So all agents can find it
Related pages