# KLIGO — developer kickoff and production readiness

Reviewed 12 September 2026. This is the current handoff entry point alongside `DEVELOPER_HANDOFF.md`. Older audit documents describe earlier snapshots; use `CURRENT_ROUTE_INVENTORY.md` for the current route tree and the actual source for behavior.

## Can the developer start?

Yes: the responsive interface and source are ready to use as the implementation reference. Begin with a local build, the decisions below and one working account-to-listing slice. This is not a finished transactional website: sample identities, listings, reviews, prices and browser-local workflows must not become real customer records or commercial claims.

The public share link exposes the prototype; it does not create customer accounts or activate a backend. The source download is runnable. The smaller kit is a reference package, not a second app. Native iOS/Android development is a separate deliverable.

## What to send

1. The public website, with English, Hebrew and Arabic available in its language menu.
2. **Complete website source** from `/design-system#resources`; open `START_HERE.md`, then `kligo-website/`.
3. This readiness guide, `CURRENT_ROUTE_INVENTORY.md`, and `INTEGRATION_CHECKLIST.md` from the ZIP.
4. `API_AND_AUTHORIZATION_CONTRACT.md` and `DATA_MODEL_AND_MIGRATIONS.md` as proposed implementation contracts, subject to the approved launch scope.
5. Brand assets, CSS tokens, responsive components, localization dictionaries, image provenance and tests included in the source. The smaller developer kit contains reference components and documentation.

## Confirmed scope and remaining kickoff decisions

Viktor confirmed website first, all four categories, new/surplus materials, and subscription/paid-placement revenue only. Buyers and suppliers arrange and pay for deals directly. Read `LAUNCH_SCOPE.md` and `MATERIALS_HANDOFF.md`; these override historical booking/payment proposals.

These require Viktor and the developer to agree; the prototype does not decide them automatically. Owners below are roles to assign, not people already appointed.

| Decision | Required agreement | Proposed owner |
| --- | --- | --- |
| First release scope | All four categories ship on the website; native app later. Still confirm geography and customer/provider/staff roles. Projects is retired and must stay out unless separately reapproved. | Viktor + developer |
| Commercial workflow | Direct provider deals are confirmed. Approve subscription/placement prices and entitlements; current prices are samples. No KLIGO deal checkout or commission. | Viktor + commercial owner |
| Accounts | General public identity/sign-in and verified contact method; recovery; company membership; staff roles. Public site access is separate from application authentication. | Viktor + developer |
| Technical ownership | Owner-controlled repository, staging/production hosting, domain/DNS, database/media storage, deployment access and rollback owner. Cloudflare/D1/R2 is the documented proposal, not an activated backend. | Viktor + developer |
| First milestone | Prove sign-in → provider membership → draft listing → review → publication → public listing, with persistence and cross-account access tests. Agree schedule and acceptance evidence. | Viktor + developer |

Payment, messaging, maps and other vendor selection can be resolved before their own implementation slices. Final legal text, real inventory and launch sign-off do not need to delay initial local development with sample data, but are required before the relevant real collection, transaction or public launch.

## Current interface contract

- `/` is the only marketplace entry. `/marketplace` redirects there. `/projects/*` is retired. `/sign-in` is the implemented auth entry; `/login` is not implemented.
- Equipment, services, parts and materials have grid/list/map choices. Company discovery has grid/map. `/providers/[slug]` is the canonical company profile; `/providers` is the company-management/policy hub. Preserve compatibility routes found in the generated inventory.
- Shared map results use `EquipmentMap` and `ListingMap` across categories. Desktop has four cards per page in a compact two-by-two panel. Hover/focus activates the matching pin without adding a card outline or an extra Show on map button. Keep detail/quote/bookmark actions and mobile access. Verify the four-card fit at the approved desktop viewport, keyboard focus visibility and small-height behavior during browser QA.
- Company logos use circular frames and fictional colored identities. The official KLIGO logo is unchanged.
- English/Hebrew/Arabic language selection uses the shared branded dropdown. Translate changed product copy in all three languages. Keep IDs, URLs, model numbers, monetary values and user-authored text intact.
- Hebrew and Arabic use client-side presentation localization, with localStorage selection; initial server HTML is English. This is not multilingual SEO. Agree server locale routing/cookies, localized metadata, hreflang and indexing during production development. Arabic presentation is implemented; independent native-speaker and RTL acceptance remains open. See ARABIC_LOCALIZATION.md.
- MapLibre/OpenFreeMap supplies the current street map. Existing pins represent approximate seed cities, not verified premises. Records without a known city remain in the result list. Retain attribution; select and validate production tiles/geocoding, privacy, limits and fallback behavior before launch. Google Maps is an optional earlier proposal, not an approved migration.

## Handoff inventory and remaining production work

| Area | Included now | Must be implemented or supplied |
| --- | --- | --- |
| Design | Approved logo library, colors, fonts configuration, tokens, buttons, forms, cards, navigation and responsive examples | Browser acceptance at desktop/mobile widths, RTL, keyboard, zoom, reduced motion and loading/error/empty states |
| Source/setup | Routes, components, lockfile, local build scripts, build plugin, tests, source manifest, repository rules | Developer-owned repository/access, staging, CI/CD and production configuration |
| Hebrew | Curated marketplace/customer/provider/public dictionaries, quantity rules, localized labels and bilingual search | Independent native Hebrew/RTL review, production date/number/timezone and server-locale behavior; final legal copy review |
| Arabic | Contextual UI and demo copy, dynamic counts, Arabic search and support intents, RTL controls and Arabic font configuration | Independent native-speaker and browser RTL acceptance; server-selected locale for production. See ARABIC_LOCALIZATION.md |
| Data/API | Seed catalog, client types, proposed entities, migrations plan, endpoint/authorization contracts | Real schema/migrations, persistence, authorization, validation, concurrency and idempotency; remove browser storage as the system of record |
| Identity/companies | Registration, recovery, profile and company flows | Actual identities, sessions, verified contacts, membership roles, account deletion/export and ownership checks |
| Requests/quotes | Interactive workflow reference and local state; booking/payment demos are historical | Durable inquiries and responses, delivery to intended providers, agreed status tracking; adapt historical booking/payment screens to direct provider deals |
| Messages/support/reviews | Demo threads, support and reporting flows | Delivery/notifications, private attachments, moderation staff tools, eligible reviews, rate limits, retention and audit records |
| Payments/ads | Sample plans, prices, billing, campaigns and placement rules | Confirmed subscription/placement-only model; approved price book, merchant accounts, billing integration, verified webhooks, tax/invoices, refunds and reconciliation |
| Assets/maps | Official KLIGO SVGs, fictional company logos, representative images, provenance/credits, external font configuration, working map components | Authorized real photos/logos/inventory, approved asset reuse, production font delivery, confirmed locations and vendor setup |
| Legal/operations | Draft policy pages and proposed operating workflows | Final company/contact details, policy/consent approval, staff ownership, backups, monitoring, incident/rollback process |

## Fonts, images and external dependencies

`app/globals.css` loads Heebo, Assistant and Noto Sans Arabic from Google Fonts. Font binaries and their license files are **not** bundled. Preserve the families and weights; decide whether to retain that delivery method or obtain the fonts and license notices for self-hosting. Do not describe the kit as containing font binaries. Review external font loading as part of performance/privacy acceptance.

`public/catalog/credits.json`, `public/home/credits.json` and `/photo-credits` record photograph sources, modifications and attribution. Category illustrations, edited previews and fictional company marks are demo assets, not evidence of real providers. Review provenance and replace with authorized production assets. The photo-guide PDF is English; the on-screen guide supports Hebrew, Arabic and browser print.

The full source includes `package-lock.json` for exact dependencies. Network access is needed for installation and externally hosted fonts/maps. The exported source strips the hosted project identity and bindings. No password, API key or service credential should be shared in the ZIP or committed; configure credentials through the chosen deployment environment.

## Acceptance before real customers

- Identity and ownership: wrong-user, wrong-company and anonymous access fail; customer/provider/staff permissions are server-enforced.
- Records survive reload and another device; failures are recoverable; duplicate submissions and concurrent quote acceptance cannot duplicate actions.
- Uploads enforce type/size/privacy rules; evidence is private; address disclosure follows the agreed workflow.
- Real email/SMS/message delivery and failure handling are verified. No demo reply implies delivery to a person.
- Subscription and paid-placement payments pass sandbox checkout, failure, cancellation/refund and webhook-replay checks before live mode. Staff can reconcile records.
- Real data and approved claims replace fixtures; sponsorship never confers verification. Legal pages and consent versions are approved before live collection.
- Browser QA covers English/Hebrew/Arabic, RTL, keyboard/touch, mobile/desktop, map fallback and four-card fit. Automated source/render tests do not constitute visual sign-off.
- Deployment, backup restore, monitoring, cost limits and rollback have named owners and evidence.

## Audit evidence and limits

The current kit documents implemented English/Hebrew/Arabic presentation, current routes, feature boundaries and proposed production work. Package verification checks actual archive contents and fingerprints. It does not constitute full browser acceptance, independent native-language review or production backend/security/payment validation. Export time identifies the package, not product approval.