Dependencies

This skill requires Python 3.8+ and standard library only. It requires the context-bundler and a functional metrics engine (e.g. eval_runner.py).

---

Triple-Loop Learning (Meta-Learning System)

This skill defines the orchestration pattern for the Triple-Loop Architecture. Pattern 5 is a robust, autonomous feedback loop where an independent Meta-Learning Orchestrator governs a long-horizon pipeline of execution, planning, and tactical problem-solving.

This architecture is entirely framework-agnostic. While originally developed for agent-agentic-os, it models the core loop defined by Meta-Harness research where autonomous systems evolve their own operating instructions based strictly on headless evaluators.

Architecture Overview

flowchart TD
    subgraph Outer["Outer Loop (Meta-Learning & Orchestration)"]
        Diagnose[Friction Aggregation] --> Hypothesize[Hypothesis Generation]
        Hypothesize --> StrategyBridge[Strategy Packet]
        EvalBridge[Objective Score Analysis] --> Persist[Keep/Discard & L3 Memory]
    end

    subgraph Mid["Strategic Planner (Dual-Loop Integration)"]
        Plan[Define Sub-tasks] --> TacticalBridge[Handoff Packet]
        Result[Aggregate Results] --> Report[Generate Report]
    end

    subgraph Inner["Tactical Executor (Single-Loop Integration)"]
        Execute[Code Mutation] --> Test[Headless Evaluation]
        Test --> ResultBridge[Pass/Fail Signal]
    end

    StrategyBridge --> Plan
    Report --> EvalBridge
    TacticalBridge --> Execute
    ResultBridge --> Result

---

The Workflow Protocol

Step 1: Friction Aggregation (Outer Loop)

1. The Orchestrator constantly ingests execution logs from existing operations. Look for repeated uncertainties, API errors, test failures, or syntax flaws.
2. Group the friction into clustered tasks.

Step 2: Hypothesis Generation (Outer Loop)

1. Define a singular thesis: "If we change instruction X, the accuracy score on benchmark Y will improve by N."
2. Write a rigid Strategy Packet for the Mid-level Planner.

Step 3: Distribution (Strategic Planner)

1. The Planner assigns disjoint code fixes to one or multiple Tactical Executors.
2. Ensure test boundaries are defined.

Step 4: Mutation & Headless Scoring (Tactical Executor)

Constraint: Subjective LLM analysis is expressly prohibited.

1. Apply the instruction set or code adjustment.
2. Run pure, headless deterministic tests. Return an objective integer/float score, not opinions.

Step 5: Verification & Promotion (Outer Loop)

1. Read the objective score differentials.
2. KEEP only if Accuracy AND F1 score pass the current baseline. Reject otherwise.
3. Postulate a retrospective mapping.

---