Roots

The description states that Roots is a local-first genealogy workspace designed to help people build family trees using evidence-based methods. It allows users to start from blank trees, sample data, or imported files, and organize people, relationships, sources, research targets, interview prompts, proof gaps, rejected candidates, and export-ready data.

Key features include:

• Separation of canonical tree data from generated outputs.
• Source registry and tracking of claims, citations, confidence levels, contradictions, and human review.
• AI workers that assist in planning research, searching sources, summarizing findings, and identifying missing evidence — but do not silently rewrite the tree.
• Visual exploration tools: tree views, family profiles, research boards, timelines, journeys across place and time.
• Export paths for GEDCOM/GEDCOM X interoperability.

The author also notes that Roots was built using Codex, JavaScript, Three.js, and TypeScript. It is described as a reusable public tool derived from a private prototype named MyFamilyTree.

Inference The product appears to be a prototype or early-stage tool, likely intended for personal use or limited community adoption.

The author positions Roots as:

• A local-first, AI-assisted genealogy starter kit.
• Designed for people who want to understand their family history without compromising privacy or accepting unsourced AI guesses.
• An evidence-first approach that separates records, claims, citations, confidence, contradictions, and human review.

It is described as a public version of a private tool (MyFamilyTree), suggesting a shift from personal use to broader applicability.

Inference Roots positions itself as a niche tool for genealogists who value rigor over convenience — not a mainstream consumer product.

The description states that Roots is aimed at:

• People who want to build family trees.
• Those seeking to understand their origins without compromising privacy.
• Users who prefer evidence-based approaches over AI-generated guesses.
• Individuals working with sensitive or private data.

It also implies a user base interested in:

• Researching genealogical records.
• Managing contradictions and uncertainties.
• Maintaining control over personal data.

Inference The target customer is likely a small subset of genealogists — possibly hobbyists, family historians, or researchers — rather than general consumers.

There is no evidence in the description of any business model, pricing structure, monetization strategy, or revenue streams. The author does not mention whether Roots will be free, paid, open-source, or sold as a service.

Inference The project appears to be self-funded and possibly open-source, but this cannot be confirmed from the description alone.

The author reports:

• Built using Codex, JavaScript, Three.js, and TypeScript.
• Developed with lessons from a private prototype called MyFamilyTree.
• Designed around a clear workflow: start a project, add people, define claims, identify proof gaps, run bounded research workers, review evidence, visualize result, export.
• Includes ADRs (Architectural Decision Records), source policies, verification scripts, research logs, export checks, and privacy gates.

Inference Technical delivery shows discipline in architecture and development practices, but no information on scalability or production readiness.

There is no evidence of traction, revenue, customer adoption, or usage metrics. The author describes Roots as a personal project that evolved into a public tool, but does not provide data on:

• Number of users.
• Engagement levels.
• Customer feedback.
• Product usage statistics.

Inference Roots appears to be in an early stage, possibly prototype or alpha, with no demonstrated market traction.

There is no evidence of competitors mentioned or analyzed. The description does not reference existing genealogy tools or platforms such as Ancestry.com, FamilySearch, MyHeritage, or others.

Inference The competitive landscape is unknown from this description — it's unclear whether Roots addresses a gap or competes with existing tools.

Key risks and red flags based on the self-reported description:

1. No traction or revenue: The product has no evidence of user adoption, monetization, or market validation.
2. Single-person team: Only one developer (Klaus Brave) is listed.
3. Unclear business model: No indication of how Roots will be monetized or scaled.
4. Limited scope: Designed for personal use and research; unclear if it can scale to broader audiences.
5. Self-reported only: All claims are unverified, with no external corroboration.

Inference Without evidence of adoption, funding, or product-market fit, the risk of failure is high.

1. What specific problems in genealogy do you observe that Roots solves?
2. How many people have used this tool outside of your own family?
3. Have you received any feedback from users beyond yourself?
4. Is there a plan to monetize or scale the product?
5. What is the long-term vision for Roots, and how does it differ from existing tools?
6. Are there any partnerships or integrations planned with genealogy platforms or archives?
7. How do you intend to onboard new users and guide them through the process?
8. What are the technical limitations of the current version that would prevent wider use?