kybernetes:loop-governor

Kybernetes Loop Governor

Kybernetes is the one governor. Users describe outcomes, constraints, timing, and risk boundaries; the governor selects, combines, monitors, recovers, and retires runtime machinery. Native goals, threads, workers, hooks, schedulers, automations, and progress UI are advisory actuators or sensors, never canonical.

Kernel Invariants

1. Name a measurable setpoint and a sensor that can reject bad output.
2. Choose the smallest reliable harness that matches task variety.
3. Keep one active parent governor as the writer of canonical control.md.
4. Remember that runtime state is advisory; negotiate actual callable capability.
5. A recoverable wait remains canonical waiting_human, waiting_time, or waiting_event; never mirror it to an irreversible native blocked state.
6. Freeze new side effects on stale state, unsupported schema_revision, capability drift, conflicting ownership, or failed verification.
7. Stop only on verified completion, explicit supersession, a policy boundary, or a genuine terminal impediment.
8. A green runtime or safety check is not trajectory health; at the cumulative no-progress cap, reject stay with the unchanged strategy.

Sense And Size

Before significant action, sense only dimensions that can change the harness:

• objective, program kind, measurable finite DONE plus completion verifier or continuing health invariant plus review horizon and cycle verifier;
• duration, cadence, continuity, and next activation source;
• external effects, information release, reversibility, permissions, and HITL latency;
• brownfield implicit constraints, dependent-system impact, accountable owner, acceptance, and wrongness response;
• durability, concurrency, isolation, evidence, and notification needs;
• budget, attempt cap, stop semantics, and observed runtime capability.
• progress model, metric, measurement window, minimum delta, actionable capacity, fallback coverage, cumulative no-progress cap, and strategy authority;