Owner review 44 — the open decisions closed; the build begins (2026-10-16)
Status: Active · Date: 2026-10-16
Answers: "D1 as recommended. D2 bring them back. D3 as recommended. D4 tiebreak label TB (unless there is a universally recognized acronym or abbreviation or word for this), D5 - yes, D6 - yes. C1 - C6: let's all proceed as recommended."
The decisions
| # | Decision |
|---|---|
| D1 | 경기 › 예정 lists only your own sessions. Your clubs' other sessions are in 소식's 일정. |
| D2 | Club events come back as the 일정 label 행사 ("모임" is retired and banned in the copy). A 행사 is titled by its own name ("9월 정모 뒤풀이"); its facts are when, then the place; its tile is a calendar glyph, since the place is free text with no pin. It is for members only, and appears in 소식 and the club's Feed, never in the 홈 Block or 경기 › 예정, which are games. Officers make one from 만들기 (일정 만들기 · 행사 만들기 · 글쓰기). |
| D3 | The status bar is dark over a bright cover: when the mean luminance of the cover's top 100 is above 0.6. It is measured once at upload, with the ThumbHash, and stored on the photo. |
| D4 | TB stays the entry column's label. No universal abbreviation exists. What is universal is the notation: the set reads 7-6 with the tie-break loser's points beside it. Team lines already draw them as a raised number. Plain text (a push, a share, the spoken label) writes 7-6(4), as the ATP and Universal Tennis do. |
| D5 | The roster's role pill on the face is accepted. |
| D6 | The public promise is "tennis clubs" now, with racket sports later. |
Sources for D4:
- UTR, How to record a tiebreak: https://support.universaltennis.com/support/solutions/articles/9000161361-how-to-record-a-tiebreak
- UTR, tiebreak rules and scoring: https://www.utrsports.net/blogs/news/the-ultimate-guide-to-tiebreak-tennis-rules-scoring
The build: C1–C6 proceed
Research traced the code for each item (findings in the build plan, docs/architecture/flat-grammar-v2-migration-plan.md § Build waves). Two facts set the order:
- Database changes go one migration at a time. They share one local Supabase stack, and a
migration upwould apply another change's half-written file. - C6, the flat v2 interface, is not in code at all. There are no S2 tokens and no v2 primitives, so it follows the migration plan's own phases: tokens, then Tag and Choice, then primitives, then pages.
Board changes:
- the 행사 item in 홈's 소식 (filed under 일정, by when it happens) and in the club's Feed;
- 행사 만들기 in the officer's 만들기 menu;
- the white-sky MediaBand specimen with its dark status bar.