LIBA Sovereign Intelligence™ · Architectural vision

Your investment history belongs to your firm.

LIBA SI™ protects your decision records with organization-level isolation and role-based access. We’re building customer-managed keys and customer-defined AI policies to give your institution more control over how its data is accessed and processed.

Four pillars

The Sovereign Intelligence™ Vault

Each ring is a pillar; each segment, one control in its current status. Select a pillar to see its controls and technical limits.

Decision Integrity & Provenance

Decision Integrity & Provenance, surrounded by four layers: 01 Private Intelligence Vault (3 verified, 2 in validation); 02 Customer-Controlled Encryption (1 verified, 2 planned); 03 AI Processing Governance (3 verified, 1 in validation, 2 planned); 04 Revocable Access (2 in validation, 1 planned).

Pillar 01

Private Intelligence Vault

Each organization’s records sit behind their own boundary, under role-based authority.

  • Role-based authorityVerified
  • Organization isolationVerified
  • Multi-factor for privileged actionsVerified
  • Organization sign-in rulesIn Validation
  • Scoped read-only API keysIn Validation
Technical detail and limits
Multi-factor for privileged actions
In the Trust Center: Authentication and MFA
Organization sign-in rules
Your administrators can limit sign-in to approved email domains, require a device check, and cap session length and idle time.
Scoped read-only API keys
API keys carry named read scopes only and are stored as hashes, never in readable form.

Each organization is its own tenant. Its records carry its organization key, the database enforces row-level security on tenant tables, and the server checks the organization of every request against the signed-in person’s verified membership.

Demonstration and evaluation workspaces hold synthetic data only and refuse real content.

The complete vault architecture is in development. Existing tenant controls do not mean exclusive customer key custody, a private vector index or protection from an administrator with infrastructure access.

  • Verified
  • In Validation
  • Planned

Decision history that compounds.

Every assumption, approval, override and outcome becomes part of your institution’s memory. Over time the record shows which assumptions held, which did not, and who decided.

See a Decision Record

From your data to your decision.

How your data would move in the full design, and which controls protect it today.

  1. Customer Data
  2. Decision Integrity & Provenance
  3. Encryption and Authorization
  4. AI Processing Policy Enforcement
  5. Approved Intelligence Execution
  6. Private Results
  7. Institutional Decision Record
  1. Protect
  2. Process
  3. Return
Today
Organization isolationVerified
Role-based authorityVerified
Encryption in transitVerified
To come
Customer key authorizationPlanned
AI policy enforcementPlanned

Powered by Continuous Intelligence

Private intelligence. Separate shared evolution.

Private intelligence

Your organization’s documents, decisions, assumptions, outcomes, prompts, corrections, AI outputs, embeddings and usage-derived content are processed only to provide the service to your organization. They are excluded from shared product improvement.

NO AUTOMATIC PRIVATE DATA SHARING.

LIBA Intelligence Evolution™

  • Public market dataIn Validation
  • Synthetic scenariosIn Validation
  • Evaluation benchmarksIn Validation
  • Licensed market dataPlanned
  • Explicitly authorized learningPlanned
Consent terms and limits

A future contribution program would need explicit consent covering purpose, data scope and retention, with an audit record and withdrawal of future contributions; any irreversible downstream effects would be disclosed. No such program is available today.

Not offered today: Federated learning, Differential privacy, Customer-specific model training. LIBA SI™ makes no claim to any of them.

What runs today, and what does not.

The vault above shows each pillar’s controls. Here are the limits that apply to all of them, and what is on the roadmap.

LIBA can access plaintext within the service’s operational trust boundary, and customers do not hold exclusive custody of encryption keys. LIBA SI™ is not a zero-knowledge system and holds no SOC 2 report. Production acceptance for external customer deployments is not yet complete.

On the roadmapCustomer-managed keys · Key rotation under your control · Customer AI processing policy · Attested intelligence execution · Key-based revocationPlanned

View all controls and statuses

Verified7

Operational control supported by the required verification evidence.

  • Role-based authorityPrivate Intelligence Vault
  • Organization isolationPrivate Intelligence Vault
  • Multi-factor for privileged actionsPrivate Intelligence Vault
  • Encryption in transitCustomer-Controlled Encryption
  • Advisory AIAI Processing Governance
  • Model provenanceAI Processing Governance
  • Server-side model configurationAI Processing Governance

In Validation5

Implemented or undergoing verification, with remaining acceptance requirements.

  • Organization sign-in rulesPrivate Intelligence Vault
  • Scoped read-only API keysPrivate Intelligence Vault
  • Metered AI useAI Processing Governance
  • Member deactivationRevocable Access
  • API key revocationRevocable Access

Planned5

Approved architectural or engineering direction that is not yet operational.

  • Customer-managed keysCustomer-Controlled Encryption
  • Key rotation under your controlCustomer-Controlled Encryption
  • Customer AI processing policyAI Processing Governance
  • Attested intelligence executionAI Processing Governance
  • Key-based revocationRevocable Access
Ownership terms and what LIBA SI™ does not claim

Under LIBA SI™’s terms, you keep ownership of the data, documents and records your team submits; LIBA SI™ receives a limited right to process them only to provide, secure and support the service.

  • LIBA SI™ is not a zero-knowledge system. As the service operator, LIBA has technical access to the systems that hold customer data; customer-managed keys are in development. They do not establish exclusive customer control if LIBA can authorize decryption.
  • LIBA SI™ makes no separate claim about encryption at rest; it has not yet been confirmed from the hosting provider’s controls.
  • LIBA SI™ does not publish model providers’ retention terms. Which providers may process your content, and on what terms, is confirmed for each deployment.
  • LIBA SI™ holds no SOC 2 report or other security certification and has not completed an independent security audit.
Full technical reference: LIBA SI™ Trust Center

See the architecture with your team.

Executive demonstration

For investment principals, family offices and investment committees.

A private session on synthetic data: one decision from evidence to outcome, and what protects it today.

Request a Private Demo

Technical security review

For CISOs, CTOs and enterprise procurement teams.

Tenant isolation, roles, sign-in rules, AI configuration and revocation, with the evidence behind each status.

Request a Security Review