OpenAI 2026 hackathon

Ños: Clinical-Symbolic System for Psychological Support

An AI system for structured, adaptive psychological support, combining clinical reasoning, symbolic narrative, contextual analysis, and safety-aware responses while preserving user agency.

Solo project by Yohann Naciff García Marcial · 0 likes · 0 comments

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 #5,596 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

Ños is a self-described AI system for psychological support, built around a modular clinical-symbolic architecture that integrates symbolic interpretation, narrative analysis, emotional regulation principles, and trauma-aware perspectives. It uses language models as reasoning engines but enforces structured retrieval of evidence from internal document families before generating responses.

What changed

The project evolved from an experimental Custom GPT into a publicly accessible web demonstration using the OpenAI API, with a focus on operational discipline, safety protocols, and architectural consistency. The author notes that earlier unstable versions were incorporated into the design rather than discarded.

Single most important open question — the commercial due-diligence read

Is there any evidence of real-world usage, user feedback, or clinical validation beyond the author's own development process? The description states no revenue, customers, or traction data exist; all claims are self-reported and unverified.

Back to contents

What The Product Actually Is

The description states that Ños is a clinical-symbolic architecture for psychological support. It is implemented through a language model but not defined by a single model. Its purpose is to help users examine what they are experiencing, recognize internal patterns, preserve autonomy, and identify a proportionate next step.

It supports situations ranging from everyday uncertainty to interpersonal conflict and complex distress, without diagnosing or prescribing treatment. The system uses a modular architecture integrating symbolic interpretation, cognitive/emotional pattern recognition, functional conversational modes, trauma-aware perspectives, emotional regulation principles, metacognitive examination, contextual analysis, and proportional responses.

The language model is the reasoning engine; the architecture determines how that reasoning is organized, questioned, calibrated, and expressed.

Evidence

  • The author describes it as a "clinical-symbolic architecture for unconventional psychological support"
  • It integrates multiple domains: symbolic interpretation, emotional regulation, trauma awareness, metacognition
  • It uses a modular design with specific components like “functional masks,” “resolved expert-inspired cases,” and “Ños functions”
  • Responses are governed by a pipeline that retrieves evidence from internal documents before invoking the model

Inference The system is not a general-purpose chatbot but a specialized tool built for psychological orientation, with emphasis on safety, context, and user agency.

Back to contents

Positioning & Claim Evolution

The author positions Ños as an AI system designed to offer serious orientation to people who want to move forward but do not currently have sufficient psychological support, and to become a useful complement when professional care is available.

It is not built around the promise of “saving everyone.” Instead, it commits to offering humanity without pretending to possess certainty. It avoids replacing psychologists or diagnosing conditions, focusing instead on helping users examine their experiences and find next steps.

The author also notes that Ños was initially developed as a private experimental GPT before being transformed into an API-based system with public-facing demonstrations.

Evidence

  • “It is built around a more honest commitment: to offer serious orientation...”
  • “It is not built around the promise of 'saving everyone.' It is built around a more honest commitment...”
  • “It is designed to help users examine what they are experiencing, recognize internal patterns, preserve autonomy, and identify a proportionate next step.”
  • “The goal is not to build an artificial therapist that claims to have every answer. The goal is to build a structure capable of staying with the question long enough to help a person find a real next step.”

Inference This positioning reflects an attempt to differentiate Ños from typical AI chatbots by emphasizing ethical restraint, clinical grounding, and user-centeredness.

Back to contents

Target Customer & ICP

The description states that Ños is intended for people who seek psychological support but cannot access a psychologist due to cost, distance, fear, family circumstances, or lack of support. It aims to help those who want to move forward but do not currently have sufficient psychological support—and to become a useful complement when professional care is available.

The system does not target individuals seeking diagnosis or treatment; rather, it supports people navigating emotional organization, difficult decisions, interpersonal conflict, and uncertainty.

Evidence

  • “Many people seek help but cannot access a psychologist when they need one—because of cost, distance, fear, family circumstances, or simple absence of support.”
  • “Its purpose is not to diagnose, prescribe treatment, or replace psychologists.”
  • “It is designed to help users examine what they are experiencing...”

Inference The ICP likely includes individuals in distress who are looking for orientation and support but may not be able to afford or access traditional therapy. The system is positioned as a bridge between self-help and professional care.

Back to contents

Business Model & Pricing Evidence

There is no evidence of any business model, pricing structure, monetization strategy, or revenue streams described in the project write-up.

Evidence

  • No mention of subscriptions, usage fees, partnerships, or sales channels.
  • No indication of how the system would be offered commercially.
  • The author states that this is a demonstration for OpenAI Build Week and not a finished product.

Inference The business model remains undefined. Any commercialization path has yet to be articulated.

Back to contents

Technical & Delivery Signals

The system was built iteratively using GPT-4o, GPT-4.5, Gemini 2.5 Pro, and stable versions of Ños itself. The architecture includes:

  • A modular design with document families (e.g., “resolved expert-inspired cases,” “functional masks”)
  • Mandatory retrieval from vector stores before model invocation
  • Model selection based on complexity
  • Server-side secret protection
  • Session limits and cost controls
  • Parallel search execution for efficiency
  • Structured generation for evaluation

The current version is Ños 1.2.5, with a planned mobile app release (Ños 1.3).

Evidence

  • “I worked with GPT-4o, GPT-4.5, Gemini 2.5 Pro, and stable versions of Ños itself.”
  • “The server retrieves evidence from: Ños Functions; Functional Masks; resolved expert-inspired cases; unresolved or failed expert-inspired cases.”
  • “Model selection based on conversational complexity”
  • “Server-side secret protection”
  • “Session limits and cost controls”

Inference There is a clear technical evolution, with emphasis on operational discipline, retrieval enforcement, and architectural consistency. The system appears designed to be scalable and secure.

Back to contents

Traction & Maturity Signals

The description contains no evidence of user adoption, customer base, or real-world usage beyond the author’s own development process.

Evidence

  • No mention of users, customers, or feedback.
  • No revenue data, ARR, or headcount.
  • The system is described as a demonstration for a hackathon and not yet a product.

Inference There is no traction. The project remains in early-stage development, with only internal testing and synthetic evaluations conducted.

Back to contents

Competitive Context

The description does not provide any information about competitors or market positioning relative to existing tools in the mental health AI space.

Evidence

  • No mention of competing products.
  • No comparison to other AI-based psychological support systems.
  • No indication of how Ños would differentiate itself from similar offerings.

Inference The competitive landscape is unknown. The author does not reference or analyze existing solutions, leaving open questions about differentiation and market relevance.

Back to contents

Key Risks & Red Flags

Several risks and red flags emerge from the self-reported description:

  1. Lack of clinical validation: No evidence of peer review, testing with real users, or professional oversight.
  2. Unverified claims: All statements are self-reported; there is no independent verification.
  3. No commercial viability: No business model, pricing, or monetization strategy described.
  4. Limited scalability concerns: The system uses expensive API calls and parallel retrieval, which may not be sustainable at scale.
  5. Single-person development: Only one developer (Yohann Naciff García Marcial) is mentioned, raising questions about long-term maintenance and growth.

Evidence

  • “No revenue, customer or traction data is available beyond what they state.”
  • “The system does not claim to be clinically validated.”
  • “Only one person worked on it.”

Inference The project lacks external validation, commercial readiness, and scalability planning. It remains a prototype with no clear path to productization.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the basis for your clinical-symbolic architecture? Is there any peer-reviewed research or expert input?
  2. How do you plan to ensure safety and ethical compliance without clinical oversight?
  3. Are there any plans for independent professional review or regulatory compliance?
  4. What are the key metrics you use to evaluate performance beyond synthetic cases?
  5. How will you scale the system while maintaining its operational discipline and cost efficiency?
  6. What is your roadmap for monetization, if any?
  7. Have you considered how to integrate Ños with existing mental health services or platforms?

Back to contents

Investment/Partnership Verdict

Not evidenced.

There is no evidence of revenue, ARR, funding rounds, headcount, customer names, or adoption data. The project is described as a demonstration for an OpenAI hackathon and not yet a product.

The author states that Ños is already a functioning system but not presented as a finished clinical product. It shows architecture, operational discipline, limitations, and direction for growth—but no traction, customers, or commercial viability.

Confidence level Low This analysis is based entirely on self-reported information, with no external corroboration or evidence of real-world impact.

Back to contents

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.