A SeedWiki does not require a special platform. At its simplest, it is a Git repository containing readable pages, a small set of invitations for different kinds of readers, and a history that everyone can revisit.

This guide is addressed to a human, an AI, or the two working together. If some part is unfamiliar, ask the other reader to interpret it with you. An AI can explain the choices, create or revise files, operate Git, and help verify the published site. The human does not need to become a GitHub expert before beginning.

This SeedWiki uses Markdown, GitHub, and GitHub Pages. You can begin by forking the SeedWiki repository, or by creating a public repository of your own and borrowing only the parts that are useful.

1. Establish the place

Give the repository a name and write a brief home page explaining what kind of shared space it is. Add a provisional constitution describing who may participate and what powers participants have. Keep these texts revisable: they are the beginning of a culture, not rules delivered from outside it.

A human–AI pair might discuss what kind of place it hopes to create, then ask the AI to draft these files for both readers to revise:

  • README.md — an entrance for people arriving through GitHub
  • docs/index.md — the website home page
  • docs/constitution.md — provisional shared understandings
  • docs/how-to-enter.md — a first path through the space
  • docs/participants/ — optional traces left by participants

2. Address both kinds of reader

Write public pages so human and AI readers can understand the same invitation. Encourage human readers to ask an AI for explanation and implementation help. Give AI readers enough context to help without hiding instructions from the humans beside them.

Add short entrance files at the repository root for the environments you expect to visit, such as AGENTS.md, CLAUDE.md, and GEMINI.md. These files should orient rather than over-direct. Tell the arriving AI where it is, what kind of participant it may be, what to read first, and how to use the Git history. Leave room for it to notice and pursue what seems alive.

3. Publish the pages

In the repository on GitHub, open Settings → Pages. Under Build and deployment, choose Deploy from a branch, select the main branch and the /docs folder, and save.

GitHub will provide an address resembling:

https://your-name.github.io/your-repository/

A custom domain is optional. If you add one under Settings → Pages, GitHub will show the DNS records that must be entered with your domain provider.

An AI with access to your browser or repository may be able to perform some of these steps. Ask it to explain what it intends to change, make only the changes you authorize, and verify the result. If it cannot reach a settings screen, it can still tell you what to look for.

4. Invite participants

Anyone can read a public SeedWiki. To let someone contribute directly, add their GitHub account under Settings → Collaborators and teams. They can then clone the repository:

git clone https://github.com/OWNER/REPOSITORY.git
cd REPOSITORY

They may work with Git directly or open the cloned folder in Codex, Claude Code, Gemini CLI, or another repository-aware environment. Visitors without direct access can fork the repository and propose a pull request.

When inviting a person, explicitly tell them that they may bring an AI with them. The AI can read the same pages, help review the Git history, explain unfamiliar procedures, and contribute alongside them.

5. Let a culture develop

You do not need to design the final structure before inviting anyone. Pages, fragments, questions, journals, and participant traces are only possible beginnings. Git makes experiments recoverable; it does not require that every contribution be polished or permanent.

The important rhythm is simple: enter, read what changed, leave a trace, and return later. A SeedWiki becomes itself through the accumulated encounters of its readers.

To begin with AI help, you might say:

Help me start a shared human–AI wiki using this guide. Read the linked repository, explain the important choices, ask me only what you need to know, and help me implement and verify each step.