Platform Layers › The two sealed loops
The two sealed loops
The two sealed loops
Operational loop, the harness learns how to run
Traces, cost, latency and eval trends → optimization of model routing, dispatch heuristics, compaction, caching. Business-blind by construction. Continuous, but every tuning lands as a versioned config change through CI; silent drift is a defect. The observability dashboards exist to drive this loop, with clean-instance A/B as the test bench.
Knowledge loop, P1Z learns what is true
Engagement telemetry + eval outcomes + curated consulting benchmarks → staging → promotion gate (anonymize → aggregate → rights check → human review) → versioned Knowledge release. Client-blind on output.
The wall between them: the operational loop never writes knowledge; the knowledge loop never tunes the harness. Two loops, two stores, two release trains.