Mission

The Open Honest Foundation advances one principle: that a system's structure should make its correctness verifiable. The Foundation governs three open standards applying that principle to software, to compliance measurement, and to cross-linguistic intelligence research.

The problem

Almost all real software is written in object-oriented languages like Python, Java, JavaScript, and C#. In these languages, you cannot test every possible state your program can be in. There are too many. The number of possible states grows faster than any test suite can keep up with.

Tests only check the cases you write. They do not check the cases you did not think of. The cases you did not think of are where the bugs hide.

This is not a problem you can fix by being more careful or writing more tests. It is built into how the language works. And it affects most of the software the world depends on: scientific code (climate models, physics simulations, AI systems), financial systems, healthcare records, civic infrastructure, security tools, voting systems, accessibility software, and anything else where correctness matters.

When people trust this software more than the language can support, things go wrong.

The Honest answer

The Honest Framework is a specification — a set of rules, patterns, and conformance requirements — for writing code that is correct by design. It is language-agnostic. Any object-oriented or imperative language can implement it: Python, JavaScript, TypeScript, Java, Go, C#, Ruby, and others. You stay in the language you already use.

In most cases you can also keep the application framework you already use within that language: Rails in Ruby, Django or FastAPI in Python, Spring in Java, Express in Node, ASP.NET in C#. Honest layers on top of these, not in place of them. You do not have to rewrite your application to start using it.

You do not need to learn a new language. You do not need exotic type systems, dependent types, or any of the other complex tools that have kept this kind of correctness stuck in academic languages like Haskell, Idris, or Coq.

Checking the code is part of the specification, not something you bolt on later. You verify Honest programs by reading their structure, not by writing endless tests against situations you can never fully cover.

The Foundation's role

Open Honest Foundation exists to protect the Honest open standards. It does this by holding the trademarks, enforcing the Code of Conduct, hearing appeals, keeping a public record of what gets enforced, and choosing its own future trustees.

The Foundation does not decide what goes into the code. That is the job of the maintainers and working groups. The Foundation's job is to keep the standards from being captured, watered down, or pulled away from the mission they exist to serve.

The Foundation is small on purpose. Its scope is narrow. Many of its rules cannot be changed by any future vote, by any commercial licensee, or by any governance body, including the trustees themselves. This is what stops the Foundation from being captured by the very forces it exists to protect against.

Where things stand

The Foundation is in its bootstrap phase. The Honest specification is structurally complete and stable: substantial Markdown documentation across the framework, a formal conformance suite of approximately 50 laws across 7 modules, and the Slop Audit methodology covering 18 compliance-mapped dimensions. The Python reference implementation is in active development; reference implementations in JavaScript, Ruby, and other languages will follow. The conformance suite is the contract any new implementation must satisfy. All of it is at honestframework.software. The Foundation is being set up to accelerate adoption and the additional language implementations.

The Foundation is built to keep running long after the bootstrap funding is gone.