> ## Documentation Index
> Fetch the complete documentation index at: https://developers.drpn.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Engineering overview

> How Darpan engineering work is organized and verified.

The Backend engine section explains how Darpan works at runtime. The Frontend app pages explain how the Vue application is shaped as a browser control surface. This section explains how to change either side safely: choose the right repository, preserve contracts, and verify the affected surface.

## Engineering model

Darpan engineering starts from the user workflow, keeps UI and backend ownership separate, uses Moqui XML for service contracts, and verifies the changed surface before broad claims.

## How to read this section

These pages cover implementation context rather than product workflow guides.

> **[Engineering process](https://developers.drpn.ai/engineering/process.md)**
>
> How changes are discovered, implemented, verified, and documented.

> **[Repo map](https://developers.drpn.ai/engineering/repo-map.md)**
>
> Frontend and backend repositories, component paths, and ownership boundaries.

> **[Release discipline](https://developers.drpn.ai/engineering/release-discipline.md)**
>
> Versioning, the release cut checklist, review questions, and verification scope.

> **[Frontend PWA philosophy](https://developers.drpn.ai/engineering/frontend-pwa-philosophy.md)**
>
> App shell, route surface model, command-first navigation, and current PWA boundary.

> **[Frontend design system](https://developers.drpn.ai/engineering/frontend-design-system.md)**
>
> Shared CSS, component, workflow, and page-surface contracts for frontend pages.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.