Skip to content
Sprint projectMay 24, 2026Kenya

Project Verify

Ray Munene · Team Verify

Submitted to The Secure Program Synthesis Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

Project Verify is a Secure Program Synthesis Hackathon project that turns code, documentation, and requirements into structured formal specifications using multiple LLMs (Claude, GPT-4o, and Gemini). It extracts preconditions, postconditions, invariants, assumptions, and testable properties, then compares outputs across models to identify disagreements and synthesize a consensus specification. The system is designed as a client-side React application where API keys are optionally provided per model, with no persistent storage of credentials. Its long-term goal is to evolve into a privacy-preserving edge-native library for running multi-model orchestration securely without centralized handling of sensitive keys.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. This project's write-up contains the most convincing plan for a useful tool among entrants I've read so far. However, it also kind of promises the world in terms of what will be done to compare answers from different LLMs.

    As far as I can tell, not only is the report vague on how to make any kind of useful comparison across LLM answers, but the code base itself contains zero functionality of that kind. It looks like the GitHub repo is very close to just containing a project template for React or something. There is a little bit in there that I could believe queries LLMs asking for specific kinds of information, but I don't see where anything useful could be accomplished with that information.

  2. The concept is relevant and the architecture is sensible: per-model elicitation, a cross-model consensus pass, a confidence rating, all client-side with strict JSON. The write-up is clear, too. But this is a system description, not a piece of research: there is no benchmark, no experiment, no worked example, and no baseline anywhere in it. The central claim, that cross-model comparison surfaces underspecification, is asserted but never tested, so there is no way to judge whether the consensus step works or whether disagreement tracks real spec gaps. That absence caps execution and impact regardless of how clean the design is. The path forward is concrete: run one evaluation on even ten known-ambiguous specs, show two or three real disagreements end to end, and validate what the confidence number is actually measuring. The foundation is reasonable; it needs an empirical core before any of its claims can be assessed.

    Read full reviewShow less

Cite this project

@misc{munene2026project,
  title = {{Project Verify}},
  author = {Ray Munene},
  year = {2026},
  month = may,
  note = {Submitted to The Secure Program Synthesis Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/project-verify-9j1k}},
  url = {https://apartresearch.com/sprints/projects/project-verify-9j1k}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026