2 Sync Notes
Othmane Ataallah edited this page 2026-07-23 09:59:45 +02:00
This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Sync Notes

Newest entry on top. One entry per weekly sync and per integration checkpoint. Decisions made here also land in Decisions within the hour.


2026-07-26 — Kickoff (entry pre-filled: this is the ratification agenda)

Present: PM, API dev (REPLACE name), Web dev (REPLACE), Mobile dev (REPLACE)

Demos: PM ran all three starters live — login → profile on API+web+mobile. /REPLACE

Ratification checklist (tick + note amendments; flip rows in Decisions after)

Foundations

  • Milestones M1M6 + ~2-week rhythm + checkpoint ritual — dates set: REPLACE
  • Mock-first workflow (Prism; auth always real API)
  • Spec-gap review vs Figma assigned (owner: PM + each dev for their screens): push notifications absent · no "my reservations" list endpoint · dashboards are point-in-time (no trends) · attachments have no previews · agenda is day/week (no month grid) · meeting recurrence is create-only

Architecture (per-repo ARCHITECTURE.md)

  • API: layers + package-by-feature confirmed · mapper style = static factories (XxxDto.from) · pagination record owner + shape (early M2) · MapStruct trigger agreed ("only if mapping pain is real")
  • Web: features/ threshold (2nd file) · UI kit via M1 spike issue · vitest trigger ("first real logic util") · ESLint+Prettier chore added to M1
  • Mobile: plain Navigator now, go_router when deep links become real (likely M2 reset-link) · widget-test bar = auth flows + one per major screen

Git & process

  • Trunk-based + squash-merge confirmed (squash set as ONLY merge style in each repo's settings)
  • Daily rebase habit confirmed (vs merge-from-main — pick ONE, no mixing)
  • Tag cadence: PM tags after each checkpoint (v0.<milestone>.0)
  • Review SLA 24h confirmed · what devs do while waiting (next Ready issue)
  • Cross-review experiment from M3 (one small cross-repo review per dev per milestone)
  • Mid-project issue IDs continue each repo's sequence (next free API-xx / WEB-xx / MOB-xx)
  • Error-code + X-Client-Type decisions ratified → spec v1.0.1 authoring assigned to: REPLACE

Engineering agreements

  • Style: .editorconfig law · Spotless parked to M6 · flutter analyze clean pre-PR
  • Testing bars per repo accepted (integration tests default on API; fromJson tests on mobile)
  • Secrets rules read aloud (incl. the "leak → tell PM immediately, no blame" clause)
  • ADR walkthrough done — everyone named one example that needs an ADR and one that doesn't

Amendments & disagreements (record them — they're the point):

  • REPLACE

Actions:

  • PM: flip ratified rows in Decisions to accepted + set milestone dates in Gitea
  • Each dev: complete repo -01 onboarding issue by Tuesday
  • PM: fill remaining Figma links in Ready issues
  • REPLACE

Template — weekly sync (copy for each new entry)

## YYYY-MM-DD — Weekly sync (Week NN)
**Present:**
**Demos (5 min each):** API: … · Web: … · Mobile: …
**Board walk:** M<x> progress <done>/<total>; carry-overs: …
**Blockers:****Decisions:** … (→ also to Decisions page)
**Next week / moved to Ready:**

Template — integration checkpoint (end of each milestone)

## YYYY-MM-DD — M<x> integration checkpoint
**Joint demo flow:** (e.g. M3: create task on web → assign → see on mobile → verify API data)
**Mock → real switches done:****Bugs filed:** #.., #.., … (label kind/bug + area/*; priority set at triage)
**Retro (3 questions):** helped: … · dragged: … · change: …
**Milestone closed?** yes/no; rolled over: …  **Tag:** v0.<x>.0