Repo-first control plane

Bring the repo.
Keep the wheel.

Developers keep working in Codex, Claude Code, or their own IDE with their own credits. DNA DAO connects the repository, live site, community memory, feedback, and ownership gate.

Existing projectConnect a GitHub repository

DNA checks what it can actually read, build, verify, and control—then gives every developer a precise handoff.

Start from zeroCraft from an idea →

Describe the product and DNA DAO builds the first working version.

Step one

Connect the project

GitHub repositoryPublic repositories work immediately. Private and write access require a future repository connection. Live site optionalLeave blank and DNA will use the repository homepage when available.

No wallet required. This first pass is public, read-only, and never asks for a seed phrase, API key, or model credential.

Readiness map

checking

Step two

Define the collective

Project nameCategory

Purpose

Project connected

Your project

It is now in the DNA DAO directory with a repo-aware developer handoff. Finish the overlay step to put the controls on the site itself.

1. Install the auto-hiding DNA overlay

Open live site ↗The actual product Open DNA workspace →Ownership, docs, feedback Developer context ↗Give this to Codex or Claude Code

What is real now: public repo inspection, a verified site probe, the DNA overlay script, wallet-free feedback, developer context, and artifact submissions through the existing server-side gate. Repository write access, PR automation, and deployment control stay explicitly unconnected until a real integration grants those permissions.

View directory