DTF Genetics
Breeding projects, lineage and generation context, current seed releases and the storefront.
Open Genetics →DTF Projects
This roadmap follows the same release records used by DTFSeeds deployment. A game only appears as playable here when it has a public route and canonical source owner; engineering builds and concepts stay separated until they pass the release gate.
Live platform
These are production surfaces, not concept pages.
Breeding projects, lineage and generation context, current seed releases and the storefront.
Open Genetics →Start Here, Academy, Encyclopedia, subject libraries, visual learning, sources and practical cultivation education.
Open Learn →GrowLens for records and measurements plus Grow Doc for structured plant-health evidence and differential reasoning.
Open Tools →Twenty-three public browser games, two public multiplayer games, and four tracked release/runtime candidates under one consistent destination.
Open Games →Public game registry
These 21 solo, local, strategy, puzzle and arcade titles plus the two multiplayer titles below make 24 public browser games in the canonical registry.
Plant-science and cultivation knowledge challenge.
Play →Life-path browser game from early grow decisions to legacy.
Play →Full 20-level platform campaign across five worlds with phenotype powers, six bosses, checkpoints, approved Seed Man art, Three.js world rendering and local high scores.
Play →Filterable discussion deck built for growers and cultivation groups.
Play →Cannabis-fantasy board race with HIT cards and special spaces.
Play →Strain-themed property strategy game.
Play →Three-lane card battle using the eight-family strain roster.
Play →Cannabis and cultivation crossword puzzle experience.
Play →Browser deduction game built from the THC Guess Who project.
Play →Retro browser action vertical slice set in The Veg Lab.
Play →Genetics adventure with phenotype, breeding and Vault Garden systems.
Play →Fast memory-matching game built around strain-family pairs.
Play →Cannabis-themed browser bingo with a quick, readable card loop.
Play →Terpene-themed quick-play challenge with a compact session loop.
Play →Deduction-style strain guessing game designed for short sessions.
Play →Wheel-based quick game with strain outcomes and replayable spins.
Play →Arcade defense mini-game built around protecting the playfield.
Play →Fast time-management arcade shift with fictional batches, stations and combos.
Play →Compact challenge game built for repeatable browser sessions.
Play →Draft-and-select mini-game themed around phenotype choices.
Play →Quick pattern and line-building browser game.
Play →Multiplayer
Only routes promoted by the canonical public-navigation contract appear here. Multiplayer builds still awaiting production runtime or live acceptance remain in the candidate roadmap below.
Development roadmap
These four release/runtime candidates remain outside the public catalog until their visitor-facing deployment and exact live-verification requirements are met.
Playable locally, but the persistent Node runtime, public health/Socket.IO path, and two-browser reconnect/rematch acceptance still have to pass before promotion.
Playable locally, but production service configuration plus frontend/API/Socket.IO and two-browser/mobile multiplayer acceptance are still required.
The qualified package exists; production publication and exact live-route verification are still required before public promotion.
The qualified package exists; production publication and exact live-route verification are still required before public promotion.
Supporting projects
Keeping these separate prevents internal systems and publishing projects from inflating the playable-game count.
Community voice-bot implementation requiring persistent service hosting and credentials.
Plant-science story publishing system with controlled content and release workflow.
Source-controlled media-processing and publishing-package automation.
Release gate
Public navigation, canonical source ownership, deployment records, project status and the live route are validated as one release contract.
The core visitor flow works in its canonical repository and the production package exists.
Source, registry, route identity, responsive behavior and runtime checks pass.
Only then does the game receive a public Play link and leave the development roadmap.