University/issuer registry
Canonical identity, former names, headquarters, campuses, official domains, portals, contacts, coverage and source evidence.
Verification Intelligence
Know the issuer before you judge the document.
University · Employer · Regulatory · Source Confidence
Bonafide intelligence is a provenance-controlled registry layer: official identities, aliases, locations, domains, contacts, verification routes, historical status and responsiveness are versioned rather than treated as static directory entries.
Bonafide intelligence registryProvenance first
UniversityInstitution record
Campuses · programmes · domains · routes
A1 routeEmployerCorporate record
Aliases · status history · HR channels
Official domainRegulatory intelligenceRecognition and status with effective dates
Historical truth is preserved instead of overwriting old records with current status.
Source-firstAuthoritative routes outrank appearanceMinimum evidenceEscalate only what can resolve uncertaintyHuman gateSerious adverse outcomes require reviewAuditableMaterial actions preserve lineage
WHAT BONAFIDE DOES
Purpose-built verification capabilities.
Each capability is a visible part of the verification workflow—not a hidden AI score.
Employer registry
Legal names/aliases, registrations where relevant, locations, domains, HR channels, entity relationships and status history.
Professional registry
Licensing bodies, registration types, status routes and jurisdiction context.
Regulatory history
Time-versioned recognition/status at the narrowest defensible institution/campus/programme/mode/period level.
Verification route registry
A1/A2/B/C/D provenance classes determine what can power automated or reviewed outreach.
Responsiveness intelligence
Median/p90 response time, success rate and follow-up count become operational source intelligence.
EVIDENCE MODEL
Provenance is part of every intelligence record.
A contact, domain or recognition record is not just a string in a database. It carries source class, retrieval/verification time, last reconfirmed status and historical changes so the verification route itself can be defended.
- A1 official regulator/issuer-controlled verified source: eligible for automated outreach
- A2 issuer-controlled domain/subdomain or documented official department page: eligible for automated outreach
- B partner-confirmed with supporting evidence: human review before automation
- C credible public lead: research only
- D applicant/agent supplied or third-party directory: never independent confirmation
INTELLIGENCE RELATIONSHIPSSource-linked, time-aware
Credentialcase context
Issueridentity + routes
Regulatoreffective status
Document versionyear + variant
Source evidenceprovenance + time
WORKFLOW
From input to defensible evidence.
Bonafide follows the strongest available verification route and resumes only the affected lane when new evidence arrives.
01Acquire source→
02Classify provenance→
03Human/agent validation→
04Version record→
05Serve trusted route
DESIGNED FOR
One evidence model. Role-specific operations.
The same underlying case can be viewed differently by institutions, employers, reviewers, operations and candidates.
Verification teams
Faster source resolution without manual web searching
Data operations
Change monitoring and provenance approval
Enterprise customers
Transparent source and coverage context
DECISION DISCIPLINE
Unknown ≠ fake.
Unmapped issuer, new template, legacy document or unavailable source must route to uncertainty/manual verification rather than an automatic accusation.
DCS BONAFIDE · CREDENTIAL INTELLIGENCE PLATFORMEstablish what is bona fide.