Lifecycle

Issue → scan → verify → revoke.

The platform is designed around one dependable lifecycle: create an authoritative record, make it scannable, resolve it publicly and preserve every material change.

1

Issue

An approved issuer creates a record under its authorized organization account.

2

Canonicalize

The system normalizes the record into the protocol’s stable data structure.

3

Protect

The canonical record is hashed with SHA-256. Ed25519 signing remains the next production gate.

4

Register

The canonical record, integrity references and audit event are stored.

5

Generate

A QR image is generated containing the public verification URL—not private data.

6

Verify

A scan resolves issuer authority, current state, expiration and stored hash integrity.

7

Revoke

An authorized issuer can withdraw a record and preserve the lifecycle audit trail.

Core implementation rule

Do not expand until issuance → VERIFIED → revocation → REVOKED works reliably.