Protocols — Your Playbooks
Step-by-step workflows that your AI executes on command.
Last updated: March 2026
What Are Protocols?
Every morning for the first 3 weeks, I typed the same 12-line prompt: read STATUS.md, check yesterday's summary, look for reminders, show me priorities. On week 4, I saved those 12 lines as a morning protocol file. Now I type one word — 'Morning' — and the entire sequence runs automatically.
Protocols are detailed, multi-step workflows stored as markdown files in ~/.claude/protocols/. Unlike rules (which define constraints from Chapter 4), protocols define processes — step-by-step instructions for complex tasks that the AI executes from start to finish. For your business, they standardize every recurring task.
Morning Boot Protocol
The most valuable protocol in any Genesis system. It runs when you say "Morning" and gives you a complete briefing to start the day.
# Morning Boot Protocol
## Trigger
User says: "Morning", "Good morning", or "I'm back"
## Steps
### Phase 1: Read Current State
1. Read ~/life/STATUS.md
2. Read yesterday's daily summary from ~/life/logs/daily_summaries/
3. Check ~/life/future_triggers.json for due reminders
### Phase 2: Build Battle Plan
Present to the user:
- **Top 3 priorities** for today (from STATUS.md)
- **Pending items** from yesterday
- **Due reminders** (time capsules)
- **Blockers** that need attention
### Phase 3: Get Confirmation
Ask: "These are today's priorities. Any changes before we start?"
## Output Format
Keep it under 30 lines. Be specific and actionable.Evening Shutdown Protocol
# Evening Shutdown Protocol
## Trigger
User says: "Goodnight", "Wrap up", or "That's it for today"
## Steps
### Phase 1: Review the Day
1. List everything completed today
2. Note any open items or blockers
3. Identify key decisions made
### Phase 2: Update Files
1. Write daily summary to ~/life/logs/daily_summaries/[date].md
2. Update ~/life/STATUS.md with new priorities
3. Check if any future_triggers.json entries need updating
### Phase 3: Tomorrow's Preview
Present:
- What carries over to tomorrow
- Any upcoming deadlines
- Suggested first task for tomorrow morningCustom Protocol Template
Use this template to create any custom protocol for your business. Good candidates: client onboarding, content publishing, sprint planning, weekly review.
# [Protocol Name]
## Trigger
User says: "[trigger phrase]"
## Prerequisites
- [What must exist before running this protocol]
## Steps
### Phase 1: [Phase Name]
1. [Step 1]
2. [Step 2]
3. [Step 3]
### Phase 2: [Phase Name]
1. [Step 1]
2. [Step 2]
## Output
[What the user should see when this protocol completes]
## Verification
[How to confirm the protocol ran correctly]The Cartographer Protocol — Map Before You Build
Before implementing any significant feature, create a blueprint. After completing it, document what was built. This protocol prevents building without understanding and ensures documentation is never an afterthought.
# System Cartographer Protocol
## Pre-Work (Before Implementation)
1. Read existing code in the target area
2. Create a state machine diagram showing the current flow
3. Create a file map listing all files that will be touched
4. Identify integration points and dependencies
5. Save blueprint to ~/life/docs/state_machines/[feature]-flow.md
## Post-Work (After Implementation)
1. Audit all files created or modified
2. Update the state machine with the actual implementation
3. Register new files in knowledge_index.md
4. Verify all documentation matches reality
## The Rule
No implementation happens without a map.
No implementation is complete without documentation.Protocols rely on the Life Repository (Chapter 2: The Life Repository) for reading and writing state. The morning protocol reads STATUS.md; the evening protocol writes daily summaries. Enforcement hooks (Chapter 6: The Enforcement System) can verify that protocols ran correctly, while the knowledge base (Chapter 7: The Knowledge Base) stores reusable patterns discovered during protocol execution.