Mission

The Open Honest Foundation, Inc. is organized exclusively for scientific, literary, and educational purposes within the meaning of Section 501(c)(3) of the Internal Revenue Code. The Foundation conducts pre-registered empirical research on the rigorous measurement and reliable production of verifiable software; conducts and disseminates research on the methodology of empirical inquiry itself; develops and disseminates open educational materials; publishes open technical standards that codify the research; and operates a practitioner certification program that attests to competence in the methodology. Any software, measurement instruments, or computational platforms developed by the Foundation exist as the means by which the research and educational programs are delivered. They are not the Foundation's mission.

The underlying public-interest problem

Software increasingly mediates decisions of public consequence: scientific computing that informs policy, financial systems that allocate capital, healthcare records and clinical decision-support tools, civic infrastructure, voting systems, accessibility platforms, and the regulated-industry workflows on which public welfare depends. The trustworthiness of this software is therefore a matter of public concern. Despite decades of professional practice, software engineering has not developed a rigorous, falsifiable, generally-accepted standard for code quality, and the arrival of AI-assisted code generation at scale has made this measurement gap urgent.

The full public-interest problem has five interrelated layers, each depending on the layer above it being addressed:

1. The absence of rigorous ground-truth measurement. No generally-accepted standard exists for what counts as quality in software, with what construct validity, predicting what deployment-time outcomes.
2. The absence of accessible verification at scale. The volume of AI-generated code requires test automation that a non-expert practitioner can reliably execute and obtain trustworthy results from.
3. The absence of frictionless construction-time verifiability tools. Property-based testing and design-by-contract check behavior; what is missing is construction-time discipline that constrains the structural shape of the code itself, while operating within practitioners' existing programming languages and frameworks.
4. The absence of pristine reference materials. AI code generation is only as good as the codebase from which it works; reference codebases free of structural anti-patterns are a precondition for trustworthy AI-assisted development and currently are not systematically available.
5. The absence of validated prompting strategies. Producing better-than-mediocre code from current AI systems requires prompting strategies grounded in empirical understanding of what training-corpus properties produce capability and how those properties can be steered.

For each layer, four further public-interest gaps are present: no rigorous research establishing the ground-truth evidence, no consensus standards built on that evidence, no technical specification analogous to public-domain standards in adjacent fields (for example, RFC 5322 for the syntax of Internet email messages), and no certification program attesting to practitioner competence.

Scope. The Foundation's first-decade work is on safety-relevant and security-relevant software, including software where AI-generated code introduces structural risks to public welfare, anchored in the established compliance frameworks the Foundation's measurement instrument references. Generalization to broader software-quality questions is a possible future extension contingent on construct validity being achieved end-to-end in the narrower domain first.

What the Foundation does

The Foundation closes this stack of public-interest gaps within its scoped operating domain through four mutually reinforcing programs:

• Scientific research. Pre-registered empirical research deposited on the Open Science Framework with persistent digital identifiers and released through peer-reviewed publication and open-access repositories. See Research for the current portfolio.
• Public education. Open educational curriculum, public-engagement events, invited talks, and accessible explanatory materials addressed to readers without specialized technical background, in service of the public's right to understand the operation and limits of the AI and software systems mediating their lives.
• Open technical standards. Specifications analogous to RFC-class public-domain technical standards, to which software can be written and against which software can be assessed, released under terms permitting any implementer to write conforming software without permission or fee.
• Practitioner certification. A Certified Honest Practitioner credential awarded on the basis of measured competence, open to any practitioner regardless of institutional affiliation, geography, or prior credentials.

These programs are operationalized through three open standards the Foundation governs (Honest Framework, Slop Audit, and MÉTRON) and through cross-traditional scholarly convenings on the methodology of empirical inquiry itself. See Frameworks for the standards and Epistemology for the methodology.

The Foundation's mission profile is shared by many established 501(c)(3) public charities operating in technical-standards development, professional credentialing, and applied scientific research, including the Internet Society (host of the IETF), the Institute of Electrical and Electronics Engineers, the Massachusetts Institute of Technology (host of the W3C), ASTM International, ANSI-affiliated bodies, the Project Management Institute, ISACA, ISC², and the credentialing programs of the American Bar Association sections.

The Foundation does not and will not engage in any substantial lobbying activity within the meaning of Section 501(c)(3), and does not and will not participate or intervene in any political campaign on behalf of or in opposition to any candidate for public office.

The Foundation's role and the two-entity architecture

The Foundation is organized as two distinct legal entities working in concert:

• The Open Honest Foundation, Inc. is the operating 501(c)(3) public-benefit nonprofit. It conducts the research, hosts the educational and certification programs, and publishes the standards.
• The Open Honest Trust is a separate custodial entity that holds the "Open Honest" and "Certified Honest Practitioner" trademarks and exercises the governance custodianship described in the Foundation Charter. The Trust licenses the trademarks to the Foundation under terms set by the Trust; the license is conditioned on the Foundation continuing to operate consistent with its stated charitable purposes and immutable governance provisions, and may be revoked through the procedure specified in the Trust's organizational documents. This revocation power is the structural anti-capture defense for the Foundation's mission.

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 do the research, deliver the educational programs, custodian the standards, run the certification, and keep all four from being captured, watered down, or pulled away from the mission they exist to serve.

Where things stand

Incorporated in Missouri on 2026-05-05 as a public-benefit nonprofit corporation under RSMo Chapter 355. Fiscal sponsorship in process with an established public-interest fiscal sponsor. Federal 501(c)(3) recognition pending (IRS Form 1023 in preparation). The Open Honest Trust is in parallel formation.

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. All of it is at honestframework.software.

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