Task Flow Mickael Rutembya · Flow Atlas

Projects

/realisations/

Atomic steps for a visitor browsing public evidence by domain, inspecting repositories, audits and proof limits.

Task intent

What the user is trying to do

« Browse the evidence portfolio filtered by domain, inspect repositories, and verify audit limits. »

Entry points

ElementDestination
Home CTA/realisations/
Navigation menu/realisations/
Offer detail evidence link/realisations/

Flow

Adjacent routes — click a node to open it.taskflow
flowchart TD A["Start: visitor clicks Projects"] --> B["Land on /realisations/"] B --> C["View domain filters"] C --> D["Browse project cards"] D --> E["Read project summary"] E --> F{"Filter by domain?"} F -->|Yes| G["Select domain filter"] G --> H["Projects filtered by domain"] F -->|No| I["Scroll through all projects"] H --> J["Click project card"] I --> J J --> K["Land on project domain"] K --> L["View provenance badges"] L --> M["Check stack lines"] M --> N["Inspect repository links"] N --> O["View evidence policy"] O --> P["Click certificate ledger"] P --> Q["/parcours/certifications/"] click B "http://localhost:8000/realisations/" "Open Projects" click K "http://localhost:8000/realisations/cybersecurite/" "Open Domain" click Q "http://localhost:8000/parcours/certifications/" "Open Certificates"

Steps

StepActionSystem response
1Visitor navigates to /realisations/Server renders project cards with domain filters
2Visitor browses domain filtersFilter chips shown at top of page
3Visitor selects a domainProjects filtered server-side
4Visitor clicks a project cardNavigate to project domain page
5Visitor inspects evidence detailsBadges, stack, repos, policy rendered

Scenario

Scenario

CTO verifies AI project evidence

Trigger

  • CTO wants to verify AI project claims
  • Navigates to /realisations/ from home
  • Filters by "AI" domain

Experience

  1. Projects page shows 3 AI-domain projects.
  2. CTO clicks "AI Production Assurance" card.
  3. Domain page shows provenance badges and stack lines.
  4. Repository links point to public GitHub commits.
  5. Evidence policy explains audit and proof limits.
  6. CTO clicks certificate ledger link.

Trust and safety rules

  • All project claims are backed by public repository links.
  • Evidence limits are explicitly stated — no cherry-picking.
  • Certificate ledger links are on-chain and verifiable.
  • Domain filters use stable slugs for shareability.

Interaction notes

  • Domain filter uses query parameter ?domain=<slug>
  • Project cards link to /realisations/<domain>/
  • Page uses CSS grid for responsive cards.
  • Repository links open in new tabs with rel="noopener".

Result states

StateWhat the visitor seesWhat happens next
BrowsingAll projects visibleMay filter or click a card
FilteredSubset by domainMay click a filtered card
VerifyingProject domain detailMay inspect repos or certificates
ConvertingVisitor clicks CTAMoves to contact or offer flow