cloud-itonami-isic-6491

Open Business Blueprint for ISIC Rev.5 6491: Financial leasing. This repository publishes a leasing actor -- lease intake, jurisdiction assessment, creditworthiness screening and lease-funding disbursement -- as an OSS business that any qualified, licensed lessor can fork, deploy, run, improve and sell.

Built on this workspace's langgraph-clj StateGraph runtime (portable .cljc, supervised superstep loop, interrupts, Datomic/in-mem checkpoints) -- the same actor pattern as every prior actor in this fleet (cloud-itonami-isic-6511, 6512, 6621, 6622, 6629, 6520, 6530, 6820, 6612, 6492, 6920, 6611, 7120, 8620, 8530, 9200, 7500, 9603, 9521, 9321, 8730, 9102, 9103, 9602, 9000, 8890, 8610, 9311, 8510, 9412) -- a second financial-services vertical alongside 6492's credit granting, but for asset-backed lease financing rather than general lending. Here it is Leasing-LLM ⊣ Leasing Governor.

Why an actor layer at all? An LLM is great at drafting a lease- intake summary, normalizing records, and checking whether a lease's own collateral value actually covers its own financed amount at the lessor's own required minimum ratio -- but it has no notion of which jurisdiction's leasing/consumer-credit requirements are official, no license to disburse real lease funding, and no way to know on its own whether an adverse credit flag against the lessee has actually stayed unresolved. Letting it disburse lease funding directly invites fabricated jurisdiction citations, funding disbursed against under-collateralized leases, and an unresolved adverse credit flag being quietly overlooked -- and liability, and financial risk, for whoever runs it. This project seals the Leasing- LLM into a single node and wraps it with an independent Leasing Governor, a human approval workflow, and an immutable audit ledger.

Scope: what this actor does and does not do

This actor covers lease intake through jurisdiction assessment, creditworthiness screening and lease-funding disbursement. It does not, by itself, hold any license required to operate a leasing business in a given jurisdiction, and it does not claim to. It also does not model a full asset-valuation/residual-value-forecasting engine -- no equipment-category-specific depreciation curve, no market-comparable appraisal workflow, no full loan-servicing system (see leasing.registry's own docstring for the honest simplification this makes: a single representative minimum collateral-coverage ratio, not an asset-category-by-asset-category survey of every risk-appetite variant). Whoever deploys and operates a live instance (a licensed lessor) supplies any jurisdiction-specific license, the real asset- valuation and credit-underwriting expertise and the real loan- servicing-system integrations, and bears that jurisdiction's liability -- the software supplies the governed, spec-cited, audited execution scaffold so that operator does not have to build the compliance layer from scratch for every new market.

Actuation

Disbursing real lease funding is never autonomous, at any phase, by construction. Two independent layers enforce this (leasing. governor's :actuation/fund-lease-disbursement high-stakes gate and leasing.phase's phase table, which never puts :disbursement/fund in any phase's :auto set) -- see leasing.phase's docstring and test/leasing/phase_test.clj's disbursement-fund-never-auto-at-any- phase. The actor may draft, check and recommend; a human lessor officer is always the one who actually disburses lease funding. Like 6511/6621/6629/6612/6492/7120/8620/7500/9603/9321/ 9602/9000/9311, this actor has ONE actuation event.

This is the beginning of the README. Read the rest at the original. Read the full README ↗