VeyaNet Decision Gate

The company appears to be a single-person project named VeyaNet Decision Gate, self-described as a browser prototype for routing AI outputs through human-supervised decision gates (PASS / REVIEW / BLOCK) in high-stakes workflows. The author states this is part of a larger architecture but submitted only a demo version due to hackathon constraints.

What changed: No evidence of prior version or evolution; this is the first public manifestation of the idea as described by the author.

Single most important open question: Is there any evidence of traction, revenue, or customer adoption beyond the prototype? The description makes no claims about actual deployment or usage in real systems.

The description states that VeyaNet Decision Gate is a working browser prototype built with HTML, CSS, JavaScript and deployed via GitHub Pages. It routes AI/system outputs into three outcomes:

• 1 = PASS
• V = REVIEW
• 0 = BLOCK

It accepts scenario signals, normalizes them into a decision packet, calculates a bounded uncertainty score, identifies evidence gaps, and keeps uncertain or unsafe outputs under human review.

Inference: The prototype is not a full system but a demonstration of the core routing logic and UI. It is described as a "supervised routing layer" that does not itself make decisions but determines whether an output should proceed, be reviewed, or be blocked based on uncertainty.

The author states that VeyaNet Decision Gate was inspired by the problem of automated systems producing outputs faster than humans can safely verify them, particularly in clinical, industrial, DevOps, or agentic workflows.

Claim: The system is designed to ensure uncertain outputs do not go straight to action but are routed through a human-supervised gate.

Inference: This suggests a positioning around safety and risk mitigation in AI deployment. It does not claim to be a complete AI governance platform, but rather a decision routing interface for uncertain AI outputs.

The description states that the system is intended for use in high-stakes AI workflows, including clinical, industrial, DevOps, or agentic environments.

Inference: The target customer appears to be organizations deploying AI systems where human oversight is required before action. However, no specific customer names, personas, or market segments are mentioned.

Not evidenced. The description does not mention any pricing model, monetization strategy, or business model.

The project was built as a browser prototype using:

• HTML
• CSS
• JavaScript
• GitHub Pages
• Codex (for code generation)
• GPT-5.6 (for framing and logic)

It is described as a lightweight demo, not a production system.

Inference: The technical stack suggests this is a proof-of-concept, not a scalable or enterprise-grade solution. It was built quickly for a hackathon submission.

Not evidenced. There is no mention of:

• Revenue
• Customers
• Adoption
• Product usage metrics
• Market traction
• Prior versions or iterations

The project is described as a single-person hackathon submission, and the author explicitly states that it is part of a larger architecture but only the final routing gate was exposed.

Not evidenced. No mention of competitors, market landscape, or existing solutions in this space.

• Single-person project: The entire system is built by one individual (AHMET BÜLENT DEMİRBAĞ), raising questions about scalability and long-term maintenance.
• Prototype-only: The system is described as a demo, not a production-ready product. No evidence of real-world deployment or integration.
• No commercial traction: No evidence of revenue, customers, or adoption beyond the prototype.
• Unverified safety claims: The system is explicitly stated to be not a clinical diagnostic device or factory controller, but it is unclear how it would integrate into such systems in practice.

1. What is the actual architecture of the larger VeyaNet system? Is this just a UI layer?
2. Has the prototype been tested or validated in any real-world environment?
3. Are there plans to move beyond the demo into production use cases?
4. How does this integrate with existing AI systems or workflows?
5. What is the roadmap for scaling this beyond a single-person project?