Repository Map

Internal only

This document contains protected Ikamet operational intelligence. Access restricted to Ikamet team via Cloudflare Access.

The eight repositories

Repo	Domain	Stack	Purpose
ikamet-os-core	—	Markdown	Global doctrine, architecture truth
app-admin	ops.ikamet.com	Next.js	Operational workspace
app-web	app.ikamet.com	Next.js	Customer application layer
app-api	api.ikamet.com	Node.js / Express	Backend orchestration
site-ikamet	ikamet.com	Astro	Immigration authority site
site-ikametsigorta	ikametsigorta.com	Astro	Insurance authority site
site-ikametstaff	ikametstaff.com	Astro	Staffing authority site
docs-ikamet	docs.ikamet.com	Astro Starlight	This documentation site

What belongs where

ikamet-os-core

Global doctrine only. Architecture decisions, workflow definitions, entity models, provider philosophy. Do not implement anything here.

app-admin

Operational UI for the Ikamet team. Customer workspace, renewals queue, task management, communications, timeline, documents. No onboarding UX. No provider calls.

app-web

Customer-facing application. Intake forms, document uploads, checkout, customer portal. No operational tools. No admin features.

app-api

Backend only. Provider integrations, workflow automation, queue workers, authentication, AI orchestration. No UI components. No frontend logic.

site-ikamet / site-ikametsigorta / site-ikametstaff

Marketing and authority content. SEO, AEO, GEO optimisation, acquisition funnels. No operational features. No application logic.

docs-ikamet

Documentation only. SOPs, architecture docs, provider docs, workflow guides. No operational systems. No application code.

Cross-repo rules

• Frontends (app-admin, app-web) call app-api exclusively — never providers directly
• Authority sites have no runtime API dependencies
• ikamet-os-core is read-only reference for all other repos
• Database access is exclusively through app-api — no frontend hits the DB