ISSUE · DEGREES & CREDENTIALS
Replace the phone call to the registrar with a click.
Somewhere right now an HR officer is on hold with a university switchboard, trying to confirm a degree that was awarded nine years ago. The registrar who can answer is a shared inbox and a three-week backlog. That latency — not fraud, not cost — is the problem education credentials actually have, and it is the one a signed proof removes: the employer clicks verify instead of calling, and the answer is arithmetic, not a favour.
The transcript request, before and after
What happens today
The graduate emails the registry. The registry mails a sealed transcript, or worse, answers the employer's phone call after a verification queue measured in weeks. Each request costs staff time at the institution and stalls a hiring decision at the employer — for a fact the institution settled at graduation and that has not changed since.
What happens with an issued credential
The institution signs the award once, at graduation, and hands it to the graduate. A decade later, any employer on any continent checks the signature in seconds — without contacting the institution, without an account, and without the institution learning where its graduate applied.
Where the standard fits, honestly
Education credentialing has a real standard — Open Badges 3.0, rebased on W3C Verifiable Credentials — and this platform's specification plans it as a sector schema pack a tenant activates instead of designs. Two honest words about that sentence: the pack is planned work, and Open Badges is a standard, not a regulation. Some sectors on this site can point at a law that recognises reusable checks; education cannot yet, and this page will not borrow authority the corpus does not hold.
What an institution would actually be adopting today.
No university issues on this platform today. Issuance for a tenant is operator-run — an institution cannot yet self-serve its own credential types — and the Open Badges pack is planned. The rows below are the measured state of the pieces a registrar's programme would stand on.
- PLANNED A wallet a person installs from an app store. wallet-native You cannot hold a credential on a phone you own. Everything a person would do with a proof waits behind this.
The register holds 17 live · 2 partial · 2 planned · 5 not yet.
4 of the 5 capabilities this page depends on have no row in the register yet, so this page will not print a state for them. They are named rather than dropped, because a slice that silently shortens itself is the same defect as a claim with no receipt.
- vc-issuance
- selective-disclosure
- partner-certification
- self-service-onboarding
The register route serves, but it carries no row for these yet. List what it does carry:
curl -s https://id.orbis.id/api/site/register | jq -r '.entries[].slug'