Understandbeforechanging.
Verifybeforeclaiming.
Testbeforetrusting.
Documentbeforeforgetting.
Eighty-four articles that decide what has to be true before a change ships. The same rules bind the people who work here and the autonomous agents that work alongside them. It is public, it is versioned, and you are welcome to run it on your own repositories.
What it is
The Constitution is the answer to a specific problem: an engineer — or an agent — who is fast, plausible and wrong. Every article closes one route to that outcome.
Every article is a rule someone can be held to. A finished task has to report what was added, changed, removed, preserved and fixed — plus what could still go wrong, what was actually tested, and what was deliberately left undone.
The doctrine was written for autonomous engineering agents, and it is the standard the people here work to. Fabricating command output, test results, file contents, API responses, deployment status, security findings, repository state or tool capabilities is forbidden. If you did not run it, say so.
The Constitution ships as a loadable skill inside ultra-agent, so an agent reads it at the start of substantial work rather than being told about it once and drifting from it by the third file.
Version 1.0, marked Production Specification. Articles get amended deliberately and the version moves with them. Nothing in here is tidied up in passing.
Selected articles
Straight from the specification. The full text of all eighty-four is on GitHub.
On how to describe your own security work:
Never claim something is “100% secure”.
When something cannot be established, it gets labelled rather than smoothed over:
Never convert an inference into a fact.
Nine conditions have to hold before a task counts as finished:
“Code written” does not equal “done.”
Work that reaches past the request has to say so, in the report, at the time:
If solving the requested task requires touching additional systems, explain why. … Do not silently expand scope.
§ 83, Engineering priority order
Not a values statement — a tie-breaker, applied in order. Convenience never outranks data integrity, and no amount of preference moves cosmetics above correctness.
The article ends where it matters: if an explicit user requirement conflicts with a higher-priority concern, explain the conflict instead of silently violating it.
The articles
Grouped into nine parts. Numbers and titles are the specification’s own; the parts are how we read it.
What we've built
Everything public we make lives at github.com/Venoly-BV. Free to use, MIT, no account required.
An autonomous engineering agent stack for Claude Code, built for large repositories. Fourteen specialist subagents, ten skills, three multi-agent workflows, three safety hooks and four repo-scale CLI utilities. The Constitution ships inside it as a loadable skill.
The Venoly Extensible Ignition Loader — a multi-stage x86 bootloader that takes a machine from firmware handoff to a running kernel, on both legacy BIOS and UEFI. It climbs 16 → 32 → 64-bit from a 512-byte MBR, or starts as a PE32+ EFI application, then presents a boot menu, reads a FAT volume, and hands over via the Linux boot protocol, a raw ELF load, or a chainloaded boot sector.
kyc — Kryptonite, an independent proof-of-work chain written from scratch in Rust. Its authors have stopped maintaining it. It is unaudited, not production-ready, and has no market value. Published as an engineering artifact, nothing more.
The people
The copyright line on our repositories reads The Venoly Engineering Constitution, because the document and the group who write it are the same thing.
The same group builds the open tooling above, reviews the Venoly platform against § 18, and competes in capture-the-flag. Security work and engineering work are not separate departments here — the article that governs a security review is in the same document as the one that governs a database migration.
What we have to show is in the repositories.
Engineering or security. Tell us what you have built and what you want to break.
founder@venoly.nlResponsible disclosure has its own page, with scope and safe-harbour terms.
Bug bountyPublic code lives in the organisation. The Venoly platform itself is not open source and does not live there — that split is deliberate and is not up for tidying.
