How it works
The path of a work through Artheia is the same for every work, and each step leaves a trace. Here it is in full, including the points where it stops and waits for a person.
A certificate becomes public only when a chip is bound to it.
There is no other way. It is not a rule written in the program that someone could get around from a console: it is enforced by the database underneath, where no direct query steps over it.
The artist registers
Opens a profile. No work can be registered yet: Artheia verifies identity by hand, and until that is done the dashboard opens but stays empty.
The work is filled in and submitted
The details of the work, five photographs, and confirmation that the declaration has been read. While it is a draft it can be changed; once submitted it goes to review and is no longer touched.
A reviewer examines it
Takes it on, and from that moment it is theirs: nobody else works on it alongside them. Six checks, then one decision out of three: approved, returned to the artist with a reason, or refused.
The chip is personalised
The chip receives three keys that exist for it alone, derived from a master key Artheia keeps in a key custody service and that is never written down anywhere. Then it is locked, and the lock cannot be undone.
The chip is bound to the document
The binding checks that the document is the approved one, and ties its fingerprint to the chip. Here the certificate becomes public, and from here the fingerprint is frozen: changing it would mean revoking and reissuing.
The two ways of verifying, and the difference between them
They are not two conveniences for the same thing: they prove two different facts. The reduction happens in the backend, not in the page, so there is no way to obtain the full record without a valid tap.
| Typed code | Tap on the chip | |
|---|---|---|
| What it proves | that the certificate exists | that the certificate is on that object |
| Record | reduced | full |
| Photographs | no | yes |
| Document | no | yes |
- What it proves
- Typed code
- that the certificate exists
- Tap on the chip
- that the certificate is on that object
- Record
- Typed code
- reduced
- Tap on the chip
- full
- Photographs
- Typed code
- no
- Tap on the chip
- yes
- Document
- Typed code
- no
- Tap on the chip
- yes