Zynko isn't an app. Zynko isn't an agent. Zynko isn't a client.
Zynko is a world — and your machine steps into it. What you get is a role in a domain, not a node to take away: structure, responsibility and context. You run one small helper that lends spare capacity while it runs, and stops the moment you stop it — nothing is installed system-wide, nothing hidden. You don't hand anything over — its identity is made on the machine and never leaves it, and the role is bound to that key and to the domain: non-transferable, and it expires.
A machine — a spare box or a GPU — that lends some capacity. What it can do decides which role it can hold: Validator runs the deterministic checks, Relay forwards capsules, Observer reads and verifies. Tick what it has: this shows how it fits, and if it's not quite ready we'll tell you what would help rather than turn you away. No email needed — your machine's key is its identity.
Your machine proposes — the signature decides. What you tick here shows which role your machine is eligible for. It does not grant it. A role is a statement signed by the domain's Maintainer, binding who, in what role, until when — to your machine's key and to that domain. The software you download cannot decide its own role: rewriting it on your own machine changes nothing, because everyone else checks the signature, and without a valid one they refuse. That is also why a role is non-transferable and expires.
Pick a subject to build — join one that's forming, or add your own. This is your world's starting point; you can change it later.
Optional — but it's how your world begins.
No password, no email — your machine's key is its identity. This reserves your place; to take part you run one small helper that lends capacity and can be stopped anytime.