Accounts are created in Supabase → Authentication → Users. To reset a password, use “Forgot password?” on the admin dashboard.
Research backlog
“Research this” opens the person on the Subjects tab. Portraits still run in vatnik web until they move here.
Subjects
Add a subject
Adding a subject costs nothing; research is a separate, paid step.
1 · Research
One paid session on GitHub Actions, roughly $1; the cost shows on the Jobs tab.
2 · The mapping
Before approving: check roster_checked against the live roster, open three source URLs by hand (a plausible URL that 404s is the classic failure), and read the rejected half of the connection audit. What you save here is what the SQL step reads; editing an approved mapping withdraws the approval.
3 · SQL
Read it, then apply it in the Supabase SQL editor. Nothing here writes to the live profile tables.
4 · Identity photographs
Tick the photographs that are clearly this person (up to three) and confirm them. Read each caption: resemblance alone is not confirmation. A portrait is only ever made from photographs you have confirmed here.
5 · Portrait
Made from the confirmed photographs, beside the canonical style reference. Judge it against the reference: same style, same framing, and clearly the right person. Publishing commits it to main and the live site deploys it, so it is its own click, after you have looked.
Coverage gaps
How each country's roster differs from the reference's. A gap is more often an unresearched beat than a real absence, so each country lists how complete its data is beside it. Computed on GitHub Actions from the live tables with the same code as vatnik web; free, no model.
Discoveries
Run a discovery (one paid session)
Runs on GitHub Actions with the repository's API key; the cost shows on the Jobs tab when it finishes.
Jobs
If a job stays queued, the dispatch function is not reachable: run the “Research desk” workflow from the repository's Actions tab.