Gimbal
The allocation optimiser
StatusBuildIn build
Where it stands. In build: a resolver slice runs today; market watch and the shadow-validation loop are still ahead.
01What it does
01
Proposes model allocation
Gimbal watches the model market and the suite’s own run telemetry, and proposes evidence-backed remaps of which model each agent role runs on.
02
Nothing remaps without clearing the target Tool’s gate
It proposes into a Tool’s own config gate and that Tool disposes; nothing is remapped without passing that gate.
02Its place on the control plane
On the propose plane, Gimbal proposes and the Tool it targets disposes. Beneath every plane, Manifold is what makes an accepted remap a config line rather than a rebuild. Its propose-plane peers are below.
03Who it works with
A pairing here means two tools actually exchange something, and the thing they exchange is named.
- ConsoleConsumesReads the same allocation telemetry Console renders
- ManifoldGates (proposes remaps through)Gimbal's remaps are applied through Manifold's config switch, never a direct write
- Every dispatching sessionConsumesEvery launched sub-agent/packet appends an allocation row Gimbal reads
- HelmNamed as a pair, with no interaction specified yet.
04Where it does the work
Every launched sub-agent/packet appends an allocation row Gimbal reads. The workflows below are the ones that name it directly, the main ones, not an exhaustive account of everywhere that reach runs.
Others on the propose plane