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

# Product overview

> How Darpan turns setup records into reviewable reconciliation output.

Most of Darpan's work is front-loaded: you build connections, schemas, and rules once, then attach them to a saved run. After that, running and reviewing is the repeatable part. This page maps the product objects and how they connect — [Core concepts](/getting-started/core-concepts) has the vocabulary definitions if you need them.

## Story of a run

1. A user signs in under an active company or tenant context.
2. Darpan opens the **Dashboard**, where saved runs are visible as operational work items.
3. The user selects an existing run or creates a new one.
4. The run points to source systems, schemas, primary ID fields, and optional RuleSets.
5. Darpan stages source data from uploaded files, text payloads, or configured connections.
6. The backend compares records, applies rules, and writes generated output.
7. The user reviews counts, differences, and output files.
8. The next action is explicit: fix source data, adjust schema selection, change rules, or accept the variance.

## Product objects

| Object           | Role                                                                          |
| ---------------- | ----------------------------------------------------------------------------- |
| Dashboard        | Work queue for saved and pinned runs.                                         |
| Ask Darpan       | Search-first navigation for pages, workflows, records, runs, and outputs.     |
| Connection       | Saved access details for systems such as SFTP, NetSuite, and AI providers.    |
| Schema           | Field and type contract for a source file or record payload.                  |
| RuleSet          | Rules-backed classification and decision model for matched records.           |
| Saved run        | Saved configuration for a reconciliation run: source, schema, key, and rules. |
| Generated output | Persisted result metadata and files from a completed run.                     |

## Related docs

* [Quickstart](/quickstart): shortest complete path through the product.
* [Ask Darpan navigation](/getting-started/ask-darpan-navigation): search-first navigation for surfaces and records.
* [Run reconciliation](/guides/run-reconciliation): execution flow for an existing setup.
* [Review results](/guides/review-results): generated output and next actions.

## What Darpan is not

Darpan is not the system of record for source business data. It reads, compares, and explains differences so the owning systems can be corrected or reviewed.

<Tip>
  Specific names for schemas, runs, and connections make run history easier to read later.
</Tip>