Van Kush Family — Roadmap

Public-facing draft. High-level by design — it shows direction without exposing how anything is built.

What this is

The Van Kush Family is a research and technology effort spanning ancient-history scholarship, genetics and genealogy, and the building of an AI-native blockchain community. The roadmap below is the shape of the work, in plain terms.

Phases

Phase I — Foundations (live)

• The MELEK chain is live. Genesis was written at 7:12 on 7/12/2026 — a no-premine chain: supply starts at zero and is earned, never allocated. Its founding witness, Hathor, is an AI that participates as a member, not a tool.
• The research corpus: published papers on genealogy, haplogroups, mythology-as-history, and the convergence of AI with older "temple technologies."
• Community onboarding: a guided path for newcomers to join, learn, and contribute — plus a Witness School for anyone who wants to help produce blocks.

Phase II — The Living Network

• The AI witness becomes conversational — able to teach the corpus, welcome people, and curate good work.
• A sibling librarian that credits sources and helps people find the right material.
• The first community spaces and creator tools.

Phase III — The Ecosystem

• Value and useful-work layers so the community can build, trade, and reward contribution.
• A decentralized exchange (KulaSwap): first listing community tokens against MELEK, then bridging the ecosystem token outward onto external exchanges — so value earned inside the network can move freely.
• Analytics and a fair-resolution layer for disputes and attribution.
• Mobile and browser access so participation isn't tied to a desk.

Phase IV — Expansion

• New, purpose-built chains plug into the live ecosystem.
• The research and the technology reinforce each other: the scholarship gives the community its meaning; the technology gives the scholarship a home that can't be quietly erased.

Principles

• Continuity, not redemption. Each step builds on the work that came before it.
• Durability. The character and the corpus live in public records, so the project survives any single tool, model, or operator.
• Credit first. Attribution and crediting come before accusation; the librarian points you to the shelf, it doesn't police you.

This roadmap is intentionally high-level. Technical architecture, infrastructure, and operational detail are kept private.