Lending programs from a demonstration
The loan application still has to be typed into the origination system
A repeating write into a loan origination system or a servicing portal has to stay on your computer: borrower data, credentials, and a delivery you must prove. OpenAdapt compiles a demonstration into a program. Later healthy runs make no generative-model API calls, so that form fill doesn't send the data to a model. VERIFIED means an independent check of the stored application agreed. A Seal is the signed receipt that the application landed.
Keep supported APIs and exports as the primary integration path. OpenAdapt is the remaining GUI write: the form the origination system still makes a person complete. If that write has a usable API, use the API.
A computer-use agent re-plans every run and can type the wrong borrower. On a healthy path this program makes no model call, so it cannot invent a different applicant. If the live record does not match the demonstrated target, it halts before the write. HALTED is not a Seal. A save banner is not a Seal either.
Local is $0. MIT. Hosted is $29/month. Enterprise goes through qualification.
Real application footage
Frappe Lending v16.2.0: one synthetic Loan Application, REST and SQL had to agree
Pinned local synthetic fixture, not a proprietary origination system. All 6 Standard-profile runs created exactly one Loan Application and returned VERIFIED after separately authenticated REST readback agreed with direct SQL and the non-target-state audit. Five qualification fault cases returned HALTED before a consequential write. Model calls: 0. No exact HALT footage was retained.
Guided view synchronized to the exact retained runtime timeline; raw footage remains unchanged.
- 1DemonstrateCapture the task and its evidence.
- 2ExecuteReplay the compiled workflow locally.
- 3Verify or haltProve the effect, or stop for review.
Borrower data stays inside a customer-controlled deployment
Original recordings stay local. Credentials stay on this computer. 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. Any private origination or servicing UI is qualified inside a customer-controlled deployment.
The remaining origination write
Complete a repeated application or servicing step that remains after supported APIs and exports. Compile the demonstrated UI step for the approved queue, form, or portal, then check the stored application independently of the screen.
Wrong borrower is a halt. A green save banner is not proof the application landed. We have not demonstrated a proprietary origination system on this page. The public proof is Frappe Lending.
Qualify one lending write
Bring one repeated UI-only step and the system of record that proves the application landed.