Darpan’s UI is the control surface. The backend is the engine that makes each run durable, scoped, repeatable, and reviewable. The backend implementation is theDocumentation Index
Fetch the complete documentation index at: https://docs.drpn.ai/llms.txt
Use this file to discover all available pages before exploring further.
toaditi/darpan Moqui component. It is mounted inside a Moqui framework checkout at <moqui-framework>/runtime/component/darpan.
Engine model
| Layer | Responsibility |
|---|---|
| Moqui | JSON-RPC transport, service contracts, entity persistence, security, session context, and XML-first orchestration. |
| Spark | Dataset normalization and comparison for files or records that exceed browser-memory workflows. |
| Drools/KIE | RuleSet compilation and execution for configurable matching, classification, and exception logic. |
| Generated outputs | Persistent result metadata and files that let users reopen, audit, and delete run evidence. |
Current shape
- Moqui component descriptor:
component.xml - Public service surface: Moqui JSON-RPC services through
/rpc/json - Service contracts: XML service definitions under
service/** - Data model: Moqui entity definitions under
entity/** - Processing helpers: Groovy and Java code under
src/main/groovy/** - Reconciliation engine: Spark-backed compare services with RuleSet and legacy mapping paths
- Rule engine: Drools/KIE services for compiling and executing reconciliation rules
- Output handling: generated-output descriptors plus tenant-scoped files
What the backend owns
- User, company, tenant, and permission checks before reads or writes.
- Durable records for schemas, saved runs, RuleSets, compare scopes, connections, and output descriptors.
- Source staging from uploads, text payloads, or configured systems.
- Spark-backed base diff computation.
- Drools-backed RuleSet execution.
- JSON-RPC responses shaped for the UI.
UI contract
The UI treats facade services as the contract. Browser code does not recreate reconciliation rules, tenant filtering, output paths, or service-side validation. This section traces product workflows into backend services, entities, processing helpers, and validation commands.Component layout
Moqui component structure, dependencies, and implementation directories.
Service layer
Facade services, core services, and backend service orchestration.
Reconciliation engine
A run from source staging through Spark, RuleSets, and generated output.
Data access and tenancy
Active tenant scope, permission membership, and generated-output isolation.