The addresses under https://witnly.com/ identify the kinds of signed evidence issued by Ovjera, an independent verifier of the work AI agents do in business systems. They are identifiers (the predicateType of a statement), not an API.
Each piece of evidence is a DSSE envelope with payloadType application/vnd.in-toto+json. The signature is Ed25519 over the DSSE pre-authentication encoding (PAE) of the raw statement bytes; keyid is the SHA-256 of the raw 32-byte public key, in lower-case hex. The digest of an envelope is the SHA-256 of its canonical JSON (keys sorted by bytes, no whitespace).
{"payloadType": "application/vnd.in-toto+json",
"payload": "<base64 of the statement>",
"signatures": [{"keyid": "<keyid>", "sig": "<base64 signature>"}]}
The payload is an in-toto Statement: _type is exactly https://in-toto.io/Statement/v1, and predicateType is one of:
| predicateType | What it is | Time of the statement |
|---|---|---|
https://witnly.com/verification/v1 | Verification of a run | predicate.run.verified_at |
https://witnly.com/undo/v1 | Verification of an undo | predicate.run.verified_at |
https://witnly.com/undo-plan/v1 | Undo plan | predicate.computed_at |
https://witnly.com/posao/v1 | Job record | predicate.vrijeme |
https://witnly.com/token/v1 | Approver token issued | predicate.vrijeme |
The evidence of one Ovjera installation forms a hash chain. Every statement carries predicate.chain = {"sequence": n, "previous": "<digest of the previous envelope>" | null}. For consecutive envelopes A and B, B's sequence is A's plus one and B's previous is A's digest. Sequence 0 has previous: null, and only sequence 0 may.
Evidence issued before Ovjera 0.7.3 carries the same types under https://ovjera.example/ (for example https://ovjera.example/verification/v1). It is the same format and stays valid: verifiers read it as the type of the same name under https://witnly.com/.
ovjera-verify checks evidence with nothing but the public key (or a trust file of keys with their validity periods): signatures, the chain, and that each verdict follows from its findings. An auditor's package bundles the chain of one run with an RFC 3161 timestamp.