Archive position — measured, not model output
0 likes on Devpost
2,263 of the 7,850 archived projects have more likes, and 5,587 share exactly 0 — so this project's #6,918 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,587 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 284 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
User Stories BotA demo video on every pull request
Get a demo video on every new feature
GitHub App that watches your pull requests and records a narrated, captioned demo.
Save time on demo prep and make informed decisions faster with a video walkthrough of every new feature.
Executive Summary
SPS Design DNA is a self-reported system for landscape design projects that claims to structure scattered project intake into an immutable, traceable "Design DNA" using AI and evidence-based workflows. The author states it was built as a Laravel backend with PHP and MySQL, incorporating OpenAI Codex for development assistance. It includes features like evidence intake, classification, immutable snapshot sealing, and AI-generated Design DNA claims tied to verified sources.
The system is described as provider-neutral, with strict validation rules and atomic generation lifecycle management. The author notes that the project was submitted to the OpenAI 2026 hackathon and has not yet reached production or customer traction.
Key open question
What evidence supports the claim that this system will be adopted by landscape designers, and how does it differentiate from existing tools in the market?
What The Product Actually Is
The description states that SPS Design DNA is an "evidence-first system for landscape design projects." It collects, reviews, classifies, and seals project evidence into immutable snapshots. These snapshots are then used to generate a structured "Design DNA" containing:
- Site conditions
- Requested changes
- Items to preserve or remove
- Material and style direction
- Planting direction
- Functional requirements
- Assumptions, unknowns, and conflicts
- Adaptive follow-up questions
- Evidence citations
The system is described as preventing unsupported AI statements from becoming project facts by requiring claims to cite verified evidence or be marked as assumptions.
Inference The system appears to be a backend workflow tool for organizing design project intake and generating structured outputs using AI, with emphasis on traceability and integrity of information.
Positioning & Claim Evolution
The author states that SPS Design DNA was created to turn "scattered intake" into a "structured, traceable source of truth." It positions itself as an evidence-first approach to landscape design project management.
It claims to be:
- An immutable system for managing design project information
- Provider-neutral in its AI integration
- Designed to prevent unsupported AI statements from becoming facts
- A tool that links AI-generated claims to verified evidence
Inference The positioning is evolving from a hackathon prototype into a potential production-grade workflow tool, but the description does not indicate any prior market traction or adoption.
Target Customer & ICP
The author states that SPS Design DNA targets landscape designers who receive project information through "scattered messages, reference images, sketches, files, site notes, and verbal instructions."
It is implied that these users are looking for a way to:
- Organize fragmented intake
- Ensure clarity in design decisions
- Prevent miscommunication or loss of requirements
Inference The primary customer appears to be individual or small teams of landscape designers working on projects with unclear or scattered inputs. No specific ICP segmentation is described.
Business Model & Pricing Evidence
The description does not contain any information about pricing, monetization, or business model.
Not evidenced.
Technical & Delivery Signals
The system was built using:
- Laravel backend
- PHP and MySQL-compatible persistence
- Eloquent models
- Canonical JSON
- SHA-256 integrity verification
- Database transactions
- Extensive automated testing (more than 600 tests)
OpenAI Codex was used for architecture exploration, implementation planning, writing services, test generation, Git workflows, and validation.
Services include:
- Evidence intake
- Evidence review
- Immutable snapshot sealing
- Snapshot verification
- Generation-attempt queuing
- Trusted identity assembly
- Atomic generation completion
- Lifecycle transitions
Inference The system is built with a focus on integrity, traceability, and safety. It uses backend technologies and AI integration for development rather than direct end-user interfaces.
Traction & Maturity Signals
The project was submitted to the OpenAI 2026 hackathon, indicating it is in an early stage of development.
It includes:
- More than 600 automated tests
- A backend workflow with multiple service components
- Immutable snapshot and integrity features
However, there is no evidence of revenue, customers, or adoption beyond the author's own account.
Not evidenced.
Competitive Context
The description does not mention any competitors or how SPS Design DNA compares to existing tools in landscape design project management or AI-assisted workflows.
Not evidenced.
Open Questions & Risks
- No evidence of traction or adoption: The system is described as a hackathon submission with no customer base or revenue.
- Unproven market fit: There is no indication that landscape designers are currently seeking this type of solution.
- Limited scope: The project appears to be a backend tool with no visible UI or end-user interface.
- Self-reported maturity: All claims about functionality and testing are from the author, not independent verification.
Questions the description leaves open
- What specific problems in landscape design project intake are you solving, and how do you know?
- Have you validated your approach with actual landscape designers or firms?
- How does this system integrate into existing design workflows or tools?
- What is the path from prototype to production, and what resources are needed?
- Are there any existing tools in the market that perform similar functions?
- What are the technical limitations of the current implementation?
Overall Assessment
Not evidenced.
The project is described as a hackathon submission with no revenue, customers, or traction data. The author states that it is not yet production-ready and has not been validated in the market.
Given the lack of evidence for commercial viability, adoption, or competitive positioning, there is insufficient basis to recommend investment or partnership at this time.
Confidence Low — based on self-reported evidence only, with no external validation.
User Stories BotA demo video on every pull request
Get a demo video on every new feature
GitHub App that watches your pull requests and records a narrated, captioned demo.
Save time on demo prep and make informed decisions faster with a video walkthrough of every new feature.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on Devpost. Back to the full gallery on Devpost.
This competitive analysis was produced byGenerated by a language model from this project's public Devpost page — its tagline, the author's own write-up and any built-with tags listed there — as captured in August 2026. Short quotations are the author's words. It is an opinion on the idea as a business, not on the people behind it, and it reflects the description as published then. If the project has moved on, request a correction below. The analysis is not independent research and contains no verified traction, revenue or customer data.
An independent guide by KFG International LLC — not affiliated with, endorsed by, or connected to Devpost or OpenAI.
