Oko/Docs

Contributions#

Wisent rewards the people who make it better. Its contribution ledger lives in compute.wisent.com; Oko reports to it the work a person's prompts produced that a verdict accepted.

What counts#

Every task the task map settles as done is one work.accepted contribution of the member who wrote it: the person whose message the task was read from. Nothing judges a prompt by its words; only the verdict on the work it asked for counts, and a task that is not done reports nothing.

The task's id is the event id, so reporting again never records a task twice, and a task a later defect reopens was reported once and stays reported. An event names the tasks it reports in its evidence, and its quantity is how many it names. Its time is the moment the verdict settled the task: a done task whose settling states no time is not reported, and is named as undated instead of given a time nobody stated.

Commands#

command	effect
`oko contributions pending [--ledger URL] [--json]`	lists the events `report` would send — task, author, when it was settled — and the undated done tasks it would not; with a ledger named, marks each event held or not
`oko contributions report [--ledger URL] [--json]`	sends the events the ledger does not hold yet and lists what it answered for each, recorded or its refusal, the ids it already held, and the undated tasks
`oko contributions link CODE [--ledger URL] [--json]`	links the member signed in to Oko to the Wisent account whose one-time code from the Rewards page it is given, and prints the ledger's answer; no other member can be named, so a code holder links only themselves

The ledger is --ledger, else OKO_CONTRIBUTION_LEDGER_URL. Both commands ask it once which events it already holds, so a report costs one request per newly settled task however long the task map's history. The bearer Oko presents as the reporter oko is the item playing oko-contribution-ledger, read under the consumer oko-contribution-client; the ledger's operator declares that bearer's SHA-256. Credits appear on the author's account once the author, signed in to Oko, creates a one-time code on the Rewards page of compute.wisent.com and runs link with it, and once a rate for work.accepted is published.

In Oko Desktop#

Evidence → Contributions runs the same three operations through Oko's native API (domain contributions, actions pending, report, link): it lists the accepted work with whether the ledger holds each event, Report to the ledger sends what it lacks and shows per task what the ledger answered, and Link your account takes the one-time code and links the member signed in to Oko. The ledger origin field is blank by default, which leaves the choice to OKO_CONTRIBUTION_LEDGER_URL. Every refusal is shown in Oko's words; a report the ledger refused in part is shown as a refusal that names the refused tasks and carries the whole report.

Refusals#

sentence	meaning
`oko contributions report: no contribution ledger is named; pass --ledger URL or set OKO_CONTRIBUTION_LEDGER_URL`	nothing to report to; `link` says the same with its own name
`oko contributions link requires <id>`	the code is missing
`oko contributions link does not take --member; it takes --ledger`	a member was named: only the signed-in member is linked
`oko contributions link: the ledger refused: … unknown or already used …`	the code was spent or never created: create a new one
`oko contributions link: the ledger refused: … linked to another account`	the member already belongs to another Wisent account
`oko contributions report: the ledger refused <task>: <its sentence>; …`	the ledger refused those events; the rest were sent, and the command exits non-zero
`oko contributions: asking the ledger what it holds failed: …`	the ledger did not answer, or refused the bearer, in its own words
the credential read's own sentence	the bearer could not be read from the vault

The real test is tests/contributions/report.rs.

Migrated from src/content/docs/contributions.md