# Confirmed launch scope

Confirmed by Viktor on 12 September 2026. This guide takes precedence over older architecture proposals, example payment screens and historical audits in this repository.

## Confirmed decisions

- Build and launch the responsive website first. The native application is a later project.
- Launch equipment, services, parts and materials together. Projects remains retired.
- Materials has two groups: **New materials** from suppliers and **Site surplus** resold by construction companies from their sites. Surplus can include reinforcement steel, gravel, soil and unused blocks.
- KLIGO earns revenue only from **subscriptions and paid placements**.
- Buyers and suppliers arrange their deals, delivery and payment directly. Do not implement KLIGO checkout for those deals, commissions, escrow, seller payouts or a platform guarantee of fulfilment.
- The developer is already part of the team. Source downloads enable development to start; repository, hosting, domain and service-account permissions are granted separately by their owners.
- Marketing campaign execution belongs to the business team. Subscription billing, placement purchase, placement delivery/expiry and access entitlements are developer responsibilities.

## How to interpret existing screens

Discovery, company profiles, listings, contact/request/quote screens and communication are interface references for the lead marketplace. Existing booking, deposit, transaction-payment and payout examples are historical prototype flows, not authorization to build a transactional marketplace. During production integration, remove or adapt these screens, links and claims so buyers are directed to the provider. Confirm which non-payment request/quote status tracking the team wants before implementing it; do not promise reserved inventory or confirmed fulfilment based on local demo state.

Keep subscription and paid-placement billing separate from buyer/seller deal amounts. A successful billing webhook may activate a paid plan or placement; it must never mark a buyer's external deal as paid or confirmed.

## Still needed from Viktor and the team

1. Confirm launch geography, account/approval roles and who handles support and moderation.
2. Approve subscription prices, included features, placement prices/durations, and billing/cancellation rules. Current figures are illustrative.
3. Have the account owners arrange Git, hosting, domain and required service access with the developer. The source ZIP contains no credentials.
4. Supply real listings, photos, company details and final policy text; review English, Hebrew and Arabic wording with native speakers.
5. Review the developer's working release and approve public customer launch after the checklist passes.

These tasks can run alongside development. No Figma conversion is required; the supplied website, components and assets are the implementation reference.