Archive position — measured, not model output
0 likes on Devpost
2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #4,011 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
Exhibit A is described as an “evidence engine for code that is only allowed to speak with proof.” The project was submitted to the OpenAI 2026 hackathon and is built by a single founder, Suryansh Sijwali. It uses AI tools including GPT-5.6, Codex, and LLMs, along with technologies like Next.js, React, Python, and GitHub Actions.
What changed
There is no evidence of prior version or evolution — this is a self-reported project submitted as part of a hackathon.
The single most important open question
Is there any indication of commercial traction, customer feedback, or product-market fit beyond the hackathon submission?
What The Product Actually Is
The description states: “An evidence engine for code that is only allowed to speak with proof.” This suggests a tool focused on generating, validating, or managing evidence related to software code — likely in the context of automated testing, code review, or compliance.
Evidence
- The tagline and project name imply a product centered on code-based proof.
- Technology stack includes AI tools (GPT-5.6, LLMs), CI/CD (GitHub Actions), and frontend/backend frameworks (Next.js, React, Python).
- The author declares the use of automated testing tools (pytest, vitest), linting (ruff), and containerization (Docker).
Inference The product likely integrates AI to support code validation or documentation, possibly within a development workflow.
Positioning & Claim Evolution
The description states: “An evidence engine for code that is only allowed to speak with proof.”
Evidence
- The tagline is the only claim made about positioning.
- No prior versions, marketing materials, or evolution of claims are provided.
Inference This may be a new concept or a rebranding of an idea, but there is no evidence of how it has evolved or what it was previously called.
Target Customer & ICP
The description does not state who the target customer is or what the ideal customer profile (ICP) might be.
Evidence
- No mention of specific users, roles, or industries.
- The technology stack suggests a developer-oriented tool.
Inference It may be aimed at developers or engineering teams looking to automate code validation or documentation, but this is speculative without further evidence.
Business Model & Pricing Evidence
There is no information in the description about pricing, monetization, or business model.
Evidence
- No mention of revenue streams.
- No pricing structure or commercial offering described.
Inference If it’s a hackathon project, it may not yet have a defined business model — but this cannot be confirmed from the provided information.
Technical & Delivery Signals
The author declares that the product was built with:
- AI tools (GPT-5.6, Codex, LLMs)
- Development frameworks (Next.js, React, Python)
- CI/CD (GitHub Actions)
- Testing tools (pytest, vitest)
- Infrastructure (Docker, Tailwind CSS)
Evidence
- The author lists these technologies as part of the build.
Inference The tool likely integrates AI into a modern development workflow and may be delivered via web or API. However, no information on delivery mechanism or architecture is provided.
Traction & Maturity Signals
There is no evidence of traction, adoption, or maturity beyond the hackathon submission.
Evidence
- The project was submitted to a hackathon.
- No mention of users, customers, or product usage.
- No prior versions or iterations are described.
Inference This is likely an early-stage prototype or proof-of-concept, not yet validated in the market.
Competitive Context
There is no evidence of competitive analysis or positioning against existing tools.
Evidence
- No mention of competitors.
- No indication of how this product relates to existing code review, testing, or AI-assisted development tools.
Inference It may be positioned within a space such as AI-powered code review or automated testing, but no evidence supports this.
Key Risks & Red Flags
Risk 1
The project is described only in a hackathon submission — no commercial traction or validation.
Risk 2
Single-founder team with no prior track record or team structure.
Risk 3
No clarity on business model, pricing, or target customer — all critical for commercial viability.
Risk 4
The tagline is abstract and not clearly actionable — may indicate a lack of focus or definition.
Diligence Questions To Ask The Founders
- What specific problem does Exhibit A solve in code development workflows?
- How does it differ from existing tools like GitHub Copilot, CodeGuru, or automated testing platforms?
- Is there any user feedback or early adoption beyond the hackathon?
- What is the intended business model and monetization strategy?
- What are the next steps for product development and market entry?
Investment/Partnership Verdict
Verdict Not evidenced.
Confidence Level Low — this is a self-reported, unverified, hackathon submission with no evidence of traction, customers, or business model.
Reasoning
The description provides no commercial signals. It is unclear whether this project has moved beyond the prototype stage or has any real-world application. The lack of data on users, revenue, or product-market fit makes it impossible to assess its viability for investment or partnership.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.
The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.