This is not a polished, commercial product. It is a living, breathing capability-graph language. If you use it to manage your production infrastructure, you accept the risk of the "frontier." Expect breaking changes, experimental syntax, and the occasional requirement to debug the compiler itself.
Vaked empowers agents with eBPF-level and filesystem-level capabilities.
By nature, an autonomous agentic system can — and eventually will — perform
actions you did not anticipate. We have built-in budget and
ebpf controls to limit this, but you remain the ultimate operator.
Review your capability graphs before compilation.
Vaked aims to make your agents more honest by enforcing constraints, but it cannot fix the fundamental probabilistic nature of the LLMs themselves. Use this tool to contain the models, not to assume they are flawless.
The language grammar, type system, compiler IR, and wire protocol are under active design. Breaking changes happen without notice. There is no stable release. There is no package manager install. There is no conventional OS support.
This project reflects a specific philosophy of systems engineering: local-first, privacy-oriented, deterministic, and honest. It may not align with "cloud-native" or "turn-key" methodologies. The project was born on the road, built in the chaos of mobile studios and intermittent connections.
Vaked's type system provides compile-time verification of the Principle of Least Privilege (POLA). It does not handle runtime enforcement, secrets management, or OS/hypervisor exploits. See the security policy for details.
This is a research project under active development. If you find a security issue, please report it privately. See the security policy for contact information.