// readme

PAI Knowledge OS

Measured, not claimed. The design choices in PAI come out of a series of lab reports, published with DOIs: PAI Reports (doi:10.5281/zenodo.24274093). The latest, Planner and Worker (doi:10.5281/zenodo.24274754), shows when a cloud planner over a local coder pays off: a local model alone handles small changes for free; on larger multi-file work a Sonnet planner over a local worker matches Sonnet alone at about a third less cloud cost. That is what pai worker mode speed|balanced|budget switches between.

Local AI used to be hard. Now it is a button.

I have spent a long time on local AI. Getting a strong model to run on my own machine was the easy part; making it actually useful was not. Which server, which quantization, which port, how to keep it alive, how to send it only the work it can do, and how to fall back to the cloud when it cannot. Every piece worked on its own and none of them worked together.

PAI is what came out of that, and I am giving it to the community. A MacBook can already run a serious model: on…