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,027 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
The description states that f1ghtback is a browser-based tool designed to help self-represented individuals navigate family court processes in California and Utah. The author, Faith Atwater-Cheltenham, describes it as built from lived experience navigating family court overload. It provides guided walkthroughs for specific forms (FL-320 in California and answer preparation in Utah), with a focus on preserving user language and not collecting personal data. The tool uses AI to explain steps but does not store or transmit personal answers. It is presented as a hackathon submission, with no evidence of revenue, customers, or traction beyond the author's own account.
Key open question
What is the actual commercial viability or scalability of this product, given that it appears to be built for a very narrow use case and lacks any demonstrated market traction?
What The Product Actually Is
The description states that f1ghtback is a browser-based tool designed to help self-represented individuals prepare responses in family court. It offers two guided walkthroughs: one for California FL-320 response preparation and another for Utah family answer preparation.
It provides:
- A source-backed router that turns three non-personal choices into one next action
- A short checklist, focused review questions, and official links
- Two form-matched, one-question-at-a-time response coaches
- Browser-side PDF/text packet generation
- No account creation, uploads, or data persistence
The tool is described as using Next.js, React, TypeScript, OpenAI Sites, Cloudflare Workers, D1, pdf-lib, and the OpenAI Responses API. It uses GPT-5.6 optionally for explanations but does not send personal answers to the AI.
Positioning & Claim Evolution
The description states that f1ghtback was built by a Black mother and disabled technologist from lived experience navigating family court overload. The goal is described as helping someone reach one contained next step, preserve their own language, and arrive at human review better prepared.
It positions itself as:
- Not letting a model choose forms or decide what is legally sufficient
- Helping users reach one next step
- Preserving user language
- Arriving at human review better prepared
The author claims it does not provide legal advice, file papers, or create an attorney-client relationship. It is described as a tool for self-represented individuals to prepare responses in family court.
Target Customer & ICP
The description states that f1ghtback is designed for self-represented individuals navigating family court processes, particularly those facing urgent timing, disability barriers, unfamiliar forms, and information overload.
It targets:
- Self-represented individuals in family court
- People with disabilities who face barriers to understanding court forms
- Individuals who need help preparing responses to court papers
The tool is specifically designed for users in California and Utah, with walkthroughs for FL-320 response preparation and Utah family answer preparation.
Business Model & Pricing Evidence
Not evidenced. The description does not mention any pricing model or business model beyond the fact that it's a hackathon submission.
Technical & Delivery Signals
The description states that f1ghtback uses:
- Next.js, React, TypeScript
- OpenAI Sites, Cloudflare Workers, D1
- pdf-lib and the OpenAI Responses API
- GPT-5.6 for optional explanations (but not for processing personal answers)
- vinext framework
- Codex for system inspection, schema building, and QA
Key technical features include:
- Personal answers remain in React memory
- Model calls accept bounded IDs only
- Packets are generated on-device
- Jurisdictions remain separated
- Stale sources fail closed
- Every output calls for human review
- No account, upload, case database, analytics, or answer persistence
Traction & Maturity Signals
Not evidenced. The description states that this is a hackathon submission and does not provide any information about revenue, customers, or adoption beyond the author's own account.
Competitive Context
Not evidenced. The description does not mention any competitors or competitive landscape.
Key Risks & Red Flags
- The tool is described as a hackathon submission with no demonstrated traction or commercial viability
- It appears to be built for a very narrow use case (family court in California and Utah)
- No evidence of revenue, customers, or market validation
- The author states that it does not provide legal advice, file papers, or create an attorney-client relationship, which may limit its utility or liability exposure
- The tool is described as not storing personal data, but the description doesn't clarify how this affects its ability to provide meaningful assistance
Diligence Questions To Ask The Founders
- What is the actual market size for self-represented individuals in family court across different jurisdictions?
- How does the team plan to validate demand beyond the author's own experience?
- What are the legal implications of providing a tool that helps with court filings but doesn't provide legal advice?
- How will the team ensure that the source information remains current and accurate?
- What is the long-term vision for scaling this beyond California and Utah?
- How does the team plan to monetize or sustain this product if it's not generating revenue currently?
Investment/Partnership Verdict
Not evidenced. The description provides no information about funding, valuation, or any investment or partnership opportunities. This appears to be a hackathon submission with no commercial traction or evidence of a scalable business model.
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.