# Decisions

## 2026-06-18 - Use Supplied Transparent Logo

The interface uses `assets/favicon/crypto-whale-logo-transparent-master.png` as the primary logo because the user requested the largest transparent-background asset.

## 2026-06-18 - Keep Current Build Static For This Iteration

The repository started as a simple static site with no package manifest or framework. This iteration keeps the build static to deliver a working visual foundation quickly while documenting the target Next.js monorepo migration.

## 2026-06-18 - English Product Copy

The technical specification explicitly asks for strong professional English copy. The interface copy uses English, while documentation notes can remain practical and implementation-oriented.

## 2026-06-18 - Analytics-First Safety Positioning

The product avoids guaranteed profit claims and states clearly that Crypto Whale provides market data and analytics only, not financial advice.

## 2026-06-18 - Separate Hero And Terminal Product UX

The landing hero keeps the supplied whale artwork clean. Product functionality lives in lower landing sections and dedicated terminal routes so the first viewport stays premium and uncluttered.

## 2026-06-18 - Static SaaS Shell Before Backend

Auth, billing, settings and admin pages are implemented as static shells first. They document the intended product flows while keeping backend, RBAC, Stripe and notification integrations as explicit next steps.

## 2026-06-18 - Shared Mock Data As Migration Contract

The static pages keep embedded records for browser compatibility, but `packages/mock-data` is now the canonical demo dataset for future API routes, component props and automated tests.

## 2026-06-18 - Access Control Before Auth Provider

Subscription gates and admin permissions are modeled as framework-free helpers before introducing Auth.js, Stripe or backend middleware. This makes the authorization rules testable and portable.

## 2026-06-18 - Mock Notification Delivery Only

Notification helpers validate targets and build deterministic delivery records without sending external requests. Real Telegram, email and webhook providers should be added only behind explicit backend adapters.

## 2026-06-18 - UA Code With Ukrainian HTML Lang

The project uses `ua` in URLs and internal state because the specification requested it. The rendered HTML uses `lang="uk"` for Ukrainian pages because `uk` is the correct HTML language tag.

## 2026-06-18 - Static I18n Runtime Before Middleware

The current project is static, so language routes are lightweight shells and the landing runtime handles URL state, localStorage and a short client-side geo fallback. After migration to Next.js, geo detection should move to middleware or backend headers.