FoC Wiki

Design and solution docs for Favours on Campus (CS3219 AY26/27 S1, group P23) that live outside the code tree. Service-level design records stay in-repo next to the code they describe.

Wiki pages

• D3 Design — Order & Credit Services — the D3 progress-check writeup (all five parts: Order, Credit, async workflow, containerization, N2H plan + task allocation); open team decisions carried as comparison tables.
• D3 Demo Script — skeleton curl walkthrough for the Week 10 session; fill in as Order/Credit endpoints land.
• D2 Design — User & Supplier Services — answers to the eleven D2 questions as built: roles, schemas, auth/JWT, supplier API. Migrated from Lark 2026-09-29; the Lark original is frozen.
• D2 Demo Script — runnable curl walkthrough: login for a JWT, then every endpoint with accepted/rejected calls per role, UI stopped.

In-repo design docs (versioned with the code)

• architecture.md — high-level service architecture (+ architecture.mmd)
• supplier-service.md — Supplier Service decision record (D1–D8)
• notification-service.md — Notification Service decision record (D1–D31: broker + push, REST API, ingest-time display-name enrichment)
• credit-service.md — Credit Service design
• AGENTS.md — tech stack, conventions, port table, AI Usage Policy

ℹ️ House rule carried over from the repo: docs are AI-disclosure-headed where AI tooling touched them, decisions are made by the team and attributed to their PR/issue, and diffs live on the PRs — wiki pages record decisions, not file manifests.