User Flow Mickael Rutembya · Flow Atlas

Evidence — Projects

/realisations/

Visitor browses public evidence by domain, inspects repositories, audits and proof limits.

User intent

What the visitor is trying to do

« I want to verify public evidence, see attribution levels, and understand the provenance policy behind each project. »

Entry points

ElementDestination
Nav "Preuves"/realisations/
Home "Examiner les preuves publiques"/realisations/
Offer detail "Voir les réalisations"/realisations/
Certificate detail "Voir les réalisations"/realisations/

Flow

Adjacent routes — click a node to open it.userflow
flowchart LR Start(["Visitor arrives"]) --> Projects["/realisations/ (Projects)"] Projects --> Domain["/realisations/<domain>/ (Domain filter)"] Domain --> Projects Projects --> CV["/parcours/"] Projects --> Certs["/parcours/certifications/"] Projects --> Eng["/contact/#call-qualifier"] CV --> Eng Certs --> Eng Eng --> End(["Engagement started"]) click Projects "https://mickael-umt.com/realisations/" "Open Projects" click Domain "https://mickael-umt.com/realisations/ai-data/" "Open Domain" click CV "https://mickael-umt.com/parcours/" "Open CV" click Certs "https://mickael-umt.com/parcours/certifications/" "Open Certificates" click Eng "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification" click End "https://mickael-umt.com/contact/#call-qualifier" "Open Qualification"

Screen inventory

IDScreenUser task
P0Projects listingBrowse evidence by domain
P1Domain filterNarrow to a specific evidence domain
P2Project cardInspect repository, commits, proof limits
P3Career pathRead profile and competencies
P4CertificatesInspect on-chain certificate ledger
P5QualificationSubmit structured call-qualification form

Flow scenario

Scenario E1

CTO verifies AI security evidence

Trigger

  • Visitor clicks "Examiner les preuves publiques" from the home page
  • Filters the projects list by "AI & data" domain
  • Opens a project card with public repository links

Experience

  1. The projects page shows all public evidence classified by attribution level: original creation, substantial contribution, scaffold-based implementation, and owner-attested collaborative work.
  2. The visitor clicks the "AI & data" domain chip to narrow the list.
  3. Each project card shows provenance badge, stack, and links to the repository and commit history.
  4. The visitor clicks "Voir le parcours" to read the CV and verify the experience timeline.
  5. From the CV, the visitor opens certificates to check on-chain verification.
  6. Finally, the visitor submits a call qualification to discuss a potential engagement.

Trust and safety rules

  • All pricing is public and deterministic; no coefficient reaches the browser.
  • The calculator access gate blocks disposable and non-routable domains.
  • Payment pages are blocked by robots.txt and carry no editorial SEO value.
  • No card data touches the server; Stripe hosts the checkout page.
  • Provenance policy is explicit: repository ownership is not enough; audit combines commits, diffs, code, training context and owner attestation.

Interaction rules

  • Mobile fields use 16 px text to avoid browser zoom.
  • Reduced-motion preferences disable nonessential transitions.
  • Language toggle switches FR/EN across all strings.
  • Project links open external repositories in new tabs with rel="noopener".

Result states

StateWhat the visitor seesWhat happens next
BrowsingProjects listing with domain chipsVisitor narrows to a domain or opens a project
VerifyingProject detail with repository and commit linksVisitor cross-references CV and certificates
QualifiedConfirmation with quote contextOwner reviews lead
ConvertedStripe return page with entitlementsBuyer downloads or books