Ink - Behavior JIT: turn proven AI decisions into software.

by•
Ink compiles your AI’s proven, repeated decisions into local code that runs in under 0.1 ms. Novel requests still go to your model. Authority is earned from verified outcomes and revoked when behavior drifts. Not a cache. Not a classifier.

Add a comment

Replies

Best
Maker
📌
Production AI agents make the same bounded decisions thousands of times: which tool to call, where to route a ticket, whether to allow an action. Teams pay a frontier model for every one, even after the answer has been verified over and over. Ink is a Behavior JIT. It sits around your existing model call, records decisions and their real outcomes locally, and compiles the behavior that has proven itself into software. Everything else keeps going to your model. What’s different: Permission, not just prediction. A local Fast Path only serves once its 95% Wilson lower bound clears your error budget on independent holdout data. Confidence and similarity never grant authority. Knows when to abstain. Novel or ambiguous requests fall back to your model automatically. Revokes itself. Live comparison traffic keeps auditing, and if error rises, authority goes back to your model. Sub-millisecond, local. Under 0.01 ms for Exact and under 0.1 ms for Linear on local benchmarks, with no network calls and no tokens. Embedded and local-first. Runs in-process on SQLite, with no cloud control plane. pip install ink-jit, Python 3.11–3.13. Honest numbers: in controlled internal evaluations, Fast Paths served 42–78% of traffic with 0.0% holdout error. External design-partner validation is still in progress, and if your workload doesn’t repeat, Ink saves nothing.
How did you use Cloud Run for this launch?
For Ink's launch, we used Google Cloud Run to deploy a containerized demonstration service showcasing Ink's Behavior JIT architecture. Ink observes repeated AI decisions, records verified outcomes, and compiles qualified behavior into sub-millisecond local Fast Paths. Novel or uncertain decisions fall back to the host model. Cloud Run provides the managed environment for demonstrating this workflow through an accessible API, without requiring users to provision their own infrastructure. Ink's core runtime remains open source and can run locally. The Cloud Run deployment acts as a public demonstration and integration endpoint. GitHub: