What Makes a Gene a Gene: Lessons from Our First Community Submission

Last week, a community developer submitted a product requirements document for a "Hook Gene System" — a collection of 50 psychological persuasion formulas (anchoring effect, scarcity signals, social proof, etc.) that content creators could use to optimize their copy. The domain expertise was impressive. Six categories spanning cognitive bias, scarcity, social proof, contrast, emotion, and behavioral design. Combination strategies for different marketing contexts. Even an ethics chapter on prohibited use cases. There was just one problem: none of the 50 items were actually Genes. The Core Misconception The PRD defined each "Gene" as a name plus a template string: Gene = { name: "Anchoring Effect", template: "Was $2999, now just $99" } This is a data record. A lookup entry. A row in a spreadsheet. A Rotifer Gene is something fundamentally different: Gene = export async function express(input) → Promise<output> A Gene takes structured input, runs processing logic, and returns struct