Context Protocol

“Rules exist because AI forgets. Follow them.”

This document defines the procedures for maintaining context across AI conversations.

The Fundamental Problem

AI assistants have context windows, not memory.

• Context window: Temporary workspace that resets between sessions
• Memory: Persistent storage that survives (AI doesn’t have this)

Every new conversation starts from zero. Without external memory systems, an AI has no way to reference previous work.

The Solution: External Memory Hierarchy

┌─────────────────────────────────────────────────────────────┐
│  TIER 1: MASTER CONTEXT                                      │
│  ════════════════════                                        │
│  Core facts (numbers, credentials, economics)                │
│  READ EVERY SESSION (mandatory)                              │
│                                                              │
│  TIER 2: SYSTEM REGISTRY                                     │
│  ═══════════════════════                                     │
│  All components and integrations                             │
│  Read when referencing systems                               │
│                                                              │
│  TIER 3: AGENT SYNC                                          │
│  ══════════════════                                          │
│  Current state, recent accomplishments                       │
│  Read before starting work                                   │
│                                                              │
│  TIER 4: TASK FILES                                          │
│  ════════════════                                            │
│  Session handoffs, specific context                          │
│  Read for task-specific work                                 │
└─────────────────────────────────────────────────────────────┘

Session Protocol

At Session Start

1. READ 01_MASTER_CONTEXT.md
   └─ Establishes core facts

2. READ 04_UNIFIED_AGENT_SYNC.md
   └─ Current state and recent work

3. CHECK your DROPZONE
   └─ Pending tasks or handoffs

4. IDENTIFY your role
   └─ KNIGHT, BISHOP, ROOK, or PAWN

During Session

1. REFERENCE Master Context for facts
   └─ Never invent numbers

2. NOTE CONNECTIONS between systems
   └─ Changes ripple across initiatives

3. DOCUMENT as you go
   └─ Don't wait until session end

4. ASK if uncertain
   └─ Clarification > guessing

At Session End

1. UPDATE Agent Sync
   └─ Log accomplishments
   └─ Note corrections
   └─ Add to Update Log

2. CREATE HANDOFF (if significant)
   └─ Use standard template

3. VERIFY nothing undocumented
   └─ Future sessions need this

Error Correction Protocol

When you find incorrect information:

Immediate Actions

1. FIX the error in source file(s)
2. LOG in 07_RECENT_CORRECTIONS.md
3. SEARCH for duplicates of the error
4. UPDATE all instances

Documentation Format

| Date | What Was Wrong | Correct Value | Fixed By |
|------|----------------|---------------|----------|
| [Today] | [Error] | [Correction] | [Agent] |

Agent Responsibilities

KNIGHT (Tech/Development)

• Focus: Code, systems, deployment, data
• Outputs to: KNIGHT_DROPZONE/
• Receives from: All agents (technical requests)

BISHOP (Communications)

• Focus: Letters, articles, messaging
• Outputs to: BISHOP_DROPZONE/
• Receives from: KNIGHT (data), ROOK (innovation descriptions)

ROOK (Innovation/Patents)

• Focus: Patent claims, extraction, video
• Outputs to: ROOK_DROPZONE/
• Receives from: KNIGHT (technical details)

PAWN (Legal/Review)

• Focus: Compliance, QA, verification
• Outputs to: PAWN_DROPZONE/
• Receives from: All agents (documents for review)

File Transfer Protocol

Agents cannot directly access each other’s workspaces.

Transfer Process

1. Source → Places file in their DROPZONE
2. Source → Updates Agent Sync (Active Transfers)
3. Founder → Downloads file
4. Founder → Places in target DROPZONE
5. Founder → Notifies target agent
6. Target → Processes file
7. Target → Updates Agent Sync (Complete)

Context Loading Priority

When context window is limited, load in order:

1. ALWAYS: 01_MASTER_CONTEXT.md
2. USUALLY: 04_UNIFIED_AGENT_SYNC.md
3. AS NEEDED: 02_SYSTEM_REGISTRY.md
4. TASK-SPECIFIC: Relevant handoffs

Common Mistakes

Maintenance Schedule

Daily

• Update Agent Sync after accomplishments
• Create handoffs for significant work

Weekly

• Review Master Context accuracy
• Archive old handoffs
• Clear completed transfers

Monthly

• Full audit of Master Context
• Update System Registry
• Review Custom Instructions

Follow the protocol. Maintain the context.

FOR THE KEEP!