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: officialize TALE full form (Temporally-Accounted Learned Escrow) Match GALE's heading style and put both full forms on the Home intro.
docs: monitoring is a built-in terminal dashboard (--tui), not the web Lens Rewrite the Monitoring page for the `throttlekit-server --tui` terminal dashboard (binding-axis hero + the actual TUI panels, keybinds, opt-in TTY, headless -> OTel/Grafana); update the Operations dashboard note, the Home feature/guide rows, and the sidebar link. The web Lens package is deprecated.
Add the Monitoring & the Lens page; link from Home, Operations, and the sidebar
docs: align Home tagline to the live site (beyond rate limiting; govern rate, concurrency & cost, provably)
docs: lead the Home tagline with GALE & TALE
docs: de-academicize positioning — capability-led, no 'research' labels Home 'Research-backed' bullet -> 'Proven, and shipping'; guides/sidebar/cross- link labels 'Research: GALE & TALE' / 'research track' -> 'GALE & TALE'; Research page retitled 'the proven guarantees' and venue mentions (SIGMETRICS/POMACS/NSDI) removed. GALE/TALE kept as engine names; the proof signals (TLA+, fleet-size- independent) kept; FairRide NSDI'16 prior-art citation kept.
Home: add a competitor comparison table (obvious differentiators)
docs: add Polyglot & Python page (service door + throttlekit-py, every axis); link from Home + sidebar
docs: 1.0.0 — API frozen under SemVer; refresh perf numbers Footer no longer says "0.x, API may still be refined before 1.0" — it now states the 1.0 SemVer freeze and links STABILITY.md. Home + Performance perf figures refreshed to the measured 1.0.0 run (169 ns/op checkSync, ~300 ns async, twoTier(leased) ~35x on Postgres) and point at BENCH.md as the canonical perf doc.
Pillar-4-Weighted-Fair-Escrow page + nav (TK-1312, queued for 0.9.1) New page: Pillar-4-Weighted-Fair-Escrow.md covering: - The 3-primitive fairness landscape comparison - The streaming algorithm (dynamic g_i + borrow phase with cost-cap) - T1-T4 guarantees + the T5 (FairRide) conceded vertex - L2 multi-process backing via existing Store + fixedWindow lease - Failure modes - Composition with combineDecisions / unifiedAdmission - Roadmap (federated WFE 0.10.x, hierarchical 0.10.x+) Sidebar + Home: added Pillar 4 entry pointing at the new page. Overload-Fairness-and-DDoS: expanded the weighted fairness section into a 3-row comparison table (weightedFairShare vs weightedMaxMin vs weightedFairEscrow), pointing at the new page for the multi-process work-conserving sibling. To push (release tag time only): cd C:\Users\ameya\tk-wiki && git push origin master
Add Unified-Admission page; update Home + Sidebar (0.9.0 prep — pushed at release tag time)
docs(federation): refresh 0.9.0 → 0.8.3 release references (DR-07) Federation #77 ships as 0.8.3 patch (not 0.9.0 minor) per the new DR-07 in research/bigger-bets/PLAN.md §8. Surface is purely additive so a patch is the right semver signal. Federation.md: - Coordinator backends table: 'Shipped 0.9.0' → 'Shipped 0.8.3' (×2) - PostgresCoordinator: '0.9.x follow-up' → '0.8.x follow-up' - SPOF caveat paragraph: 'For 0.9.0' → 'For 0.8.3' Home.md: - Guides table Federation row: '(0.9.0)' → '(0.8.3)' No content change beyond the version reference.
docs(federation): new Federation page + sidebar/home/Distributed-and-Provable cross-links (TK-911) The federation user-facing wiki page for the 0.9.0 release. Pushes to origin happen at release tag time per the local-accumulate-then-push rule (memory/throttlekit-wiki.md). New page Federation.md covers: - Quick start (federate + RedisCoordinator example) - The contribution narrative vs static partition (eval table at K=3) - All four outage shapes + Δ bound per shape - Coordinator backends matrix (TestCoordinator / RedisCoordinator shipped; PostgresCoordinator / Raft 0.9.x / 1.0.x follow-ups) - SPOF caveat + Sentinel/Cluster/Postgres/Raft mitigation ladder - Pointers to the TLA+ spec, BFS twin, DESIGN.md, RESULTS.md Cross-links added: - Home.md table: new Federation row - _Sidebar.md: new Federation link - Distributed-and-Provable.md: new 'Cross-cluster federation' sub-section that says when to use federate() vs the existing twoTier(leased) windowCoupled (essentially, when processes span multiple regional clusters)
docs(home): refresh 0.8.1 breadth — quota, peek/forecast, KV, CLI, config, decorator; 186 ns checkSync
docs: document 0.8.0 stores, adapters, and distributedTokenBudget
Mark GALE Pillars 2-3 and TALE Layers 2-3 shipped (0.7.0) learnedReservation/predictiveReservation and leaseSizer/predictiveLeaseSizer now ship as first-class API. Research.md status markers flipped to Shipped + the shipped-surface paragraph updated; new admission-pacing section on the Overload page; new 'Sizing the lease' subsection on the Distributed page; Home breadth bullet notes the LLM cost-control stack.
Document tokenBudget + provability rebrand (0.6.0)
Add ThrottleKit wiki: guides, distributed model, research
Initialize wiki