Constrain
Bounded iteration, checked arithmetic, explicit absence, region-managed memory and a narrow API catalog replace broad, ambient access to C and libc.
A systems dialect made for AI
Kibrahacha constrains the dangerous surface of C and gives AI a small, explicit vocabulary for writing fast systems software.
Discover KibrahachaBuilt in Curaçao
The idea came first. Practice raised the bar.
We began with a realization: AI models work better within enforced constraints—and every constraint a programming language can enforce is ultimately formal in nature.
A constraint must be expressible as a rule the toolchain can evaluate, rather than advice the model must remember. That led us to experiment with a small set of purpose-built C primitives whose individual contracts we could verify with Frama-C.
With a tiny core, we built a Minsky machine, demonstrating that a tightly constrained vocabulary could still express general computation. From there, we guided state-of-the-art AI models through increasingly demanding projects, producing hundreds of thousands of lines and adding primitives only when real workloads justified them.
Kibrahacha is the resulting deep module: the accumulated constraints, evidence, interfaces and lessons needed to let AI focus on the program’s logic.
Safety by subtraction
Bounded iteration, checked arithmetic, explicit absence, region-managed memory and a narrow API catalog replace broad, ambient access to C and libc.
Core primitives carry explicit Frama-C WP/RTE evidence. Source, generated C and link closure are audited without pretending that composition proves the whole application.
One native CLI teaches the language, exposes every API and contract, builds portable C99, and course-corrects mistakes before they become architecture.
The honest boundary
Mechanical, unforgiving work: source restrictions, bounded control flow, numeric contracts, memory identities, API discovery, generated-code invariants and reproducible closure.
Functional correctness, protocol decisions, security policy, constant-time reasoning and whole-system behavior still require engineering evidence. Kibrahacha states those nonclaims.
Start with the clear safe implementation, measure it, then isolate only the proven bottleneck as a narrow C99 hotpath. Performance exceptions stay explicit instead of spreading through the program.
Once an AI learns the four core patterns and searchable API, it stops spending iterations rediscovering defensive C. Attention returns to design—and useful code often arrives in one pass.
The name
Kibrahacha
Curaçao’s kibrahacha trees wait through dry conditions, then break into canopies of flowers. For a few magical days, they turn parts of our beautiful island a stunning yellow. Kibrahacha means “axe-breaker”—a name earned by wood hard enough to live up to it. It is a fitting name for a tool built to break old classes of software failure, and for work rooted on the island where it was made.
0.1.0 is taking root
Kibrahacha, Kibra TLS and Kibra Webserver are being prepared for public release together. The first live reference stack is already serving at kibrahacha.dev.
Dependencies: a C compiler.