RetailPOS — Architecture + PRD

• What it is: Point-of-Sale platform for retail ("RetailPOS"): sales, inventory, products/kits, multi-terminal stock tracking with overselling protection, offline mode with a sync protocol, desktop cash register. Built on the user's personal fullstack scaffold (same stack as fin_fullstack/shipkit).
• Type / status / role: web-app (+desktop) · active · contributor (architect / spec author) — user wrote PRD/architecture (4 commits, but this is the core of the specification), main implementer — Nuriddinkhuja (23 commits).
• Active period: 2026-01-02 → 2026-02-17 (~1.5 months), 27 commits.

• Monorepo: Turborepo + Bun, .mcp.json (shadcn MCP). Apps: web (Next.js 16 + React 19, next-intl ru/en/uz, Better Auth, Eden Treaty, Tailwind v4), api (Elysia/Bun + Better Auth + Swagger), admin (Next.js), `desktop` (desktop cash register with offline sync). Packages: auth/cache/cli/db/email/entities/eslint-config/typescript-config/ui — identical to user's boilerplate.
• Backend: Elysia + Drizzle ORM + Postgres, versioned modules /src/modules/v1.
• Documentation (core of user's contribution): docs/prd/ — structured PRD: 00-overview (336L), 01-architecture (680L), 02-database-schema (1103L), 03-api-specification (1006L), apps/{desktop-app 717L, admin-panel 873L, sync-protocol 809L}, modules/{sales 466L, inventory 308L, products 548L}, 13-roadmap (487L) + phased roadmap.

Confirmed by commits/PRD (user's authorship):

• Offline-first sync protocol for POS (docs/prd/apps/12-sync-protocol.md, 809L): designed sync protocol for desktop cash register with the server for offline operation — one of the hardest tasks in POS. → distributed consistency design.
• Multi-terminal stock reservation (0e5aaa7, DB schema + API): product kits + stock reservation with overselling protection when multiple registers sell at the same time. → understanding of concurrency/inventory.
• Spec-driven architecture: ~8000 lines of PRD (DB schema 1103L, API spec 1006L) before/alongside implementation — problem statement for team and AI. → tech-lead/architect role.
• Personal boilerplate reuse: RetailPOS bootstrapped on personal Turborepo scaffold (Elysia+Next+Better Auth+Drizzle+Eden) — same foundation as fin_fullstack/shipkit. → systematic and reusable.

• Sessions found: 0 transcripts. The session directory contains only sessions-index.json (no .jsonl). The repo has .claude/ + .claude/commands/roadmap.md (custom roadmap-status slash command, added by the user).
• What was done with AI: spec-driven process — PRD + roadmap + custom .claude/commands indicate that the user tuned AI workflow for the team (agent codes per PRD).
• AI workflow patterns: PRD-first + custom slash commands for roadmap; user as "architect directing AI/team."

• ~8000 lines of structured PRD (architecture, DB, API, sync protocol) authored by the user.
• Fullstack POS with web + admin + desktop + offline sync on one Turborepo.
• Multi-terminal stock reservation (anti-overselling).
• i18n ru/en/uz.