drpn-ai/darpan Moqui component. It is mounted inside a Moqui framework checkout at <moqui-framework>/runtime/component/darpan.
Engine model
This split keeps browser workflows thin. The UI asks for a run; the backend validates access, prepares data, compares records, applies rules, and writes output.
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 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.
Rules and schemas
RuleSet, Rule, compare-scope entities, and JSON schema model.
Data access and tenancy
Active tenant scope, permission membership, and generated-output isolation.
Operations and validation
Gradle commands and backend review checklist.