User Flow Mickael Rutembya · Flow Atlas

Project Domain

/realisations/<domain>/

Visitor browses public evidence filtered by domain: provenance badges, stack lines, repository links, and evidence policy section with certificate ledger link.

User intent

What the visitor is trying to do

« I want to see the actual work done in one domain, check provenance levels, and verify public repositories. »

Entry points

ElementDestination
Domain chip Sibling domain/realisations/<sibling>/
All domains link/realisations/
Project card View repositoryhttps://github.com/...
Project card Review commitshttps://github.com/.../commits
Evidence policy Certificate ledger/parcours/certifications/

Flow

Adjacent routes — click a node to open it.userflow
flowchart LR Start(["Visitor arrives"]) --> ProjDomain["/realisations// (Domain)"] ProjDomain --> SiblingDomain["/realisations//"] ProjDomain --> AllProjects["/realisations/"] ProjDomain --> Repo["https://github.com/..."] ProjDomain --> Commits["https://github.com/.../commits"] ProjDomain --> CertLedger["/parcours/certifications/"] AllProjects --> ProjDomain Repo --> End(["Evidence verified"]) Commits --> End CertLedger --> End click ProjDomain "https://mickael-umt.com/realisations/ai-security/" "Open Domain" click AllProjects "https://mickael-umt.com/realisations/" "Open All" click CertLedger "https://mickael-umt.com/parcours/certifications/" "Open Certificates" click End "https://mickael-umt.com/realisations/ai-security/" "Open Domain"

Screen inventory

IDScreenUser task
P0Project domainBrowse evidence by domain, inspect provenance
P1External repoVerify code, commits, diffs
P2Certificate ledgerCheck on-chain certificates

Flow scenario

Scenario P2

CTO verifies AI Security evidence

Trigger

  • Visitor clicks "AI Security" from home page positioning column
  • Wants to see actual public evidence

Experience

  1. Domain page loads with project cards filtered by AI Security.
  2. Visitor sees provenance badges (original, contribution, scaffold, collaborative).
  3. Clicks "Voir le dépôt" → opens GitHub repository.
  4. Clicks "Vérifier les commits" → reviews commit history.
  5. Clicks certificate ledger link to verify on-chain certificates.

Trust and safety rules

  • Provenance policy is explicit: ownership alone is insufficient; audit combines commits, diffs, code, training context and owner attestation.
  • Evidence limits remain visible; confidential work is marked "Détails sous NDA".
  • Certificate ledger is on-chain and verifiable without trust.

Interaction rules

  • Active domain chip has aria-current="page".
  • Project cards show period, name, provenance badge, stack line, and evidence note.
  • Repository links open in new tab with rel="noopener".

Result states

StateWhat the visitor seesWhat happens next
BrowsingFiltered project cards with provenance badgesVisitor opens repo, commits, or certificate ledger
VerifiedExternal evidence reviewedVisitor returns to site or contacts via qualification