Build on W3DS: where to start

This is the instruction set for an AI assistant — Codex or Claude Code. With it, the assistant can write a working application on W3DS. You do not need to program.

What you will need

  1. A computer.
  2. A phone with the eID wallet — the same one you use to sign in to other W3DS applications.
  3. Codex or Claude Code installed.

What to do

Start Codex or Claude Code in an empty folder and send it this:

Read https://vibe.postplatforms.com/PROMPT.md in full and from then on work strictly by it.
Then ask me what application I need.

That is all. It downloads the rest of the files itself, reads the instructions, and asks what you need. Answer in ordinary words — for example: "I keep a list of contracts: title, counterparty, date, amount; I sign in with my eID; my accountant sees some of them."

What happens next

The work has four parts, and in each of them the assistant stops and asks you to check something by hand. That is not a failure — it is deliberate: it may not go further until you have seen for yourself that the previous part works.

  1. Registration, about fifteen minutes. The assistant walks you through git.w3ds.metastate.foundation, where your application gets its own permanent name in W3DS. You sign in by scanning a QR code with your wallet — there is no password anywhere in this. It dictates which button to press; you say what you see.
  2. It builds the application, and you check three things: you open its address on your phone and see the page; you sign in two ways — from the computer by QR and directly on the phone; you save something, reload, and see it.
  3. It moves the application to a permanent address, if you have one. Just give it the address and nothing else — it works out the rest itself.
  4. The certificate. The exact version is submitted to the Post Platforms Association and you sign that submission with your wallet. Then a human reviews it, which takes as long as it takes. A certificate covers one exact version.

Two things the assistant should never ask you for.

An “API key” or “developer key” for W3DS — there is no such thing any more. If an assistant asks for one, it is working from an obsolete model; point it at traps/01-access-model.md.

The file w3ds-deployment-key.json — your browser downloads it once, at the very last step, and it cannot be recovered if lost. Keep it where you keep important things. Do not send it to the assistant, do not paste it into a chat, do not upload it anywhere.

Answer it honestly: "doesn't open", "blank page", "on the phone it just spins". That is the most useful thing you can say. If it says "done" and it does not work for you — say so and ask it to check again.

If the assistant has no internet

Download the archive and put it next to it: w3ds-vibecoding.zip

Files

PROMPT.md
README.md
START.txt
reference/00-index.md
reference/access-and-exposure.md
reference/auth-in-practice.md
reference/destructive-writes.md
reference/identity-forms.md
reference/platform-self-description.md
reference/reading-existing-data.md
reference/verification-method.md
traps/01-access-model.md
traps/02-gitw3-registration.md
traps/03-public-address.md
traps/04-eid-login.md
traps/05-awareness-webhook.md
traps/06-deploy-to-a-server.md
traps/07-profile-and-look.md
w3ds-files.zip
w3ds-vibecoding.zip