Lineage Nook

What the company appears to be: Lineage Nook is a self-reported personal project built by one developer (Poppy_Bumpkin Vang) as part of an OpenAI 2026 hackathon submission. It is described as a private, evidence-grounded tool for preserving family history and relationships between generations. The author states it supports mapping family relationships, preserving claims with sources, visualizing lineage through a graph, and exporting structured data.

What changed: This is a self-reported development effort submitted to a hackathon. No prior version or evolution is described; this is the first public manifestation of the idea.

Single most important open question: Is there any evidence that Lineage Nook has been used by anyone beyond its creator, or that it has achieved any traction or adoption?

The description states that Lineage Nook helps users:

• Create and organize people and family records
• Map relationships across generations
• Preserve claims alongside their supporting sources
• Explore lineage information through a visual relationship graph
• Keep separate family trees and user records securely isolated
• Export structured lineage information for long-term preservation

The author describes it as a private workspace that preserves connections without pretending every claim is equally certain or fully resolved. It is designed to distinguish evidence from interpretation.

Evidence: The project write-up explicitly lists these features.

Inference: Based on the description, Lineage Nook appears to be a personal tool for family history management with an emphasis on preserving uncertainty and source integrity.

The author states that Lineage Nook was designed as a place where people can map family relationships, preserve supporting sources, distinguish evidence from interpretation, and carry family knowledge forward without flattening it into a simple family tree.

It is positioned as a tool for preserving family history in a way that acknowledges complexity, uncertainty, and the importance of source documentation.

Evidence: The project write-up describes this positioning directly.

Inference: The product's positioning reflects an attempt to address limitations in traditional genealogy tools by emphasizing evidence-based storytelling over simplified lineage structures.

The description does not name specific target customers or personas. It implies a general audience interested in preserving family history and relationships, particularly those who value accuracy and source documentation over simplistic genealogical trees.

Evidence: No explicit customer segments or personas are mentioned.

Inference: The tool likely targets individuals or families who want to maintain detailed and nuanced records of their lineage, possibly including genealogists, historians, or people with complex family histories.

There is no evidence in the description of any business model or pricing structure. The project is described as a personal hackathon submission.

Evidence: Not evidenced.

Inference: If this evolves into a commercial product, it would likely be priced for individual users or small family groups, but no such indication exists.

The author built Lineage Nook using:

• React and TypeScript
• Supabase and PostgreSQL
• Row-level security and scoped database privileges for user isolation
• Deterministic exports for portable lineage records
• Automated tests, type checking, production builds, and browser verification
• Git commits and an evidence ledger to preserve a traceable build history

The development process involved using Codex (an AI coding agent) in a repository-based session. The author provided intent, privacy requirements, decision boundaries, and approval gates while Codex implemented features, ran tests, documented evidence, and stopped when new authorization or verification boundaries appeared.

Evidence: The project write-up details the tech stack and development approach.

Inference: The use of AI coding tools suggests a modern, automated development process. The emphasis on security and testability indicates attention to robustness and privacy.

There is no evidence of any traction or adoption beyond the author's own development effort. No customers, users, revenue, or usage metrics are mentioned.

Evidence: Not evidenced.

Inference: As a hackathon submission, it has not yet reached a stage where user engagement or market validation can be assessed.

The description does not mention any competitors or existing solutions in the family history or genealogy space. No comparison to other tools is made.

Evidence: Not evidenced.

Inference: Given the focus on privacy, evidence preservation, and uncertainty handling, Lineage Nook may aim to differentiate from traditional genealogy platforms that often simplify or flatten historical information.

• No traction or user base: The project is described as a solo effort with no evidence of adoption.
• Unverified claims: All descriptions are self-reported and unverified; there is no independent confirmation of functionality or performance.
• Limited scope: As a hackathon project, it may not reflect long-term viability or scalability.
• Unclear commercialization path: No indication of how the tool might evolve into a sustainable business.

Evidence: Not evidenced.

Inference: The lack of any external validation or user feedback raises concerns about real-world applicability and potential market demand.

1. What specific use cases drove the design decisions around privacy, source documentation, and uncertainty handling?
2. Has anyone other than yourself used Lineage Nook? If so, what feedback did you receive?
3. How do you plan to scale beyond a single-user model if this becomes a product?
4. Are there any known technical limitations or edge cases that have not been addressed in the current version?
5. What is your vision for monetization or long-term sustainability of the project?