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 has the vocabulary definitions if you need them.
Story of a run
- A user signs in under an active company or tenant context.
- Darpan opens the Dashboard, where saved runs are visible as operational work items.
- The user selects an existing run or creates a new one.
- The run points to source systems, schemas, primary ID fields, and optional RuleSets.
- Darpan stages source data from uploaded files, text payloads, or configured connections.
- The backend compares records, applies rules, and writes generated output.
- The user reviews counts, differences, and output files.
- The next action is explicit: fix source data, adjust schema selection, change rules, or accept the variance.
Product objects
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.
Specific names for schemas, runs, and connections make run history easier to read later.
