You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stumbling Toward a Formally Verified 9P: a big-picture tour of formal verification with TLA+, for testing 9P implementations deeper than a finite test suite. By Adam (rndmcnlly), via a Claude Opus agent on Lathe.
Stumbling Toward a Formally Verified 9P: A Field Guide for Joël
2026-06-15T05:30:34Z by Showboat 0.6.1
Who, what, why. Hi Joël — Adam here. Well, sort of Adam. The words below were
assembled by a Claude Opus-based agent running on
Lathe inside Open WebUI,
while the real Adam loaded the dishwasher and supervised from his phone. (He'd like it noted
that the forks are now sorted. So are the bytes.)
Empirical test: OpenRouter 1h cache TTL -- prompt_cache_ttl vs cache_control.ttl
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Open WebUI tool pattern: self-registering FastAPI routes (insert before SPAStaticFiles catch-all)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
description: Reference pattern for Open WebUI tools that register their own FastAPI endpoints. Demonstrates idempotent route injection before the SPA catch-all, version-stamped dedup, and lazy init.
Anyone operating an LLM inference API with API key authentication -- whether a direct provider or an aggregator -- should consider supporting scoped JWT tokens. DeepInfra already does this well. The pattern is general and solves real problems that the rest of the industry is working around with proxies and key management sprawl.
The problem
Organizations that distribute LLM API access to their users (universities, SaaS platforms, dev teams) currently have two options:
Give each user a real API key via a management API. This works, but the organization loses control the moment the key leaves their hands. Keys can be shared, leaked, or used in ways the organization didn't intend. Revoking a key often destroys its analytics history. And provisioning keys is a heavyweight operation -- there's no cheap way to issue thousands of ephemeral credentials.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mixed-initiative synthesis of lock and key gridworlds
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It started as a procedural audio vibe test, but then things got weird.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters