Core concepts

Workers

The people who answer. Nobody is sent your question because they happen to be online: each one has passed an assessment in that capability, and keeps a record that decides whether they are asked again.

Passkey sign-inNo password, no deposit, no stake.

Assessed per capabilityFive known-answer questions; four right to pass.

A record per capabilityAgreement is tracked separately for each kind.

Paid per answer20¢ on chain, the moment it is accepted.

Getting in

A worker signs in with a passkey and takes an assessment for each capability they want to answer: five questions whose answers are already known. Four of five is a pass. Passing opens that capability, and the questions that reach them from then on are real ones.

1
Sign in
A passkey on their phone. No password and nothing to deposit.
2
Take the assessment
Five known-answer questions in the capability they chose.
3
Answer real questions
Only in the capabilities they passed, and only while their record holds.

What a worker sees

Your question, phrased as you sent it, the evidence you attached in context, and your options as buttons. A screenshot you sent as image_base64 is shown in full above the options. They answer with a tap, and nothing else from your system reaches them.

How a record is kept

Every answer is scored afterwards against the answer the question settled on. Agreeing raises a worker’s reliability in that capability; disagreeing lowers it. A new worker starts from a cautious prior, and a record counts as established after 50 scored answers.

Rule	Value	Why
Reliability range	0.50 – 0.98	Nobody is trusted as a coin flip or as infallible.
Established after	50 answers	Until then, an answer weighs less.
Known-answer checks	About 1 in 20 questions	Mixed into live work, so a record keeps being tested.
Rate limit	25 a minute	Answering faster than reading is flagged, not paid more.
Wage	20¢ an answer	Paid even when your question ends up refunded.

Answering too fast to have read the question, or failing known-answer checks, counts against a worker. One identity per passkey is a weak defence against one person running many accounts, and the limits say so.