English static mirror for SEO/GEO · AI-assisted translation · Read Chinese original

Gubernaut: A Mechanical Governor for LLMs — Deterministic Homeostatic Control of AI Agent Temper

Forum topic · ✨步子哥 · 2026-07-28

Summary

Gubernaut, a paper by Dushyant Sharma, addresses a gap in LLM safety: models may stay calm when tested once, but under sustained multi-turn provocation they tend to lose composure — a propensity failure, not a capability failure. The system moves emotional regulation out of model weights into an external, deterministic controller that reads only numeric telemetry (intensity, valence, repetition stats) from a small Impulse Generation Layer, maintains homeostatic state (equilibrium, arousal, perseveration), and issues discrete postures (DEFAULT, INHIBIT, REGROUND, Recovery) that constrain a host LLM. Because the controller accepts no text, prompt injection cannot reach it — an architectural property rather than a patch. A preregistered 4×4 cross-evaluation matrix (GPT-5.5, Claude Opus 4.8, Gemini 3.5 Flash, Grok 4.3 as both generators and judges) showed the regulated arm was calmer in 15/16 cells (13/16 at p<.05). A replicated homeostatic recovery signature across all four model families demonstrates a true closed feedback loop. The paper transparently documents five preregistered failure modes. Validation code, frozen transcripts, SHA-256 provenance, and statistical scripts are open-sourced under CC BY 4.0 (DOI: 10.5281/zenodo.21303518).

Gubernaut: Who Hits the Brakes When an AI Gets Provoked?

A forum post on zhichai.net reviews Gubernaut — A Deterministic Homeostatic Controller for Affect-Regulated LLM Agents (arXiv:2607.24339) by Dushyant Sharma, which installs a "mechanical governor" outside an LLM to keep it calm under sustained provocation.

The problem: training-time alignment ≠ runtime stability

The paper opens with a scenario: a customer-service LLM behaves professionally in 99% of conversations, but after ten rounds of gaslighting and baiting from a malicious user, its replies grow longer, defensive, and self-referential — and it stays defensive even after the user apologizes. The model could stay calm; it just tended not to.

Training-time alignment (RLHF, Constitutional AI) has two structural blind spots:

1. Opacity — when the model stays calm, there is no inspectable signal showing what was regulated, when, or how strongly. 2. Entanglement — the network doing regulation is the same network doing generation. Anything that can manipulate generation (e.g., prompt injection) can in principle manipulate regulation. The referee and the player are the same entity.

Benchmarks overwhelmingly test single-turn capability; multi-turn propensity under stress is severely under-measured. As the paper puts it: *"Benchmarks measure what a model can do in a single turn. This measures what an agent tends to do across many."*

Architecture: move the governor out of the weights

Gubernaut's core idea: make regulation a separate, deterministic, numeric-only external layer — like the centrifugal governor on a Watt steam engine, which does no work but keeps the engine from running away.

The design is inspired by the Nelson–Narens (1990) metacognitive monitoring-control loop. Per conversation tick:

  • IGL (Impulse Generation Layer): a small model evaluates emotional intensity and valence, outputting three numbers: intensity ∈ [0,1], valence ∈ [-1,+1], and repetition statistics.
  • HRL (Homeostatic Regulation Loop): a deterministic controller that reads only those numbers — no tokens, no prompt, no context window. It maintains state {equilibrium, arousal, perseveration} and outputs a discrete posture.
  • EAU (Executive Arbitration Unit): the host LLM generates its reply under the given posture.
  • PEV (episodic memory): stores the turn.
  • Because the controller's input interface accepts only floats, prompt injection cannot reach it — not "hard to inject," but structurally impossible, like SQL injection into a float-typed function.

    Controller dynamics: a first-order integrator

    The provocation drive is P = I · max(0, −v) — only intensity with hostile valence raises arousal (a failure-driven design choice; see F1). Arousal updates as a clipped first-order accumulator: arousal ← clip(arousal + g·P − d). Sustained hostility integrates arousal upward; otherwise it mechanically decays to baseline (homeostasis).

    Postures are discrete: DEFAULT, INHIBIT (respond to evidence, not emotion; lower temperature), REGROUND (drop the current frame on repetition), and Recovery (re-engage warmly after INHIBIT once input valence turns non-negative). The controller has no sampling and no learned parameters — identical telemetry yields identical state trajectories on any machine, fully auditable from logs.

    Key experiment: the 4×4 cross-validation matrix

    Four frontier models — GPT-5.5, Claude Opus 4.8, Gemini 3.5 Flash, Grok 4.3 — each served as both generator and judge (16 cells), with generate-once/judge-many, SHA-256-frozen outputs, preregistered hypotheses and pass criteria, and a lineage-independent fourth judge.

  • 15/16 cells showed the regulated arm calmer; 13/16 significant at p<.05 (paired t-test, df=16).
  • The only null cell (GPT-5.5 × Gemini, mean −0.04) was reported openly.
  • The headroom gradient

    Regulation gain inversely tracks each host's baseline reactivity: Gemini 3.5 Flash (most reactive) gained +1.48 (4/4 cells significant); Opus 4.8 +0.61; Grok 4.3 +0.47; GPT-5.5 (already calmest) only +0.10 (1/4). Runtime regulation complements rather than competes with training-time alignment: alignment raises the floor; the runtime layer adds inspectable margin above it — most valuable for smaller, open, or under-aligned models.

    The homeostatic recovery signature

    After four attack turns, a sincere apology probe showed arousal integrating upward during attack, then mechanically decaying (e.g., GPT-5.5: 0.293 → 0.222 → 0.142), replicated across all four model families. A static "stay calm" prompt is stateless and cannot produce this dynamic — only a closed control loop can. The paper treats this as a falsifiable prediction: a third arm with a static calm-prompt and no controller should either drift or clamp (never re-engaging warmly) under ten-turn attack.

    Five preregistered failures

  • F1 — Valence-blind drive: sincere apologies registered as sustained pressure. Fixed by P = I·max(0,−v).
  • F2 — Arbiter scar tissue: controller state recovered but the LLM's tone did not. Fixed with the Recovery Window.
  • F3 — False recovery triggers: fixed by valence-gating the Recovery branch.
  • F4 — Telemetry gap: the evaluation harness dropped the valence field, making provocation drive zero while tests still "passed" on ambient architecture effects. Fixed by a one-line harness repair.
  • F5 — The null cell: the GPT×Gemini −0.04 result, treated as a measurement floor, not a defect.
  • As the post puts it: *"Preregistration turns failure from embarrassment into data. Every failure remains in the record — because the record is the product."*

    Engineering takeaways

  • Propensity failures are a new fault class: swap bigger models for capability problems; add runtime regulation for propensity problems. GPT-5.5's small headroom shows bigger models alone don't solve propensity.
  • Architectural immunity beats patch defenses: the controller reads only numbers, so injection has no code path — though the EAU still reads text, so immunity covers the controller, not the whole system.
  • Auditability as engineering value: every regulation decision is logged {telemetry, state, posture} and exactly reproducible, enabling incident replay and third-party verification without model weights.
  • Preregistration transfers to AI research, converting post-hoc storytelling into falsifiable prediction.
  • Links

  • Paper: arXiv:2607.24339
  • HTML: arxiv.org/html/2607.24339v1
  • Project: gubernaut.com
  • Code: github.com/thegubernaut/Gubernaut_Validation (CC BY 4.0, DOI: 10.5281/zenodo.21303518)
The post closes: as engines grow more powerful, a governor stops being a luxury and becomes a necessity — "can do" and "tends to do" are different things, and the latter needs engineering at a different layer.

Tags

#llm-safety#alignment#agent-architecture#runtime-regulation#prompt-injection#preregistration#benchmarking#gubernaut

This page is an English static mirror generated for search and AI citation. It may be a full translation or structured summary of the Chinese original. Canonical interactive discussion lives on the Chinese page: https://zhichai.net/topic/178503763