Lending operations
Move lending operations through the final UI-only mile.
Keep supported APIs and exports as the primary integration path. When a repeated lending operation still ends in a form, portal, or work queue, demonstrate that last-mile step once. OpenAdapt compiles it into a governed local program whose healthy runs make no model calls and whose business effect can be checked independently.
Real reference workflow
From demonstration to verified Frappe write
Synthetic local data, real Frappe Lending interactions, and an oracle outside the replay path.
- 1.0
Demonstrate
Complete one synthetic Loan Application while OpenAdapt captures the browser evidence and input events.

Demonstrate — captured Frappe Lending frames · synthetic local fixture - 2.0
Compile
Turn the demonstration into a parameterized, inspectable workflow with a declared business effect.
workflow.jsoncompiled- workflow
- create-loan-application
- parameters
- email · phone · product · amount · term
- target
- Loan Application form
- effect
- exactly one matching record
- healthy run
- deterministic · zero model calls
Compile — inspectable task contract derived from the recorded synthetic workflow - 3.0
Replay
Execute the compiled steps locally against Frappe Lending without asking a model to reinterpret the task.

Replay — real compiled run · local, model-free, independently checked - 4.0
Verify the write
Check the saved record through a separately authenticated read-only REST session and a direct SQL delta audit.
independent effect evidenceverified- REST readbackexact fields matched
- SQL delta+1 Loan Application
- Collateral auditnon-target digest unchanged
- Execution6/6 compiled trials correct
0 silent incorrect successes0 over-halts0 model callsVerify — three baseline and three cosmetic-drift compiled trials; scoped to the pinned local reference environment
Frappe Lending v16.2.0, Frappe v16.27.0, and ERPNext v16.27.0 were pinned in a local fixture with fictional values. The six compiled trials cover one task on one environment under baseline and cosmetic-drift conditions. The evidence manifest records the exact software, task, oracle, media hashes, and scope. OpenAdapt is unaffiliated with Frappe Technologies Pvt. Ltd.; Frappe is its registered trademark.
Inspect evidence manifestKeep borrower data inside its declared boundary
Original recordings stay local. If a hosted or cross-boundary workflow is enabled, only a sanitized derivative admitted by destination policy may upload; policy can require local review and approval of its exact hash. Live observations can contain borrower data again, so they remain inside the declared managed, BYOC, or on-prem trusted runtime boundary. Browser workflows use the managed path; any private or deployment-specific UI-only gap is qualified inside a customer-controlled deployment.
Where the execution layer fits
- Complete a repeated application, servicing, or operations step that remains after supported APIs and exports.
- Compile the demonstrated UI step for the approved queue, form, or portal inside its declared execution boundary.
- Hand QC and compliance an illustrated report of every run: what ran, what it saw, what changed.
Put one lending workflow into production
Bring one repeated UI-only step and the system of record that proves its outcome. We'll map the deployment, verification, shadow run, and supervised rollout.
Evaluate a workflow