User Flow Mickael Rutembya · Flow Atlas

Certificate Detail

/parcours/certifications/<slug>/

Visitor inspects a verifiable certificate: issuer, date, domains, mint transaction or issuer URL, and related CV capabilities. Can filter certificates by year.

User intent

What the visitor is trying to do

« I want to verify this certificate on-chain or with the issuer, and see which CV capabilities it documents. »

Entry points

ElementDestination
Certificate card From ledger/parcours/certifications/<slug>/
NFT verify PolygonScanhttps://polygonscan.com/tx/<mint_tx>
NFT view OpenSeahttps://opensea.io/assets/matic/<contract>/<token_id>
Issuer verify External issuer<issuer_url>
Same year Filter/parcours/certifications/?year=<YYYY>
Related capability Capability detail/expertises/<slug>/

Flow

Adjacent routes — click a node to open it.userflow
flowchart LR Start(["Visitor on CV"]) --> CertDetail["/parcours/certifications//"] CertDetail --> CertLedger["/parcours/certifications/"] CertDetail --> PolygonScan["https://polygonscan.com/tx/"] CertDetail --> OpenSea["https://opensea.io/assets/matic/..."] CertDetail --> IssuerUrl[""] CertDetail --> SameYear["/parcours/certifications/?year="] CertDetail --> CapDetail["/expertises//"] CapDetail --> ContactQual["/contact/#call-qualifier"] ContactQual --> End(["Engagement started"]) click CertDetail "https://mickael-umt.com/parcours/certifications/cert-slug/" "Open Certificate" click CertLedger "https://mickael-umt.com/parcours/certifications/" "Open Ledger" click CapDetail "https://mickael-umt.com/expertises/ai-security/" "Open Capability" click End "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification"

Screen inventory

IDScreenUser task
P0Certificate detailVerify provenance, issuer, mint tx, capabilities
P1Certificate ledgerBrowse all certificates by year and domain
P2External verifierCheck on-chain or with issuer
P3Capability detailReview documented capability

Flow scenario

Scenario C2

Visitor verifies a Polygon certificate

Trigger

  • Visitor clicks certificate from CV or ledger
  • Wants to verify mint transaction

Experience

  1. Certificate detail loads with issuer, start date, domains, token ID.
  2. Visitor clicks "Vérifier la frappe ↗" → opens PolygonScan.
  3. Confirms mint transaction and contract address.
  4. Clicks related capability link → reviews documented capability.

Trust and safety rules

  • Certificates are minted on Polygon; ledger is public and verifiable.
  • Issuer URL and mint transaction are stable references.
  • Certificate detail links to CV capabilities without duplicating content.

Interaction rules

  • NFT certificates show PolygonScan and OpenSea links.
  • Non-NFT certificates show issuer verification link.
  • Related capabilities are rendered as capability rank cards.

Result states

StateWhat the visitor seesWhat happens next
VerifyingCertificate provenance, issuer, mint txVisitor checks external verifier
ExploringRelated capabilities and evidenceVisitor opens capability or returns to CV