← Назад към блога

Why Baga? Specs, Effects, and the Age of AI

2026-08-11 16:26:20
The question is not "what is new". The question is "what has not been glued together yet".

Baga was designed with AI-assisted development in mind. When an AI agent generates code, how do you trust it? Baga answers: specs are first-class, effects are visible in types, and the compiler produces human-readable proof sketches.

spec is a keyword — you write the contract before the implementation. The compiler checks the implementation against the spec with --verify. This means both humans and AI agents can understand what a function guarantees without reading its body.

Effects are type dimensions. str !IO !Net tells you this function does I/O and touches the network. You cannot hide side effects. Pure functions are guaranteed to have no observable effects — critical for safe parallel execution and caching.

Readable proof sketches are extracted from code and specs. Unlike Coq or Lean proof objects that require specialized training, Baga proof sketches are designed to be read and understood by any competent programmer.

In the age of AI-generated code, these properties matter. Baga makes trust visible.