A licence authorises use. It does not attest a signature.
A Gankpo Suite licence is a commercial right: it ties an instance of the software to the party operating it. It says nothing about who signs, or about what is signed. Those questions belong to other authorities, deliberately kept separate.
Four things never to conflate
Gankpo's architecture separates four identities. This separation is not editorial caution: it is enforced by the software, and the licence portal has no structural means of circumventing it.
The licence holder
Who operates the software commercially. A company, a public body, an individual. This is what the licence portal manages — and nothing else.
The instance
Which machine runs Gankpo Suite. Each instance carries its own key and receivesits own licence credential, bound to that key. A commercial right may authorise several machines; none uses another's credential. Copying a licence file to another workstation therefore achieves nothing.
The signer
Who signs personally. Personal signature belongs to the signer's Wallet, on their own device. The Suite prepares and orchestrates; it never signs on anyone's behalf.
The organisation seal
The organisation deliberately committing its own seal. A distinct authority, exercised explicitly, which no licence implies.
In short: holding a licence does not prove a document was signed, and signing a document does not presuppose holding any particular licence. The two facts are independent, and remain so.
How a licence is structured
An operating right belongs to a holder. It carries an edition, a validity period, and a number of authorised instances. Under that right, the holder declares the workstations running the software.
Operating right
├── holder
├── edition
├── period
└── authorises N instances
├── instance A (its own key)
├── instance B (its own key)
└── instance C (its own key)Retiring an instance frees a slot; declaring more than the right allows is refused, with a stated reason. A suspended right suspends all of its instances.
Declared holder, attested holder
A name typed into a form remains a name typed into a form. Gankpo measures identity assurance on an explicit scale, from I0 to I4, and displays it as such.
- I0 — declared identity, not attested. Every holder starts here.
- I1 — identity linked to a local identity document.
- I2 — identity attested by a recognised authority, named.
- I3 — identity attested, with recent validity status.
- I4 — institutional status verified by recognised anchoring.
Two distinct things: the level states the strength of the proof, themethod states how it was obtained — legal registry, authority document, domain control. Controlling a domain proves you administer a DNS zone, not that you are the entity bearing that name: it is a method, never a level.
Confirming an email address is not part of this scale: it proves you control a mailbox, nothing more. And the word "attested" implies a third-party authority, which is then named on screen — an attestation that does not say on whose behalf it is made attests nothing.
Privacy
The licence platform knows about licences and authorised instances. It does not know about documents: not their content, not their fingerprint, not their recipients, not their number. Nothing in its normal operation requires this, and nothing in its structure permits it.
See how it works
A public demonstration walks through the full cycle — holder, operating right, instances, activation, transfer, suspension — using the engine's real rules. It issues no licence and writes no data.