open source
Read every decision. Test every change.
The runtime, playground, documentation, and design reasoning live together. Inspect the implementation, run the same checks as CI, and contribute under Apache-2.0.
what a change has to pass
The build gate.
Lint, format, strict types, an import linter that keeps dependencies pointing inward, and three test layers that run as separate CI jobs so a failure names the layer. Contributions run the same commands locally.
Store tests run against real PostgreSQL, MySQL and DynamoDB, which CI starts as service containers. No store is mocked, and no test calls a model provider or any other outside service. A feature with no end-to-end case asserting its behaviour is not done, whatever the line coverage says.
The docs are part of it. The reference is generated from the module and the pages are copied from the repository, so the build fails on a diff rather than letting a page fall behind the code.
for coding agents
Twenty-six skills, one per feature.
Written for an agent that has never seen the codebase: the mental model, the vocabulary, the invariants that get a change rejected, and the working code. They are the same files the documentation guides are generated from, so there is one copy and it is the tested one.
status
Pre-alpha, at 0.x.
The public API still changes between minor releases. Breaking changes go in the changelog in the commit that makes them true.
A name scheduled for removal ships at least one minor release emitting a DeprecationWarning that names its replacement, so deprecated in 0.N means removed no earlier than 0.N+2. Security fixes are the exception. The full policy is in CONTRIBUTING.md.