Source-issued credentials
Future issuers can issue credentials that later verifiers validate directly rather than reconstructing authenticity retrospectively.
Future Issuer Network
From retrospective checks to source-issued trust.
Direct issuance · Status · Revocation · Public verify
The long-term network phase allows universities, boards or employers to issue directly verifiable credentials through the DCS trust layer after the underlying R-Series and shared infrastructure are validated in Phase 0.
Issuer network · future phaseSource-issued trust
Authorized issuerInstitution or employer issues
→Credential proofHash/status/verification URL
→HolderShares permitted evidence
→VerifierChecks status and receipt
This UI position is intentionally future-gated until issuer onboarding and trust-layer dependencies are validated.
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.
Issuer identity
Issuer identity and key/status lifecycle become part of the credential trust path.
Status/revocation
Credential status can be checked without exposing restricted internal reference intelligence.
R-Series seam
Receipt/signature/audit integration remains conditional on Phase-0 repository validation.
Public verification
Future public result shows high-level verification evidence while protecting private reference/profile internals.
Network onboarding
Issuer network is a later maturity phase, after core verification, enterprise hardening and assurance work.
EVIDENCE MODEL
This is a future network phase—not a current production claim.
The UI reserves the product position now so engineers do not need to redesign navigation later, but backend activation depends on validated DCS trust-layer components, issuer onboarding and production security/legal gates.
- Issuer-issued credential receipt candidate: issuer + credential hash + status + verification URL
- Network phase follows enterprise and self-service maturity in the final roadmap
- No dependency on blockchain availability should block ordinary verification logic
- Public verify output must never expose restricted template/profile details
Issuer network · future phaseSource-issued trust
Authorized issuerInstitution or employer issues
→Credential proofHash/status/verification URL
→HolderShares permitted evidence
→VerifierChecks status and receipt
This UI position is intentionally future-gated until issuer onboarding and trust-layer dependencies are validated.
WORKFLOW
From input to defensible evidence.
Bonafide follows the strongest available verification route and resumes only the affected lane when new evidence arrives.
01Onboard issuer→
02Issue signed credential→
03Record status→
04Verify later→
05Expose allowed evidence
DESIGNED FOR
One evidence model. Role-specific operations.
The same underlying case can be viewed differently by institutions, employers, reviewers, operations and candidates.
Universities/boards
Future direct issuance
Employers
Future source-issued employment confirmations
Platforms
Directly verifiable credential consumption
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.