We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Docs sweep: brand ThrottleKit Lens; new Scaling/Policy Plans/Replay pages; 8-tab Lens + Monitor door - Home/_Sidebar: (TUI) -> (Lens), Policy-Plans compare row, links to the new pages - Monitoring-and-the-Lens: rebrand to ThrottleKit Lens, 5 -> 8 tabs (Cost Room/Replay/Plan), Monitor door section - new pages: Scaling-and-the-Fleet (Tier-1 + Tier-2 + leaseWindowed), Policy-Plans, Replay - Tier-1/Tier-2 cross-links + Monitor door across Polyglot/Operations/Federation/Pillar-4/Unified/Distributed/Performance/Middleware
docs(concurrency): 0.11.2 — PostgresConcurrencyCoordinator (shipped) + demand-proportional allocation (opt-in)
Distributed adaptive concurrency: eager handoff (D-DAC-20) + self-fencing (D-DAC-21) Document the 0.11.0 completion of the hard bound: eagerHandoff removes the acknowledged-handoff ramp-latency cost (near-floor ramp, no loosening of the bound; the pitch-perfect {acknowledgedHandoff, eagerHandoff} config), and self-fencing (default ON under fail-closed) closes the partition in-flight overshoot under the standard bounded-clock-skew assumption, with the FLP/CAP frontier stated honestly.
Distributed adaptive concurrency: document acknowledged handoff (opt-in hard async bound, D-DAC-19 / TK-1330)
Distributed-Adaptive-Concurrency: occupancy cap (D-DAC-18) The 0.10.0 coordinator reserves each peer's max(share, inflight), eliminating the synchronous rebalance overshoot in Σ inflight (a joiner no longer ramps into an incumbent's still-occupied capacity). Kept the honest framing: this is NOT a hard instantaneous bound across the async fleet — grant-reply + reporting lag leave a bounded (~1.5–2×), self-draining residual; a hard instantaneous bound would need acknowledged handoff. InflightCap is model-checked in the synchronous spec + twin.