context-first-gatekeeping

name: "context-first-gatekeeping" description: "The absolute gatekeeping factor for app development success. Context-first, never act without verified planning, unbroken hierarchy chains, and domain boundaries enforced." triggers: - "Before ANY implementation action" - "When starting a new task" - "After context compaction" - "When resuming from interrupted work" version: "1.0.0"

Context-First Gatekeeping Skill

The Prime Directive

NEVER ACT WITHOUT SUCCESS RETRIEVAL OF PLANNING

This is the absolute gatekeeping factor that determines whether app development succeeds or fails.

The Five Pillars

Pillar 1: Context-First Protocol

Before ANY action:

1. Load context (scan_hierarchy)
2. Recall relevant memories (recall_mems)
3. Check anchors for constraints (list_anchors)
4. Verify chain integrity (think_back)

Pattern:

LOAD → VERIFY → ACT

NEVER: Assume, guess, or "I think I remember..."

Pillar 2: Parent Hierarchy Must Exist

Unbroken chain requirement:

Trajectory (Level 1)
└── Tactic (Level 2)
    └── Action (Level 3)

Validation:

function validateHierarchy(): boolean {
  const hierarchy = scan_hierarchy({ action: "status" })
  
  // Level 1: Trajectory must exist
  if (!hierarchy.trajectory) {
    throw new Error("NO TRAJECTORY - Use declare_intent first")
  }
  
  // Level 2: Tactic must exist for actions
  if (!hierarchy.tactic && isActionLevel()) {
    throw new Error("NO TACTIC - Use map_context first")
  }
  
  // Level 3: Chain must be unbroken
  const ancestors = getAncestors()
  if (ancestors.length < requiredLevel) {
    throw new Error("BROKEN CHAIN - Repair with map_context")
  }
  
  return true
}

Pillar 3: Never Act Without Verified Planning

Planning must be retrieved, not assumed:

// WRONG - Acting on assumption
// "I remember we planned to do X, let me implement it"

// RIGHT - Verifying planning exists
const plan = recall_mems({ query: "plan trajectory tactic" })
if (!plan || plan.length === 0) {
  throw new Error("NO PLAN FOUND - Create plan before acting")
}

// THEN act based on verified plan

Pillar 4: Domain Boundaries Enforced

Never cross domains without explicit approval:

Validation:

function validateDomainBoundary(files: string[], domain: string): boolean {
  const boundaries = DOMAIN_BOUNDARIES[domain]
  
  for (const file of files) {
    const inAllowed = boundaries.allowed.some(p => file.startsWith(p))
    const inForbidden = boundaries.forbidden.some(p => file.startsWith(p))
    
    if (!inAllowed || inForbidden) {
      throw new Error(`DOMAIN VIOLATION: ${file} not in ${domain}`)
    }
  }
  
  return true
}

Pillar 5: Context-Purified State

After context compaction, NEVER trust memory:

// After compaction event
if (justCompacted) {
  // RELOAD everything
  think_back({ mode: "full" })  // Reload context
  recall_mems({ query: "recent" })  // Reload memories
  list_anchors()  // Reload constraints
  
  // VERIFY chain still intact
  validateHierarchy()
}

The Gatekeeping Checklist

Before ANY implementation action:

┌─────────────────────────────────────────────────────────────┐
│                    GATEKEEPING CHECKLIST                     │
├─────────────────────────────────────────────────────────────┤
│  [ ] 1. Trajectory exists?         (declare_intent)         │
│  [ ] 2. Tactic defined?            (map_context)            │
│  [ ] 3. Plan retrieved from mems?  (recall_mems)            │
│  [ ] 4. Anchors loaded?            (list_anchors)           │
│  [ ] 5. Chain unbroken?            (scan_hierarchy)         │
│  [ ] 6. Drift acceptable (<60)?    (think_back)             │
│  [ ] 7. Domain boundaries OK?      (validateDomainBoundary) │
│  [ ] 8. No pending failures?       (brain.metrics.failures) │
└─────────────────────────────────────────────────────────────┘

IF ANY CHECK FAILS → STOP, FIX BEFORE PROCEEDING

Failure Escalation Protocol

When a gate fails:

Level 1: Auto-Recoverable

• Missing tactic → map_context({ level: "tactic" })
• High drift → think_back({ mode: "full" })

Level 2: User Guidance Needed

• No plan found → Ask user to provide/confirm plan
• Domain violation → Ask user for cross-domain approval

Level 3: Critical - Stop Chain

• No trajectory → Must declare_intent (new session)
• Broken chain → Must manually repair hierarchy

Integration with Sequential Orchestration

This skill is the first step in sequential-orchestration:

1. context-first-gatekeeping (THIS SKILL)
   ↓ All gates pass
2. sequential-orchestration
   ↓ Sequential delegation
3. export_cycle
   ↓ Intelligence captured
4. map_context
   ↓ Hierarchy updated

Red Flags - Immediate Stop

Quick Commands

# Full gatekeeping check
scan_hierarchy({ action: "status" })  # Check hierarchy
think_back({ mode: "check" })          # Check drift
recall_mems({ query: "plan" })         # Check planning
list_anchors()                        # Check constraints

# Repair broken chain
map_context({ level: "tactic", content: "..." })
map_context({ level: "action", content: "..." })

# Context recovery
think_back({ mode: "full" })

Gatekeeping Flow Diagram

digraph gatekeeping {
    "Action Requested" [shape=doublecircle];
    "Trajectory Exists?" [shape=diamond];
    "Declare Intent" [shape=box];
    "Tactic Defined?" [shape=diamond];
    "Map Context" [shape=box];
    "Plan Retrieved?" [shape=diamond];
    "Recall Mems" [shape=box];
    "Chain Unbroken?" [shape=diamond];
    "Think Back" [shape=box];
    "Drift OK?" [shape=diamond];
    "Domain OK?" [shape=diamond];
    "Get Approval" [shape=box];
    "PROCEED" [shape=doublecircle, style=filled, fillcolor=green];
    "STOP" [shape=doublecircle, style=filled, fillcolor=red];

    "Action Requested" -> "Trajectory Exists?";
    "Trajectory Exists?" -> "Declare Intent" [label="no"];
    "Trajectory Exists?" -> "Tactic Defined?" [label="yes"];
    "Declare Intent" -> "Tactic Defined?";
    "Tactic Defined?" -> "Map Context" [label="no"];
    "Tactic Defined?" -> "Plan Retrieved?" [label="yes"];
    "Map Context" -> "Plan Retrieved?";
    "Plan Retrieved?" -> "Recall Mems" [label="no"];
    "Plan Retrieved?" -> "Chain Unbroken?" [label="yes"];
    "Recall Mems" -> "Chain Unbroken?";
    "Chain Unbroken?" -> "Think Back" [label="no"];
    "Chain Unbroken?" -> "Drift OK?" [label="yes"];
    "Think Back" -> "Drift OK?";
    "Drift OK?" -> "Think Back" [label="no (>60)"];
    "Drift OK?" -> "Domain OK?" [label="yes (<60)"];
    "Domain OK?" -> "Get Approval" [label="no"];
    "Domain OK?" -> "PROCEED" [label="yes"];
    "Get Approval" -> "PROCEED" [label="approved"];
    "Get Approval" -> "STOP" [label="denied"];
}

This skill is a companion to hivemind-governance and must be loaded BEFORE any implementation work begins.