Agreed founder split (see Product/Founding Decisions):
| Person | Primary ownership |
|---|---|
| Herry Suryo Nugroho | lakuyo-app (KMP; Android primary), lakuyo-windows |
| Iman Suherman | lakuyo-backend, lakuyo-ios, lakuyo-macos, lakuyo-control-plane, lakuyo-docs (Apple run targets from shared KMP as needed) |
Spec-first sequence
1. Spec / contract change in lakuyo-control-plane
2. Client implementation (Android + iOS + macOS + Windows; backend if cloud)
3. Acceptance against spec (automated + manual) on each client
4. Phase release when all four clients pass — no staggered public rollout
5. Update delivery/implementation-status.md
Simultaneous release (ADR-003)
- Public release gate: A phase ships only when Android, iOS, macOS, and Windows all show ✅ for that phase’s specs in
implementation-status.md. - Internal development: May lead on one platform to prove domain behaviour first, but early access, marketing, and store listings go live together per phase.
- Parity rule: All clients remain bound to control-plane specs — no platform invents divergent business rules.
PR requirements
- Reference specification ID in title/body.
- Do not ship behaviour missing from a spec.
- Cross-link sibling PRs when a change spans repos.
Communication
- Product decisions land in lakuyo-docs first; behaviour changes also update lakuyo-control-plane specs before code.
- Temporary chat decisions are not source of truth until reflected in docs (and specs when behaviour changes).