Refactor code structure for improved readability and maintainability

README.md

@@ -33,6 +33,7 @@ The monorepo is organized into **Apps** (deployable applications) and **Packages
 │   └── docs-dev/         # Component Documentation & Playground (Storybook)
 │
 ├── packages/
+│   ├── core-api/         # Shared HTTP Client, Observability & Data Services Engine
 │   ├── ui/               # Shared UI Component Library
 │   ├── utils/            # Shared Utilities (Date, Encryption, Core Logic, etc)
 │   └── configs/          # Shared Tooling Configurations
@@ -204,7 +205,40 @@ An isolated environment for developing and documenting UI components.
 
 ---
 
-### 5. `packages/utils`
+### 5. `packages/core-api`
+
+The **platform-agnostic API engine** for the monorepo. Provides an isolated HTTP client factory, a unified observability pipeline (Grafana Faro + OpenTelemetry), and a generic data services engine.
+
+* Consumed by `apps/web`, `apps/landing`, and any future workspace
+* Centralizes all `@grafana/faro-*` and `@opentelemetry/*` dependencies
+* Provides plug-and-play telemetry via `initTelemetry()` + `faroAdapter`
+
+**Tech Stack**:
+
+* Axios (isolated instances, zero singleton pollution)
+* Grafana Faro (RUM, Logs, Error tracking)
+* OpenTelemetry (custom spans, distributed tracing)
+* TypeScript (strict types, module augmentation)
+
+**Key Capabilities**:
+
+| Feature | Description |
+|---|---|
+| 🏭 HTTP Client Factory | `createHttpClient()` — per-app isolated Axios instances with interceptor hooks |
+| 📡 Faro/Loki Baseline | Every request automatically pushes structured logs with `module.key` and `module.action` |
+| 🎯 Custom Spans (Opt-In) | `telemetryContext.customSpanName` creates explicit OTel spans visible in Grafana Tempo |
+| 🛡️ Error Normalization | `ApiError.fromAxiosError()` — structured, serializable error codes for all failure modes |
+| 📦 Data Services Engine | `CommonRemoteDataServices` — full CRUD + lifecycle operations with zero boilerplate |
+
+**Documentation**:
+
+| Document | Contents |
+|---|---|
+| [README.md](packages/core-api/README.md) | Architecture, HTTP client setup, observability strategy, data services, app integration guide |
+
+---
+
+### 6. `packages/utils`
 
 Shared business logic and reusable utility modules that can be consumed across multiple applications. Fully tested using Vitest.
 
@@ -212,7 +246,7 @@ This package is intended to hold non-UI, cross-cutting logic such as date/time h
 
 ---
 
-### 6. `packages/ui`
+### 7. `packages/ui`
 
 Shared UI component library (Buttons, Inputs, Cards, Layouts).
 
@@ -221,7 +255,7 @@ Shared UI component library (Buttons, Inputs, Cards, Layouts).
 
 ---
 
-### 7. `packages/configs`
+### 8. `packages/configs`
 
 Single source of truth for tooling configuration.