Loopx

Key features

• LoopX keeps the architecture explicit so the same governed outcome can survive a change of agent harness or external provider.
• The Kernel folds its mechanics into five questions.
• Goal state and statusTracks active state, todos, claims, gates, evidence, run history, and first-screen attention.: loopx status, loopx diagnose, loopx review-packet
• Capabilities turn those generic primitives into outcome-owned work lanes.
• The terms describe different boundaries rather than interchangeable kinds of plugin