Two-person project, full issue discipline

FlexDriver's app repo was not solo: rong6767 contributed 56 commits of real subsystems — Firebase Crashlytics/Analytics integration (2025-06-18), the user-consent screen and terms (2025-06-04), API response-format handling, recognition-state fixes (#51) — with 新聞 adding 14 more. The split was clean: collaborators took bounded subsystems; the owner kept the core loop, the analytics stack (18/18 commits on analytics_service.dart + tools/), and the marketing site (123/123).

And the process didn't shrink to fit the headcount: numbered issues all the way — #47 (load-car discoverability), #49 (email input), #50 (barcode-first, barcode-first-pivot), #51, #52 (shipping-company layer) — a two-person team running the same traceable commit-to-issue discipline as a large one, visible in the log a year later. Which is the point: the discipline wasn't for coordination overhead — it was for the history being readable, and this note is its beneficiary.

Interview archetype: "how do you collaborate / split work" — bounded subsystems for partners, load-bearing core retained, numbered issues regardless of team size; the arbiter question (there-must-be-an-arbiter-above) never triggered because the pots were never shared.