Trust
Governed by design.
AI assists. Software records. People decide.
Governance
Explicit authority
Who can recommend, modify and approve is defined. Only a named person can authorize a decision.
Recorded changes
Accepted, rejected and changed recommendations are kept with timestamps, connected to the evidence and versioned assumptions behind them.
Advisory AI
Model contribution is recorded as advice, separate from the calculations and from the decision itself. Nothing retrains itself.
Accountability by design
Evidence lineage
The record is designed to keep each source with the decision it supported, so the basis of a decision can be traced.
Audit history
Changes, approvals and timestamps are kept with the record rather than overwritten.
Model accountability
What a model contributed is recorded separately from deterministic calculations and from the human decision.
Document governance
Source materials are attached to the record with which they were used. Supported formats are configured per deployment.
These describe the record architecture. LIBA SI does not claim SOC 2, ISO or other certifications, or completed independent security audits.
Data boundaries
Private by default
Each deployment’s data is private unless the organization chooses otherwise.
Isolated per deployment
Decision history is held separately for each organization and is not pooled across organizations.
Owned by the organization
Each organization owns its decision history. LIBA SI does not train across sponsors’ private Decision Records.
Security architecture and controls are reviewed privately with each deployment.
Private deployment program.
We work with a limited number of real estate sponsors and developers, beginning with one consequential decision workflow.
Request access