One foundation for every institutional decision
From origination to compliance, Liquidity US reads signals, prices risk and monitors portfolios on one governed context. Every recommendation arrives with the evidence behind it.
One version of everything the institution knows
Formal records and informal judgement, held as one governed context graph: structured, permissioned, queryable. Origination, diligence, structuring, monitoring and compliance each draw on it and each add to it.
Playbooks
The way an institution does the work, held as living practice and applied with precision.
Policies
The standards of an institution, upheld at the moment of decision.
Skills
The judgement of the best analysts, codified for the whole institution to inherit.
Tools
The actions the system can take, from retrieving precedent to testing a covenant or drafting a memo.
Connections
The relationships between every record, linked so that context travels wherever it is needed.
Entities
Every sponsor, borrower, facility and covenant, gathered into a single record.
- Playbooks — encoded flows: Origination, Underwriting, Structuring, Monitoring, Screening, Diligence, Approval, Portfolio review, Amendments, Exit
- Policies — rules & limits: Eligibility, Concentration, Approval gates, Exceptions, Leverage limits, Advance rates, Covenant thresholds, Pricing floors, Sector caps
- Skills — procedures: Credit analysis, Cash flow review, Collateral quality, Benchmarking, Sponsor assessment, Stress testing, Recovery analysis, Covenant drafting, Peer comparison
- Tools — operations: Ratios, Tables, Term extraction, Charts, Waterfall model, Scenario run, Data validation, Document parse, Time series
- Connections — relation types: Ownership, Exposure, Precedent, Lineage, Guarantees, Shared sponsors, Sector overlap, Servicer links, Comparable deals
- Entities — object types: Borrowers, Facilities, Portfolios, Documents, Sponsors, Collateral pools, Tranches, Counterparties, Decisions, Scores
Memory that improves with approval, versioning and an audit trail
Learning candidates are generated only from qualifying signals: an outcome that contradicts a recommendation, an analyst challenge that holds, or a gap that recurs above a threshold. Ordinary usage does not change memory.
Exploration is not learning. Approved changes are versioned. Rejected proposals change nothing and the reason for rejection is captured as a signal.
- Proposed for human approval
- A proposal is a diff against the current knowledge version with the evidence that prompted it. The system drafts the change and waits for a named owner to approve or reject it.
- Versioned and reversible
- Every approved change records the approver, timestamp and triggering evidence. The workflows and live positions the change would affect are shown before approval, so any change can be reversed.
Every recommendation arrives with its working
Work is decomposed into typed steps before execution, each with a declared input and a verifiable output. A use-of-funds assessment is a plan a reviewer can inspect step by step.
Every figure links to the exact position in the source document. Precedent retrieval is explicit and includes the prior decisions that argue against the recommendation.
- Hypotheses tested
- The system states what would falsify its view and runs that check. Below a confidence threshold, or where evidence conflicts, it abstains and routes to a reviewer.
- Attached to the record
- The full trace persists as a decision record on the facility or covenant it concerns, so it is available at the next amendment without being reconstructed from memory.
Deployed inside institutional controls
Cloud, private cloud or dedicated instance, single-tenant, with data residency options.
- Customer-managed keys
- Encryption at rest and in transit under keys the institution holds.
- No migration
- Liquidity US reads from institutional systems of record and leaves them in place. Nothing enters the model unresolved: low-confidence extractions queue for review and do not propagate.
Context that compounds
Every decision, exception and judgement call is retained, attached to the borrower, facility or covenant it applied to. The firm gets sharper with each deal instead of resetting with each management era.
- Retained where it applies
- The reasoning and the committee vote sit on the record the decision was made about.
- Available at the next amendment
- It survives staff changes and flags when the question comes up on the same credit.
One system across the entire deal lifecycle
