Problem
Assembling a credential payload can be non-trivial, and users need to save an in-progress credential and return to it later rather than completing issuance in one session.
Current behaviour
The reference implementation only persists credentials once they have been issued. There is no way to save an unsigned, in-progress credential and resume it.
Expected behaviour
A user can save the current state of a credential they are preparing, list and retrieve their saved drafts, continue editing a draft, and later issue it. Drafts are clearly distinct from issued credentials and are never treated as verifiable until issued.
Scope
Persist a draft credential (the in-progress payload plus the metadata needed to resume, such as credential type and version) with a draft state. Provide create, list, retrieve, update, and delete for drafts, and a path to issue a draft through the existing issuance pipeline. Keep drafts tenant-scoped and separate from the issued-credential record.
Problem
Assembling a credential payload can be non-trivial, and users need to save an in-progress credential and return to it later rather than completing issuance in one session.
Current behaviour
The reference implementation only persists credentials once they have been issued. There is no way to save an unsigned, in-progress credential and resume it.
Expected behaviour
A user can save the current state of a credential they are preparing, list and retrieve their saved drafts, continue editing a draft, and later issue it. Drafts are clearly distinct from issued credentials and are never treated as verifiable until issued.
Scope
Persist a draft credential (the in-progress payload plus the metadata needed to resume, such as credential type and version) with a draft state. Provide create, list, retrieve, update, and delete for drafts, and a path to issue a draft through the existing issuance pipeline. Keep drafts tenant-scoped and separate from the issued-credential record.