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
Human direction. AI execution.
Over the last months, AI wrote hundreds of thousands of lines across real systems projects, guided and reviewed by one human.
The work exposed a recurring problem: AI could write C quickly, but too much attention went to bounds, nulls, overflow, allocation and cleanup instead of the logic that made the program useful.
Each hard-earned lesson became a constraint, primitive, audit rule or clearer CLI contract inside one deep module. The result is not a prompt or a style guide. It is an executable boundary that carries the experience forward.
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 tree waits through dry conditions and then breaks into a canopy of yellow. Its name carries kibra, “to break,” and hacha, “axe.” 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.