CodeGnosis

Company: CodeGnosis

Self-reported basis: The description is entirely self-reported and unverified, based on a Devpost submission for the OpenAI 2026 hackathon. No third-party verification, revenue, customer data or traction evidence is available.

What it appears to be: A developer tool that performs local, read-only analysis of codebases and presents dependency relationships in two formats: an interactive "galaxy" for humans and a structured JSON export for AI systems. It claims to provide one canonical model shared between human and AI users, with emphasis on truthfulness, evidence, and structural context.

What changed: The project was rebuilt from a failed prototype during OpenAI Build Week, focusing on creating a single, truthful structural model that both humans and AI can access without contradiction.

Single most important open question: Is there any evidence of real-world usage or adoption beyond the hackathon prototype? The description states no revenue, customers or traction data exist.

The description states that CodeGnosis:

• Scans a project locally and read-only
• Resolves real dependency relationships
• Creates one canonical evidence-bearing model
• Provides an explorable galaxy for humans with guided investigations, dependency paths, entry points, loops, unresolved references, Gravity, Blast, Drift candidates, uncertainty, and line-level evidence
• Provides an AI export in complete versioned JSON containing files, relationships, diagnostics, evidence, exclusions, completeness, hashes, and bounded source context
• Offers a printable human report
• Includes configurable privacy exclusions remembered per project
• Contains a Vault with plain-language definitions, the public lexicon of Another, and the Law of the Living ethical base
• Reports evidence and limitations instead of inventing a universal health score

Inference: The product appears to be a code analysis tool that attempts to reconcile human understanding and AI interpretation through a shared structural model. It is built with React, Python, JavaScript, and integrates with GPT-5.6.

The description states:

• CodeGnosis began as an ambitious prototype assembled by four AI collaborators working without one shared domain model
• The vision was to let a human and an AI understand the same codebase in their own native languages
• The architecture drifted out of sync, leading to contradictions and false health scores
• For OpenAI Build Week, they recovered the original vision and rebuilt it around one truthful structural model

Inference: The positioning evolved from a multi-AI collaboration with unclear alignment into a single, unified model approach. The claim is that this model is more accurate than previous attempts, and that it avoids false health scores by reporting evidence and limitations.

The description does not state who the target customer or ideal customer profile (ICP) is.

Not evidenced: No mention of specific user roles, industries, or use cases beyond general developer tooling.

The description does not provide any information about:

• Revenue model
• Pricing structure
• Monetization strategy
• Customer acquisition plan

Not evidenced: No evidence of business model or pricing in the self-reported description.

The description states:

• Built with React, Python, JavaScript, GPT-5.6, and other technologies
• The Build Week rebuild was authored in one primary Codex session using GPT-5.6
• Codex helped recover architecture, define domain contract, build analyzer and interface, create adversarial fixtures, construct privacy barriers, and verify system
• Veris (operating through Claude Code CLI) served as independent architecture challenger and Key-2 auditor
• The analyzer produces evidence-backed dependency relationships across major language families
• It identifies real cycles and supported entry points
• Records exclusions and completeness
• Packages bounded source context without writing into the analyzed project

Inference: The tool is built using AI-assisted development, with a focus on correctness and privacy. It uses local-first principles and integrates with AI models for analysis.

The description states:

• This was submitted to the OpenAI 2026 hackathon
• It was rebuilt from a failed prototype during Build Week
• The team size is one (Timothy Drake)
• No revenue, customer or traction data is available beyond what they state

Not evidenced: No evidence of real-world usage, adoption, or product maturity beyond the hackathon submission.

The description does not mention any competitors or competitive landscape.

Not evidenced: No information about existing tools or market positioning.

• The project is described as a hackathon prototype with no verified traction or revenue
• The team size is one (Timothy Drake)
• The product claims to be built using AI-assisted development, but there's no evidence of how this scales or how it compares to traditional code analysis tools
• No mention of privacy compliance, security, or scalability beyond local-first principles
• The description makes strong claims about truthfulness and shared models, but lacks any validation or testing data

Inference: The lack of traction, revenue, or customer feedback indicates a high risk that the product has not yet proven its value in real-world usage.

1. What is the current status of CodeGnosis beyond the hackathon prototype?
2. Have you tested the tool with real codebases from developers or organizations?
3. How do you plan to scale this product beyond a single developer’s use case?
4. What are your plans for monetization and customer acquisition?
5. Can you demonstrate how the shared model approach improves collaboration between humans and AI in practice?
6. How do you ensure that the tool remains accurate as codebases grow and change over time?