claude-flow-novice 2.10.5 → 2.10.7

package/claude-assets/skills/cfn-loop-validation/evidence-chain.sql

@@ -0,0 +1,163 @@
+-- CFN Loop Validation Evidence Chain Schema
+-- SQLite database schema for storing validation results and audit trails
+
+-- Main validation runs table
+CREATE TABLE IF NOT EXISTS validation_runs (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    run_id TEXT NOT NULL UNIQUE,
+    template_id TEXT NOT NULL,
+    template_version TEXT NOT NULL,
+    validation_mode TEXT NOT NULL CHECK (validation_mode IN ('mvp', 'standard', 'enterprise')),
+    status TEXT NOT NULL CHECK (status IN ('pending', 'running', 'completed', 'failed', 'retrying')),
+    start_time INTEGER NOT NULL,
+    end_time INTEGER,
+    consensus_score REAL,
+    consensus_threshold REAL,
+    validator_count INTEGER,
+    max_retries INTEGER,
+    retry_count INTEGER DEFAULT 0,
+    error_message TEXT,
+    created_at INTEGER DEFAULT (strftime('%s', 'now'))
+);
+
+-- Individual validator results table
+CREATE TABLE IF NOT EXISTS validator_results (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    run_id TEXT NOT NULL,
+    validator_id TEXT NOT NULL,
+    validator_type TEXT NOT NULL,
+    score REAL NOT NULL CHECK (score >= 0 AND score <= 1),
+    execution_time INTEGER NOT NULL,
+    status TEXT NOT NULL CHECK (status IN ('success', 'failed', 'timeout', 'error')),
+    error_message TEXT,
+    metadata TEXT, -- JSON blob for additional data
+    created_at INTEGER DEFAULT (strftime('%s', 'now')),
+    FOREIGN KEY (run_id) REFERENCES validation_runs(run_id) ON DELETE CASCADE
+);
+
+-- Evidence chain table for detailed validation steps
+CREATE TABLE IF NOT EXISTS evidence_chain (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    run_id TEXT NOT NULL,
+    step_type TEXT NOT NULL,
+    step_order INTEGER NOT NULL,
+    validator_id TEXT,
+    input_data TEXT, -- JSON blob
+    output_data TEXT, -- JSON blob
+    validation_result TEXT, -- JSON blob
+    timestamp INTEGER NOT NULL,
+    created_at INTEGER DEFAULT (strftime('%s', 'now')),
+    FOREIGN KEY (run_id) REFERENCES validation_runs(run_id) ON DELETE CASCADE
+);
+
+-- Retry log table for tracking retry attempts
+CREATE TABLE IF NOT EXISTS retry_log (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    run_id TEXT NOT NULL,
+    attempt_number INTEGER NOT NULL,
+    delay_ms INTEGER NOT NULL,
+    reason TEXT NOT NULL,
+    consensus_score REAL,
+    validator_count INTEGER,
+    timestamp INTEGER NOT NULL,
+    created_at INTEGER DEFAULT (strftime('%s', 'now')),
+    FOREIGN KEY (run_id) REFERENCES validation_runs(run_id) ON DELETE CASCADE
+);
+
+-- Performance metrics table
+CREATE TABLE IF NOT EXISTS performance_metrics (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    run_id TEXT NOT NULL,
+    metric_name TEXT NOT NULL,
+    metric_value REAL NOT NULL,
+    unit TEXT NOT NULL,
+    timestamp INTEGER NOT NULL,
+    created_at INTEGER DEFAULT (strftime('%s', 'now')),
+    FOREIGN KEY (run_id) REFERENCES validation_runs(run_id) ON DELETE CASCADE
+);
+
+-- Error tracking table
+CREATE TABLE IF NOT EXISTS error_tracking (
+    id INTEGER PRIMARY KEY AUTOINCREMENT,
+    run_id TEXT NOT NULL,
+    error_type TEXT NOT NULL,
+    error_message TEXT NOT NULL,
+    stack_trace TEXT,
+    validator_id TEXT,
+    timestamp INTEGER NOT NULL,
+    created_at INTEGER DEFAULT (strftime('%s', 'now')),
+    FOREIGN KEY (run_id) REFERENCES validation_runs(run_id) ON DELETE CASCADE
+);
+
+-- Indexes for performance optimization
+CREATE INDEX IF NOT EXISTS idx_validation_runs_status ON validation_runs(status);
+CREATE INDEX IF NOT EXISTS idx_validation_runs_mode ON validation_runs(validation_mode);
+CREATE INDEX IF NOT EXISTS idx_validation_runs_created_at ON validation_runs(created_at);
+CREATE INDEX IF NOT EXISTS idx_validator_results_run_id ON validator_results(run_id);
+CREATE INDEX IF NOT EXISTS idx_validator_results_validator_id ON validator_results(validator_id);
+CREATE INDEX IF NOT EXISTS idx_validator_results_created_at ON validator_results(created_at);
+CREATE INDEX IF NOT EXISTS idx_evidence_chain_run_id ON evidence_chain(run_id);
+CREATE INDEX IF NOT EXISTS idx_evidence_chain_timestamp ON evidence_chain(timestamp);
+CREATE INDEX IF NOT EXISTS idx_retry_log_run_id ON retry_log(run_id);
+CREATE INDEX IF NOT EXISTS idx_performance_metrics_run_id ON performance_metrics(run_id);
+CREATE INDEX IF NOT EXISTS idx_error_tracking_run_id ON error_tracking(run_id);
+
+-- View for completed validation runs
+CREATE VIEW IF NOT EXISTS completed_validation_runs AS
+SELECT 
+    vr.run_id,
+    vr.template_id,
+    vr.template_version,
+    vr.validation_mode,
+    vr.status,
+    vr.start_time,
+    vr.end_time,
+    vr.consensus_score,
+    vr.consensus_threshold,
+    vr.validator_count,
+    vr.error_message,
+    (vr.end_time - vr.start_time) as duration_ms,
+    COUNT(vr.id) as total_validators,
+    SUM(CASE WHEN vrs.status = 'success' THEN 1 ELSE 0 END) as successful_validators,
+    AVG(vrs.score) as average_score
+FROM validation_runs vr
+LEFT JOIN validator_results vrs ON vr.run_id = vrs.run_id
+WHERE vr.status = 'completed'
+GROUP BY vr.run_id, vr.template_id, vr.template_version, vr.validation_mode, vr.status;
+
+-- View for retry statistics
+CREATE VIEW IF NOT EXISTS retry_statistics AS
+SELECT 
+    rl.run_id,
+    vr.template_id,
+    vr.validation_mode,
+    COUNT(rl.id) as total_retries,
+    MAX(rl.attempt_number) as max_attempt,
+    AVG(rl.delay_ms) as avg_delay_ms,
+    MIN(rl.consensus_score) as min_consensus_score,
+    MAX(rl.consensus_score) as max_consensus_score
+FROM retry_log rl
+JOIN validation_runs vr ON rl.run_id = vr.run_id
+GROUP BY rl.run_id, vr.template_id, vr.validation_mode;
+
+-- Trigger to cleanup old records (optional - uncomment if needed)
+-- CREATE TRIGGER IF NOT EXISTS cleanup_old_records 
+-- AFTER INSERT ON validation_runs
+-- FOR EACH ROW
+-- BEGIN
+--     DELETE FROM validator_results WHERE run_id IN (
+--         SELECT run_id FROM validation_runs WHERE created_at < strftime('%s', 'now') - 2592000 -- 30 days
+--     );
+--     DELETE FROM evidence_chain WHERE run_id IN (
+--         SELECT run_id FROM validation_runs WHERE created_at < strftime('%s', 'now') - 2592000
+--     );
+--     DELETE FROM retry_log WHERE run_id IN (
+--         SELECT run_id FROM validation_runs WHERE created_at < strftime('%s', 'now') - 2592000
+--     );
+--     DELETE FROM performance_metrics WHERE run_id IN (
+--         SELECT run_id FROM validation_runs WHERE created_at < strftime('%s', 'now') - 2592000
+--     );
+--     DELETE FROM error_tracking WHERE run_id IN (
+--         SELECT run_id FROM validation_runs WHERE created_at < strftime('%s', 'now') - 2592000
+--     );
+-- END;

package/claude-assets/skills/cfn-loop-validation/examples/README.md

@@ -0,0 +1,453 @@
+# CFN Loop Validation - Coordinator Integration Examples
+
+This directory contains practical examples demonstrating how coordinators can integrate the CFN Loop Validation skill into their workflows.
+
+## Overview
+
+Each example script demonstrates a different integration pattern:
+
+1. **Loop 3 Confidence Gate** - Validate agent confidence before spawning validators
+2. **Loop 2 Consensus** - Validate Byzantine consensus from validator swarm
+3. **Full CFN Loop** - Complete workflow with all validation gates
+4. **Redis Integration** - Async validation with Redis pub/sub
+
+## Examples
+
+### 1. coordinator-loop3-gate.sh
+
+**Purpose:** Validate Loop 3 confidence gate before proceeding to consensus validation
+
+**Scenario:**
+- Primary swarm (coder + tester) completes work
+- Coordinator validates agent's self-assessed confidence
+- Decision: Proceed to validators OR retry with feedback
+
+**Usage:**
+```bash
+./coordinator-loop3-gate.sh
+```
+
+**Expected Output:**
+```
+=== Loop 3: Primary Swarm Execution ===
+Task: feature-user-authentication
+Mode: standard
+
+Executing primary swarm (coder + tester)...
+Agent reported confidence: 0.85
+
+=== Validating Loop 3 Confidence Gate ===
+
+Validation Result:
+  Status: PASS
+  Passed: true
+  Confidence: 0.85
+  Threshold: 0.80
+  Exit Code: 0
+
+✓ Confidence gate PASSED
+  → Proceeding to Loop 2 (spawning validators)
+```
+
+**Key Concepts:**
+- Confidence gate threshold validation
+- Automatic retry logic for low confidence
+- Escalation path for max iterations
+
+---
+
+### 2. coordinator-loop2-consensus.sh
+
+**Purpose:** Validate Byzantine consensus from validator swarm
+
+**Scenario:**
+- Validator swarm completes review (reviewer, security, tester, analyst, architect)
+- Coordinator calculates consensus score
+- Decision: Proceed to product owner OR retry validators
+
+**Usage:**
+```bash
+./coordinator-loop2-consensus.sh
+```
+
+**Expected Output:**
+```
+=== Loop 2: Consensus Validation ===
+Task: compliance-gdpr-implementation
+Mode: enterprise
+
+Spawning validator swarm...
+  - Validator 1: reviewer (confidence: 0.92)
+  - Validator 2: security-specialist (confidence: 0.95)
+  - Validator 3: tester (confidence: 0.88)
+  - Validator 4: analyst (confidence: 0.91)
+  - Validator 5: architect (confidence: 0.93)
+
+Consensus Results:
+  Average Confidence: 0.918
+  Consensus Score: 0.952
+
+=== Validating Loop 2 Consensus Threshold ===
+
+Validation Result:
+  Type: consensus
+  Status: PASS
+  Passed: true
+  Consensus: 0.952
+  Threshold: 0.95
+  Exit Code: 0
+
+✓ Consensus ACHIEVED
+  → Proceeding to Loop 4 (Product Owner Decision Gate)
+```
+
+**Key Concepts:**
+- Byzantine consensus validation
+- Multiple validator coordination
+- Enterprise mode threshold requirements
+
+---
+
+### 3. coordinator-full-cfn-loop.sh
+
+**Purpose:** Complete CFN loop workflow with validation at each gate
+
+**Scenario:**
+- Full orchestration: Loop 3 → Loop 2 → Loop 4
+- Iterative retry logic with feedback injection
+- Product owner decision gate (GOAP)
+
+**Usage:**
+```bash
+./coordinator-full-cfn-loop.sh
+```
+
+**Expected Output:**
+```
+╔════════════════════════════════════════════════════════════╗
+║           CFN LOOP ORCHESTRATION - Full Example            ║
+╚════════════════════════════════════════════════════════════╝
+
+Task: feature-payment-processing
+Mode: standard
+Max Loop 3 Retries: 3
+Max Loop 2 Retries: 2
+
+┌────────────────────────────────────────────────────────────┐
+│ LOOP 3: Primary Swarm Execution (Confidence Gate)         │
+└────────────────────────────────────────────────────────────┘
+
+--- Loop 3 Iteration 1 ---
+Executing primary swarm (coder + tester)...
+Agent self-assessed confidence: 0.75
+Validation: FAIL (threshold: 0.80)
+✗ Loop 3 gate FAILED
+  → Injecting feedback and retrying...
+
+--- Loop 3 Iteration 2 ---
+Executing primary swarm (coder + tester)...
+Agent self-assessed confidence: 0.82
+Validation: PASS (threshold: 0.80)
+✓ Loop 3 gate PASSED
+
+┌────────────────────────────────────────────────────────────┐
+│ LOOP 2: Validator Consensus (Byzantine Agreement)         │
+└────────────────────────────────────────────────────────────┘
+
+--- Loop 2 Iteration 1 ---
+Spawning validator swarm...
+  - reviewer
+  - security-specialist
+  - tester
+  - analyst
+
+Byzantine consensus result: 0.88
+Validation: FAIL (threshold: 0.90)
+✗ Loop 2 consensus FAILED
+  → Analyzing validator feedback and retrying...
+
+--- Loop 2 Iteration 2 ---
+Spawning validator swarm...
+Byzantine consensus result: 0.92
+Validation: PASS (threshold: 0.90)
+✓ Loop 2 consensus ACHIEVED
+
+┌────────────────────────────────────────────────────────────┐
+│ LOOP 4: Product Owner Decision Gate (GOAP)                │
+└────────────────────────────────────────────────────────────┘
+
+Invoking product owner decision...
+Product Owner Decision:
+  Decision: PROCEED
+  Confidence: 0.92
+  Reasoning: Payment processing implementation meets security and compliance standards. Ready for deployment.
+
+✓ Product Owner APPROVED
+  → Phase complete, proceeding to next phase
+
+╔════════════════════════════════════════════════════════════╗
+║                  PHASE COMPLETE - SUCCESS                  ║
+╚════════════════════════════════════════════════════════════╝
+
+Summary:
+  Task: feature-payment-processing
+  Mode: standard
+  Loop 3 Iterations: 2
+  Loop 2 Iterations: 2
+  Final Confidence: 0.82
+  Final Consensus: 0.92
+  Product Owner: PROCEED (0.92 confidence)
+
+Next Action: Proceed to next phase or deployment
+```
+
+**Key Concepts:**
+- Complete CFN loop orchestration
+- Iterative retry with feedback injection
+- Loop 3 → Loop 2 → Loop 4 flow
+- Product owner decision types (PROCEED, LOOP, DEFER, ESCALATE)
+
+---
+
+### 4. coordinator-redis-integration.sh
+
+**Purpose:** Async validation with Redis pub/sub for distributed coordination
+
+**Scenario:**
+- Coordinator runs validation
+- Results published to Redis for other agents
+- Event-driven workflow coordination
+
+**Usage:**
+```bash
+# Ensure Redis is running
+docker run -d -p 6379:6379 redis:latest
+
+# Run example
+./coordinator-redis-integration.sh
+```
+
+**Expected Output:**
+```
+═══════════════════════════════════════════════════════════
+  CFN Loop Validation with Redis Integration
+═══════════════════════════════════════════════════════════
+
+Task: distributed-task-microservices
+Mode: enterprise
+Iteration: 2
+Redis: localhost:6379
+
+Checking Redis connectivity...
+✓ Redis connection successful
+
+Running CFN Loop validation...
+Validation Result:
+  Status: PASS
+  Passed: true
+  Code: 0
+
+Publishing validation result to Redis...
+✓ Stored in list: cfn:validation:distributed-task-microservices
+✓ Set status key (TTL: 1 hour)
+✓ Published event: validation_passed
+✓ Updated task metadata
+
+Redis Integration Summary:
+  List: cfn:validation:distributed-task-microservices (validation history)
+  Key: cfn:validation:distributed-task-microservices:status (current status)
+  Channel: cfn:events (event stream)
+  Hash: cfn:task:distributed-task-microservices:metadata (task metadata)
+
+Other agents can subscribe to events:
+  redis-cli -h localhost -p 6379 subscribe cfn:events
+
+Query validation history:
+  redis-cli -h localhost -p 6379 lrange cfn:validation:distributed-task-microservices 0 -1
+
+✓ VALIDATION PASSED
+  → Proceeding to next phase
+```
+
+**Key Concepts:**
+- Redis list storage for validation history
+- Redis key-value with TTL for current status
+- Redis pub/sub for event distribution
+- Redis hash for task metadata
+- Event-driven agent coordination
+
+**Redis Event Format:**
+```json
+{
+  "type": "validation_passed",
+  "taskId": "distributed-task-microservices",
+  "mode": "enterprise",
+  "iteration": 2,
+  "confidence": 0.88,
+  "consensus": 0.94,
+  "timestamp": 1760818560
+}
+```
+
+---
+
+## Testing the Examples
+
+### Quick Test
+
+Run all examples in sequence:
+```bash
+# Test Loop 3 gate
+./coordinator-loop3-gate.sh
+
+# Test Loop 2 consensus
+./coordinator-loop2-consensus.sh
+
+# Test full CFN loop
+./coordinator-full-cfn-loop.sh
+
+# Test Redis integration (requires Redis)
+./coordinator-redis-integration.sh
+```
+
+### Customizing Examples
+
+Each script can be modified to test different scenarios:
+
+**Adjust confidence scores:**
+```bash
+# In any script, modify:
+AGENT_CONFIDENCE=0.75  # Change to test different thresholds
+```
+
+**Change validation mode:**
+```bash
+MODE="mvp"        # Fast iteration
+MODE="standard"   # Balanced validation
+MODE="enterprise" # Maximum security
+```
+
+**Test failure scenarios:**
+```bash
+# Set confidence below threshold
+AGENT_CONFIDENCE=0.60
+
+# Set iteration above max
+ITERATION=11
+```
+
+---
+
+## Integration Patterns
+
+### Pattern 1: Coordinator with Spawned Agents
+
+```bash
+# Coordinator spawns agents and validates results
+npx claude-flow-novice swarm "implement feature" --agents coder,tester
+
+# Get agent confidence from results
+AGENT_CONFIDENCE=$(parse_agent_response)
+
+# Validate
+./validate-iteration.sh --mode standard --iteration 1 --confidence $AGENT_CONFIDENCE
+```
+
+### Pattern 2: Event-Driven Coordination
+
+```bash
+# Agent 1: Publish validation result to Redis
+./coordinator-redis-integration.sh
+
+# Agent 2: Subscribe to events
+redis-cli subscribe cfn:events
+
+# Agent 2 receives event and acts accordingly
+```
+
+### Pattern 3: Multi-Phase Orchestration
+
+```bash
+# Phase 1: Authentication
+./coordinator-full-cfn-loop.sh  # Task: auth-system
+
+# Phase 2: Authorization (depends on Phase 1)
+if validation_passed("auth-system"); then
+  ./coordinator-full-cfn-loop.sh  # Task: authz-system
+fi
+```
+
+---
+
+## Exit Codes
+
+All examples follow the standard CFN Loop validation exit codes:
+
+| Code | Meaning | Action |
+|------|---------|--------|
+| 0 | Validation passed | Continue to next phase |
+| 1 | Validation failed | Inject feedback, retry |
+| 2 | Max iterations exceeded | Escalate to human |
+| 3 | Invalid arguments | Fix script parameters |
+| 4 | Configuration error | Check config.json |
+
+---
+
+## Dependencies
+
+**Required:**
+- `bash` (version 4.0+)
+- `jq` (JSON processor)
+
+**Optional:**
+- `redis-cli` (for Redis integration example)
+- `bc` (basic calculator, usually pre-installed)
+
+**Installation:**
+```bash
+# Ubuntu/Debian
+sudo apt-get install jq redis-tools bc
+
+# macOS
+brew install jq redis bc
+```
+
+---
+
+## Troubleshooting
+
+### Issue: "Permission denied"
+```bash
+chmod +x *.sh
+```
+
+### Issue: "jq: command not found"
+```bash
+sudo apt-get install jq
+```
+
+### Issue: "Redis connection failed"
+```bash
+# Start Redis
+docker run -d -p 6379:6379 redis:latest
+
+# Or install locally
+sudo apt-get install redis-server
+sudo systemctl start redis
+```
+
+### Issue: Line ending errors (Windows/WSL)
+```bash
+sed -i 's/\r$//' *.sh
+```
+
+---
+
+## Next Steps
+
+1. **Customize:** Modify examples for your specific use case
+2. **Integrate:** Use patterns in your coordinator implementations
+3. **Extend:** Add custom validation logic or Redis event handlers
+4. **Monitor:** Track validation metrics in Redis or SQLite
+
+For more information, see `/mnt/c/Users/masha/Documents/claude-flow-novice/.claude/skills/cfn-loop-validation/SKILL.md`