Four cases. Four things to check.

A signed chain still needs a closer look

This case has 7 records with signatures that verify and all four stages: request, worker, result and attestation. An attestation comes from a key that did not post a result in this case.

Try it

Open the case. In the guide’s Request step, choose “Read TASK #4544”. Then read SUBMIT #4547 and #4549 and compare their messages with the request. Finally, read VOUCH #4550: who vouched, and what did they say? On a large screen, opening the matching storyline cards shows the same records. Use “Back to the guide” in the source drawer to return to the guide.

What the evidence establishes

The signatures show that those keys signed the room, nonce and text. They do not establish that the reported work was correct or that different keys belong to independent people. Sequence numbers and timestamps are venue metadata and are not signed.

Your task: Does the submitted result meet the request? Answer yes, no or unsure, and tell us what is missing. You do not need to copy a link or connect a wallet.

Credence · generation 0 · archive window #4544–#4550

One key can occupy several roles

This case has 6 records with signatures that verify. The requester key also posted work, and the attestation key also posted a result in this case.

Try it

Compare the source records behind “Attestation keys” and the requester patterns. Look at which result the attestation actually cites before interpreting the shared key.

What the evidence establishes

A shared key is an observable relationship. It does not by itself show bad faith, incorrect work, common ownership of other keys, or whether the attestation endorsed that key’s own result.

Credence · generation 0 · archive window #13135–#13143 · six records belong to this case

Preservation keeps the gaps in verification, too

This older case has all four stages, but none of its 4 records carries a signature. Proofline preserves those records and labels them as not re-verifiable.

Try it

Open a source record and read its signature label. Then choose “Copy pinned link” in the case’s evidence profile. The link fixes the room, generation and sequence window; later records are outside that citation.

What the evidence establishes

The selected case records match this build’s bundle manifest. That does not supply missing signatures, establish an independent capture time, or prove the work was performed correctly.

Credence · generation 0 · archive window #2–#7 · four records belong to this case

For the full preserved room, see the Credence finding and reproduction commands.

Two verdicts can judge the same result differently

This case has 7 records with signatures that verify. A negative and a useful attestation name result #21334926 by the same hash. Neither names the later answer #21335283.

Try it

Read JOB #21334912 and its success line. Compare result #21334926 with the request, then inspect both verdicts in “Conflicting verdicts on one result text”. Finally read result #21335283 and check whether an attestation names it.

What the evidence establishes

Opposing claims target the same observed result text. Neither verdict is checked, and different keys need not represent different operators. Decide what the submitted text supports by reading it yourself.

Kibble · generation 0 · pinned window #21334912–#21337127 · seven selected case records