How meckss/foc works
FoC is documented as a campus errand platform with a closed credit economy: a student requests a pickup, another student fulfils and delivers it, and credits circulate within the platform. The repository names four service boundaries, but the sampled source only shows a starter frontend; service internals and inter-service wiring are not evidenced. The frontend page renders a button, and its layout wraps the page. Accordingly, the graph shows the documented product workflow separately from the known frontend behavior, without inventing service calls.
Main entry points: supplier-service Store pickup · page.tsx Starter home page · order-service Errand request · layout.tsx Root layout
Components 13
Frontend
- Starter home page
frontend-service/app/page.tsx - Root layout
frontend-service/app/layout.tsx - Button component
frontend-service/components/ui/button.tsx
Service boundaries
- User service
user-service - Supplier service
supplier-service - Order service
order-service - Credit service
credit-service
Errand workflow
- Errand request
order-service - Store pickup
supplier-service - Campus delivery
order-service - Closed credit economy
credit-service
Other components
- Requesting student
- Fulfilling student
Connections 7
- Root layout → Starter home page: renders
- Starter home page → Button component: renders
- Requesting student → Errand request: requests
- Errand request → Store pickup: needs collection
- Fulfilling student → Store pickup: fulfils
- Store pickup → Campus delivery: delivers
- Closed credit economy → Fulfilling student: credits circulate