Interface languages
SC-0012026-10-27
Options
English Chosen
Українська Chosen
Ελληνικά
Chosen
English (default) + Українська
Why
English is the language of the documentation and the client; Ukrainian for the team
Technology stack
SC-0032026-10-27
Options
Per layer, from decisions/2026-10-27-system-architecture.md
API contract — npm package · spec as a release asset · generated in each client
jobs — Redis + BullMQ · pg-boss · outbox + cron without Redis
search — PostgreSQL · Meilisearch · OpenSearch
mobile — Expo + EAS · bare React Native
Next.js hosting — ECS Fargate · Amplify
Chosen
Web and admin: Next.js (admin on shadcn/ui, TanStack Table, react-hook-form), Tailwind on tokens, next-intl. Mobile: React Native on Expo with dev builds, Expo Router, TanStack Query, i18next, EAS. Server: Node.js 22, NestJS 12 modular monolith (api + worker), REST /v1 with OpenAPI, Socket.IO chat. Data: PostgreSQL 18 via Prisma 7, search in PostgreSQL, Redis + BullMQ from the first version, S3. Services: Stripe Connect, FCM/APNs, email, Sentry. AWS eu-central-1; how each app is hosted is set by DevOps. Contract: @lrm/api-client from the backend's CI
Why
The client fixed React Native, NestJS, PostgreSQL, React admin and AWS (S-03 §2.2); Next.js for SEO; separate repositories; no better way to share a versioned contract than a package; Redis from the start (operator: «давай зразу робити редіс»); hosting is DevOps' call (operator)
Charts library
SC-0082026-10-27
Options
Not in the first release
Recharts Chosen
ECharts
Chosen
Recharts — in the admin's basic reports and the dashboards; the showcase draws its charts as SVG on tokens in Recharts' shapes
Why
React and SVG, coloured by the tokens' CSS variables; operator's choice
Depth of the showcase
SC-0092026-10-27
Options
full
basic Chosen
Chosen
Basic: Simplified recommended at every section intake
Why
Operator: «Треба згенерувати базовий шовкейс»
Product name on the site
SC-0102026-10-27
Options
Working name
Provena
Aurelle
Chosen
«Luxury Resale Marketplace», short «LRM»
Why
The name is not confirmed by the client; nothing invented in its place
Sample world
SC-0112026-10-27
Options
Proposed cast
other names
Chosen
Every person, company, brand, hub and provider name invented; cities real
Why
Operator: «Всі назви мають бути вигадані і імена також»
Another project’s prototype as design baseline
SC-0122026-10-27
Options
No, stack sample only
Yes, as a starting point
Chosen
No — stack sample only; no design baseline
Why
It is a different product for another client; nothing of its design is used
Color scheme — first proposal
SC-0132026-10-27
Options
Midnight & Champagne (one, simplified)
Chosen
Revised: three proposals
Why
Operator: «Схема має відчуватися преміально і дизайн має відповідати тематиці»
Working order
SC-0142026-10-27
Options
Step by step
batches of independent steps
Chosen
Batches A–F, one gate per batch, each step approved or revised on its own
Why
Operator asked to run showcase subtasks in parallel
Technology and architecture
SC-0152026-10-27
Options
Full dialog
one proposed stack
Chosen
Deferred to a separate dialog with the operator; steps 2, 18, 19 wait for it
Why
Operator: «Технології і архітектуру будем обговорювати в окремому діалозі»
Basis of the showcase
SC-0162026-10-27
Options
Whole documentation
blueprint only Chosen
Chosen
Blueprint only; nothing outside docs/ is read
Why
Operator: «Основа тільки блупрінт, за папку докс не лізь»
Microcopy and tone
SC-0172026-10-27
Options
Full
Simplified
Skip
Chosen
Skipped here, and removed from the showcase skill
Why
Operator: «Цей пункт також забери з самого скіла, він не потрібен зараз»
Illustrations, logo, loaders
SC-0182026-10-27
Options
In order after Foundations
now in separate agents
Chosen
Now, in separate agents, alongside Foundations; loaders once a mark is picked
Why
Operator: «Запусти генерацію ілюстрацій та анімацій та лоадерів в окремих агентах»
Logo — first round
SC-0192026-10-27
Options
Six marks
Hallmark
Ten past ten
Loupe
Seal
Provenance
Second hand
Chosen
Not picked: six more, more interesting and detailed (each with a simplified small version)
Why
Operator: «Згенеруй більше логотипів, цікавих, можливо більш деталізованих»
Typefaces
SC-0202026-10-27
Options
A Cormorant Garamond + Inter Chosen
B Playfair Display + Manrope
Chosen
A — Cormorant Garamond (display) + Inter (text), JetBrains Mono
Why
Engraved-caseback serif with an exact sans and tabular figures for prices; restrained, watchmaking
Logo shortlist
SC-0212026-10-27
Options
18 marks in three rounds
Chosen
Meridian and Armillary shown first; Armillary picked afterwards (SC-004)
Why
Operator likes both and will choose after their meaning is explained
Key screens — section intake
SC-0222026-10-27
Options
Full
Simplified Chosen
Skip
Chosen
Simplified, the mobile app first: the screens the main flows need, drawn on the phone; the web second
Why
Operator: «Мобільний застосунок першим»; basic depth (SC-009); the pilot is the mobile app
Phone screens' scale
SC-0232026-10-27
Options
Web sizes in the phone frame
a compact phone scale
Chosen
Compact: inside a phone frame body 13, a row 14, titles 18–26, controls 40/44, header 48, a tighter 10/14/18/20 rhythm, icons 15, pictures' line 1.15; a thin dark bezel on phones and tablets
Why
Operator: the phone screens looked «грубими і неакуратними»; a phone is read closer than a desktop
Technology — section intake
SC-0242026-10-27
Options
Full Chosen
Full + repositories
Simplified
Chosen
Full, with a section on how the apps share the API contract
Why
Operator: the contract «має бути обов'язково описано в технічному розділі»
Technology stack — shape of the page
SC-0252026-10-27
Options
By layer (clients, server, data, services)
by architectural part
Chosen
By part: Web client (site and admin), Mobile client, Server — each described (what it does, how it is built, how it talks, how it ships) with its technologies; hosting, quality and the API contract shared below
Why
Operator: «описати веб клієнт, мобільний клієнт, а також сервер як три архітектурні сутності»
Security — the status of an open claim
SC-0262026-10-27
Options
Not promised
To be discussed Chosen
Chosen
To be discussed («Обговорюється»): not decided in the documentation yet, to be agreed with the client
Why
Operator: «Формулювання "не обіцяю" не прийнятне, краще "to be discussed"»
Flows — section intake and the list
SC-0272026-10-28
Options
Full · Simplified (Recommended, SC-009) · Skip
the list of ten
Chosen
Full: ten flows — sign-in (register, sign in, forgotten password, staff invitation), then sell, buy direct, chat, offer, buy with inspection, return or dispute; Flow 7 (a sale undone) left out, its visible parts drawn in flows 9 and 10. Built in parallel, gated by batch
Why
Operator: Full; «Будуй кілька флоу паралельно на скільки це можливо»
Flows — the devices of a step
SC-0282026-10-28
Options
Phone only, as described
web and phone side by side
Chosen
Every flow of a buyer, seller or visitor shows each step on the public web (desktop) and in the app (phone) side by side, the same actions numbered alike and lit together; staff flows stay on the admin web only
Why
Operator: «клієнтські флови мають бути також продубльовані на мобільних екранах, щоб клієнт міг глянути і десктоп і мобільну версію»
Rating the seller — a comment or not
SC-0292026-10-28
Options
Stars only, as REV-C01
keep the comment of the key screen
Chosen
Stars only, 1–5, no text; the comment leaves rateSeller on Key screens too
Why
Operator chose the blueprint (REV-C01)
Chat flow — who reports, and why
SC-0302026-10-28
Options
Sofia reports after her own blocked message (No action)
Daniel pushes the sale off the marketplace
Chosen
Daniel's phone number is blocked, then he asks to settle outside the app; Sofia reports and blocks him; Elena sees his blocked-message history and warns him
Why
Operator: the recommended story; a report needs a reason the reader believes
Refund after a failed inspection or a return
SC-0312026-10-28
Options
The item, the rest "To be discussed"
the full amount charged
Chosen
The item's price is refunded; inspection fee and shipping are shown "To be discussed" while Q-022 and Q-029 are open
Why
Operator: the recommended option; SC-026 wording
Ukrainian for "case"
SC-0322026-10-28
Options
«справа» (letters)
«кейс» (admin, flows)
Chosen
«Кейс» everywhere — letters, the badge, the dictionary
Why
Operator: the team’s word, as in the admin sidebar «Кейси»