SACASE
01Livestock Platform
2026—NOWCLOSE CASE ×
01 / 07Civic technology / Data infrastructure2026—NOW

Morocco Livestock Platform

One animal. One traceable record. Multiple actors who can finally work from the same history.

ROLE
Product architecture · Full-stack engineering · UX
STATUS
Active product build
STACK
Next.js · FastAPI · PostgreSQL · SQLAlchemy · Docker
PRODUCT INTERFACE / 01Public listing
Public livestock listing with animal details and contact actions
PRODUCT JOURNEY / 01

THE PRODUCT,
IN USE.

One complete interface state at a time. Each screen documents the task, the system response, and what the user can do next.

01 / REGISTER

Create the identity

A farmer registers the animal and its base ownership, species, media, and status information.

01Public listing
Public livestock listing with animal details and contact actions
02 / RECORD

Build the history

Weight events, health records, reminders, and veterinary actions accumulate around that identity.

02Animal identity
Animal profile with identity, status, ownership, and health information
03 / VERIFY

Control trust

Role-aware workflows keep professional verification and moderation explicit.

03Growth history
Animal growth page with weight chart and history
01 / CONTEXT

WHY THIS PRODUCT
NEEDED TO EXIST.

CHALLENGE

Animal records are split between farmers, vets, marketplaces, and administrators. That fragmentation makes ownership, health history, weight changes, and listing legitimacy difficult to verify or reuse.

RESPONSE

I designed the product as a modular system around a durable animal identity. Farmer actions, vet verification, marketplace visibility, moderation, and audit history operate as connected states instead of isolated features.

02 / OPERATING LOGIC

THE OPERATING
SEQUENCE.

  1. 01REGISTER

    Create the identity

    A farmer registers the animal and its base ownership, species, media, and status information.

  2. 02RECORD

    Build the history

    Weight events, health records, reminders, and veterinary actions accumulate around that identity.

  3. 03VERIFY

    Control trust

    Role-aware workflows keep professional verification and moderation explicit.

  4. 04CONNECT

    Reuse the record

    The same trusted profile supports daily farm work, public listings, oversight, and future analytics.

03 / PRODUCT DECISIONS

DECISIONS THAT
SHAPED THE BUILD.

01 / DATA

Identity before features

Every weight, health, ownership, media, and marketplace record attaches to one animal profile instead of becoming a disconnected form submission.

02 / TRUST

Verification is a lifecycle

Farmer, vet, and admin permissions determine who can create, verify, expose, moderate, or challenge a record.

03 / ACCESS

Web-first and multilingual

The interface is built for phones and weak laptops, with Arabic/Darija and French requirements shaping layout and content structure.

04 / INTERFACE EVIDENCE

Secondary screens that extend the core journey without diluting it.

05 / 07Farmer dashboard
Farmer dashboard showing livestock totals, vet messages, species distribution, and weight updates
06 / 07Marketplace
Livestock marketplace with filters and verified listings
07 / 07Arabic onboarding
Arabic right-to-left farmer account creation interface
05 / MY RESPONSIBILITY

SCOPE OF
RESPONSIBILITY.

I am leading the product architecture, domain model, API boundaries, responsive interface system, and full-stack implementation across Next.js and FastAPI.

The current build covers farmer onboarding, animal records, growth and health histories, listing management, public marketplace views, vet workflows, and administration. It remains an active product build—not a government deployment.

  • Product architecture
  • Role-based access
  • Marketplace
  • Data integrity
OPEN SOURCE REPOSITORY
NEXT CASE / 02FitFuel AI