Genesis Cohort: Request Access

Why the Next 120 Days Matter?

Earth-based construction is crossing a critical threshold. Robotics, material science, AI-driven design, and climate pressure are converging—not into finished products, but into a new discipline that still lacks a shared language.

Standards, methods, and reference frameworks are being formed right now. What gets defined in this window will shape how Earth-Tech is built, regulated, funded, and understood for decades.

This moment favors founders, not spectators.

18

36

Every ~18 days we lock a chapter and publish a new “frozen” draft- moving the foundation from initial concept to validated, release-ready standards

That’s why this work cannot happen through one-off events— only through a time-boxed digitally- steering sprint with real, tangible deliverables.

This is the “Model T” moment —

not after adoption, but before standardization.

The Genesis Cohort is the reference layer the world will build upon.

1

Founding Release (Codex + Map + Charter)
Not an ongoing community. A defined sprint with a clear end date and publishable assets.

Two circles of 18 members: Hardware/Materials and Design/Software. A curated group of senior practitioners co-authoring the field’s DNA.

Inside the Genesis Steering Sprint

An async-first workflow that turns global expertise into publishable field foundations.

Integrated Steering Structure

Genesis is structured as an integrated ecosystem. A central Steering Committee aligns strategy, regulation, and finance, guiding two focused technical circles: Hardware/Materials and Design/Software. This structure ensures that the field's engineering foundation is not just technically sound, but also regulatorily viable and market-ready.

Strategic Alignment + Technical Execution. A complete ecosystem stack. Cross-circle alignment is built in—no siloed outputs.

AI-Assisted First Drafts, Expert Validation

Every chapter starts with an AI-assisted first draft (v0.1), synthesized and curated from experts' inputs and provided research bases. As a Fellow, you serve as the final authority—validating terms, adding real-world constraints, and approving what is ready for release in the technical Codex v1.0.

AI synthesizes the provided knowledge. Humans validate the standard.

18-Day Freeze Cycles & Decision Gates

Work runs in strict 18-day cycles: draft → validate → lock. This rhythmic cadence prevents "infinite threads" and ensures momentum. Strategic decisions arrive as one-page briefs—ensuring high decision velocity without operational drag.

Defined deadlines. Keeping the process crisp and lightweight.

Founding Signatories & Public Release

The sprint culminates in the public release of the field’s institutional assets. The official roster of Founding Signatories will be published alongside the Founding Charter and the technical Codex. Fellows may sign with section-level reservations—preserving professional rigor without blocking the release.

Publishable outputs. Your signature on the field’s DNA.

Designed for senior practitioners: clear roles, fixed cycles, publishable outputs.

The Ecosystem Map

A curated, publishable map of the entire Earth-Tech landscape—companies, labs, builders, toolchains, and key opinion leaders—organized by domain and geography. Built to become the reference layer founders, investors, and institutions use to navigate what’s real, what’s emerging, and who is shaping standards right now.

Logo-based. Region-tagged. Updated as the field evolves

This Fellowship Is Not for Everyone

We value alignment over scale.

This Circle Is For You If...

✔ This space is designed for those ready to do the hard, necessary work of field-building:

This Circle Is Likely Not a Fit If…

✖ To protect the integrity of the work, this is likely not the right fit if you:

• Co-Authorship Intent: You want to co-author the industry’s foundational standards, not just attend discussions.

• Disciplined Commitment: You can commit 1.5–2.5 hours per week for the 120-day sprint.

• Expert Sign-off: You are comfortable validating and signing off on release-ready language for the Codex, Charter, and Global Map.

• Substance over Opinion: You prefer contributing through technical constraints and source-linked validation rather than open-ended opinions.

• Async Logic: You value a lean, async-first workflow with fixed 18-day freeze cycles and binary decision gates.

• Seeking "Access" Only: You are looking for visibility, networking, or "access" without a commitment to specific deliverables.

• Passive Experience: You expect a traditional course, webinar series, or a passive community experience.

• Unclear Constraints: You need guaranteed outcomes without engaging in the necessary tradeoffs and technical constraints of field-building.

• Proprietary Barriers: You cannot work within Safe-Harbor rules or share the non-proprietary knowledge needed to build a shared industry foundation.

• Cadence Friction: You cannot realistically meet the production cadence, including the 18-day freeze dates and validation deadlines.

Founding influence is earned through published work.

A Note from the Founder

I’m Idan Keisar.
a builder, a technologist, a CPA, and a father.

My professional journey began in the analytical world of systems and structures. At PwC, and later as an economist, I spent years studying how markets move and how institutions make decisions at scale. I’ve always been obsessed with the “operating system” behind the reality we see.

That obsession led me into entrepreneurship. After co-founding several startups, I established Impact Labs—one of Israel’s leading ecosystems for hardware R&D and advanced manufacturing. As an expert in 3D printing and additive manufacturing, I built the platform to help teams move from concept to physical reality. There, I learned that meaningful innovation doesn’t happen in isolation; it requires shared practice and robust infrastructure for builders.

Over time, my Ikigai brought me back to the most ancient technology of all: earth.

I reached a point where it became clear that the way we build no longer serves the way we live. Homes are becoming less accessible, construction is increasingly extractive—economically and environmentally—and brilliant innovation stays trapped in prototypes and presentations. What’s missing is not technology—we already have robotics, AI, and material science. What’s missing is the shared institutional foundation.

I’m building the Genesis Cohort because I believe we are at a “Model T” moment for Earth-Tech. But the Codex and the Charter are only the beginning. My roadmap leads directly from this intellectual foundation to the establishment of a Global Earth-Tech Innovation Center—a specialized "Impact Labs" dedicated to earth-based construction, located within the first Tree of Life village. This will be the physical engine where our shared standards are tested, refined, and deployed at scale.

I don’t claim to have all the answers, and I’m not here to lecture experts. My role is to be the Architect of this sprint—leveraging my experience building ecosystems to provide the structure, discipline, and an AI-assisted, expert-validated production engine that turns raw expertise into publishable foundations.

I’m deeply committed to this mission—not only for the industry, but for our children—to inherit a world built with wisdom, not just force.

If you’re a builder who values substance over announcements, you may be a fit for Genesis.

Let’s build the foundation.

Idan.

Request Access: Genesis Cohort

Help Define Earth-Tech Before It Standardizes

Request Access to Genesis

Seats are limited to 36. Applications are reviewed on a rolling basis.

Accepted candidates receive the Acceptance Pack (dates, protocols, tracks and relevant pricing)

What is the Genesis Cohort, in one sentence?
A 120-day, async-first steering sprint for 36 senior practitioners to co-author the foundational assets of Earth-Tech: the Codex v1.0, the Global Ecosystem Map, and the Founding Charter.

Frequently Asked Questions (The Deep Dive)

Everything you need to know about the mission, the mechanics, and the commitment of joining the Genesis Cohort.

THE MISSION & VALUE

Why does Earth-Tech need “field foundations” at all?
Because the technologies are converging faster than the shared language, reference standards, and practical constraints. Without a common foundation, the field stays fragmented—slowing adoption, financing, and regulatory clarity.

Why is this urgent now? Can it wait?
We are in a pre-standardization window. The window to define the field’s DNA is closing. What gets defined in this period becomes the reference layer others build on for decades. Waiting means continued fragmentation, incompatible approaches, and slower adoption.

What do I get as a Fellow / Founding Signatory?
You move from contributor to co-author of the reference layer:

• Founding attribution: Your name (and optionally your organization) listed on the published institutional assets.

• Direct influence: Help shape definitions, constraints, and reference protocols the field can safely align around.

• High-trust network: A curated, capped circle focused on deliverables—not community noise.

• First consideration: Priority consideration for future initiatives and physical programs (when launched), subject to availability and program terms.

Why TerraBots and Idan Keisar to lead this?
TerraBots is building the operating platform and production engine for the sprint. Idan brings institutional discipline (PwC strategist, CPA, economist) and hands-on ecosystem building experience (founder of Impact Labs—Israel’s pioneering ecosystem for hardware R&D and advanced manufacturing). The role is not “guru” or lecturer—it's architecting the structure that turns expert input into publishable foundations.

What does Genesis not promise?
We do not guarantee investment, clients, or specific pilot projects. Genesis is a field-building initiative focused on producing foundational assets. These foundations can enable future collaborations, programs, and initiatives—but outcomes depend on participants and external conditions.

THE MECHANICS & WORKFLOW

When does Genesis run, and what is the cadence?
Genesis begins February 06, 2026 and runs for 120 days. Work is structured into 18-day freeze cycles. Each cycle locks a chapter for release-ready progress.

How much time is realistically required?
Most Fellows should expect ~1.5–2.5 hours per week. The work is structured around high-leverage validation and targeted input—not operational noise.

How does the async-first model work?
Work happens through a structured, document-based system (Google Drive + email). Each 18-day cycle follows a clear path: draft → validate → lock.

Are there live calls?
One live sync call per 18-day cycle (optional but strongly recommended). Everything else is async. Calls are recorded and summarized.

Who are the 36 Fellows, and how is the cohort balanced?
The cohort is curated to balance:

• Circles: Hardware/Materials and Design/Software (up to 18 per circle)

• Profiles: industry leaders, academic pioneers, hands-on builders

• Geography: global representation to avoid local-only assumptions

What happens if I disagree with a specific clause in the final Codex or Charter?
We use a structured reservation mechanism. You may sign the final documents while formally registering a section-level reservation on a specific point—preserving professional integrity without blocking publication.

How do you handle time zones?
The async-first system is designed for global participation. Deadlines are set in 18-day windows. The optional sync call is scheduled in advance and recorded for Fellows who cannot attend.

Is the working language English?
Yes. All official drafting, review, and published outputs are in English for global applicability.

OPERATIONAL SHARE (PRICING) & RESOURCES

Does Genesis have a financial contribution?
Yes. Genesis runs with an Operational Share model. The funds are paid to TerraBots to cover the real costs of producing the Genesis cycle and publishing the deliverables.

Why does it cost money?
Because producing institutional-grade outputs at global quality requires a real production engine: coordination, synthesis, editing, information design, legal review, and operational infrastructure. This is not a casual community—it is a time-boxed production sprint with publishable outputs.

What does the Operational Share cover?
Operational Share is designated to cover:

• Program operations & coordination (running the sprint, maintaining cadence, ensuring output quality)

• AI-assisted synthesis & tooling (draft acceleration, structured knowledge production)

• Professional editing & information design (turning drafts into publishable documents)

• Legal & governance review (charter wording, attribution, release protocols)

• Publication & distribution (release packaging, website publication, dissemination)

Will I receive budget transparency?
Yes. With the acceptance package and payment documentation, TerraBots provides a clear overview of the budget allocation and how the Operational Share is used to deliver the outputs.

What are the pricing tracks? Are scholarships available?
Pricing tracks and Operational Share options are disclosed after acceptance (to avoid a “pay-to-play” dynamic). A limited number of scholarships are available for exceptional domain experts.

Can my organization pay on my behalf?
Yes. Corporate-sponsored participation is supported, including invoices and payment via standard corporate processes (e.g., card/wire and PO where applicable).

Can I sponsor without joining as a Fellow?
Yes. Organizations can support the mission through sponsorship packages (e.g., logo placement, Ecosystem Map support, publication support) without committing a domain expert. Contact us by email for sponsorship options.

IP, TEAM, CREDIT & PRIVACY

Will I be required to share proprietary IP or confidential information?
No. Genesis operates under a clear Safe-Harbor rule: do not upload proprietary designs, trade secrets, or confidential client/company data. We build shared definitions, interfaces, constraints, and reference protocols- what the field can safely align on.

Can I use my team or researchers to support my contribution?
Yes, with prior approval. Teams can support background research or drafting under your profile. However, the Signatory (you) remains responsible for final validation and sign-off.

How is credit attributed?
All Founding Signatories appear in the final published documents. You can be listed with your name, title, and organization (optional), subject to your organization’s policies.

Are applicant lists or preliminary rosters public?
No. Applicant lists and preliminary rosters are not published. Names appear publicly only after seat confirmation and explicit consent.

What happens if I cannot meet the minimum contribution requirements?
Founding Signatory status is earned through contribution—not payment alone. If a Fellow repeatedly fails to respond to tagged items or validation requests, they may be excluded from the final signatory roster to protect the integrity of the title.