Frame / 02 · boundary map
Rails solve access. What solves understanding?
The intelligence fabric is complementary by construction: every new data service becomes a better signal for the layer above.
ULI / rails
Reach
Bank stack
Control
Owns the customer relationship, consent management, policy and credit decision.
The hard work is often between systems, not inside one system.
Intelligence fabric
Understanding
Reconciles signals, carries uncertainty forward and makes the human decision better prepared.
Not a core replacement. A layer above.
| Capability | ULI / rails | Bank stack | Fabric |
|---|---|---|---|
| Data access | service catalogue + consented pulls | bank-owned integrations | one view across sources |
| Consent | access rail, not decision authority | purpose + borrower record | consent artefact beside evidence |
| Cross-source reconciliation | outside the rail | manual / fragmented | conflict is surfaced, never smoothed |
| Policy interpretation | not the rail's job | rulebook + credit policy | deterministic policy layer |
| Evidence / provenance | service metadata | documents and audit trail | claim → source → transformation |
| Credit reasoning | not the rail's job | credit officer / committee | agents recommend; people decide |
| Post-sanction monitoring | new signals | LMS / CBS views | assumption-linked early warning |
The signal base
The honest constraint
Every new ULI data service is a new signal for the layer above. Complementary to RBIH by construction — and the weak-land-records constraint is precisely a reconciliation problem, which is what this layer does.