Farm Operations within an Olive-Oil Traceability Platform
My Producer/Farm module in a five-person traceability project: ownership-protected farm management, private maps, activity journals, and AI action plans that producers review before use.
My role
Producer/Farm module developer
Scope
Integrated local application · Producer/Farm domain
Give producers a reliable record of their farms and day-to-day work, while making selected origin information usable by a wider traceability platform.
02 / My contribution
What I built
Owned the ProducerProfile/Farm domain in a five-person team: data relationships, ownership checks, private maps and uploads, farm journals, public-origin rules, and producer-reviewed AI plans. The other supply-chain modules and shared platform are team work.
03 / Delivery scope
What’s included
Integrated local application · Producer/Farm domain
OliveTrace follows Tunisian olive oil from producer to consumer. I owned the ProducerProfile and Farm domain: Eloquent relationships, validated CRUD, access policies, private uploads and maps, opt-in public origin cards, activity journals, and saved AI advice. Stable farm references connect my module to the team’s harvest, certification, distribution, and consumer modules. Authentication, roles, layouts, and infrastructure are shared platform work. The documented delivery includes automated checks and a local Docker deployment; no hosted deployment is claimed.
Academic team project · Five contributors02 /Product experience
What the product does.
01Producer/Farm module4 capabilities
Owned farm records
Producers manage their own profiles and farms. Ownership policies, service checks, validation, and restricted foreign keys protect domain relationships.
Private maps, selective publication
Owners and admins can inspect exact farm locations. Public origin cards require both profile and farm opt-in, and omit contact details and precise coordinates.
Activity journals
Plan, edit, complete, or cancel farm work with date and water-use validation, overdue indicators, and retained history.
Advice with human review
Save a snapshot of relevant farm facts and validated AI recommendations. Producers explicitly choose which suggestions become journal activities.
02Team integration1 capabilities
Stable integration contracts
Shared farm IDs and selectable-farm rules connect to the harvest module. A public-origin service provides selected provenance data to the consumer module.
03 /System design
How the pieces connect.
System workflow
My module, its boundaries, and the team around it.
The Producer/Farm domain owns farm operations and reviewed advice. Stable references connect it to the shared traceability platform.
My contribution · Producer/Farm operations
People
Producer / adminOwned records or scoped moderation
Authorized requests
Application rules
Laravel + BladeOwnership policies, validated forms, maps, and journals
Eloquent relationships
Domain records
MySQLProducerProfile, Farm, activities, and advice reports
Stable farm references
Integration contract
Farm selector + originEligible farm IDs and opt-in public information
My contribution · Advisory AI workflow
Prepare
Fact snapshotSelected farm and activity data; no contact details or exact GPS
Explicit request
Generate
Configured AI providerGemini, OpenAI, or Ollama adapter
Validate output
Review
Saved reportEvidence-linked recommendations for producer review
Producer adopts a suggestion
Follow through
Farm journalIdempotent activity creation and completion tracking
01A domain within a shared platform
My implementation centers on ProducerProfile, Farm, activity records, and advice reports. The wider application combines five student modules; authentication, common user management, layouts, and infrastructure are shared work.
My module
Producer profiles, farms, private locations, farm journals, and reviewed advice.
Team modules
Harvest/milling/oil lots, laboratory/certification, product/distribution, and consumer traceability.
Integration boundary
Stable farm references, ownership-aware selectors, and a filtered public-origin contract.
02AI is an advisory step
A report stores its input snapshot and validated recommendations. Contact information, precise GPS, activity titles, and free-text notes are excluded from provider inputs. Advice never changes farm records automatically; adoption is an explicit producer action.
04 /In action
A closer look at the build.
Actual project screens and documented visuals. Open any image for the full view.
Archive farms that have linked history instead of deleting their provenance. Foreign-key restrictions and service rules keep downstream references intact.
02
Keeping public and private data separate
Public origin is a deliberately limited view, with explicit publication rules. Private logos, contacts, notes, and exact coordinates stay outside that contract.
03
Working within a team boundary
Documented farm selectors and origin contracts let other modules integrate without duplicating producer data or bypassing ownership and status checks.
06 /The toolkit
Each tool has a job.
Open a technology to see its role in this project.
Application
Laravel 12 + PHP +
Controllers, Form Requests, ownership policies, services, and automated checks.
Blade + Vite +
Server-rendered workspaces and reusable forms within shared Front/Back Office layouts.
MySQL + Eloquent +
ProducerProfile/Farm relationships, foreign keys, retained history, and integration references.
Maps & AI
Leaflet + OpenStreetMap +
Private location picker and farm overview, with explicit map loading.
Gemini / OpenAI / Ollama adapters +
Configurable providers for saved advice; normal farm operations work without AI.
Shared delivery
Docker Compose +
Documented local application and MySQL deployment with persistent storage.
GitHub Actions + SonarQube +
Team pipeline with formatting, SQLite/MySQL tests, coverage reports, and a quality gate.
07 /Delivery notes
The documented scope.
Integrated module
Producer/Farm features operate inside the team application with real MySQL relationships and shared authorization infrastructure.
Repeatable local delivery
The 22 October handover documents the automated pipeline and verified local Docker setup. Public hosting is not confirmed in that handover.
Traceable AI workflow
Saved snapshots, validated outputs, and explicit producer adoption connect advice to follow-up work without autonomous changes.
Explore further
Want to go deeper?
Explore the available resources or talk with me about the design and engineering behind this project.
