Every return
has a story.
See what changed. Understand why. Govern what becomes official.

- Published Official
- 2.000%
- Current Open
- 2.080%
- Difference
- +8.0 bp
Knowing the number changed is easy.
Knowing why is harder.
Compare the published official snapshot with the current open return. A difference is the starting point for investigation.
EXPLAIN THE DIFFERENCE
Keep the recorded movement and the open remainder in view.
Explore BPS Alpha. Investigate performance, examine movement and daily variance, then follow evidence through governance and lineage.
Explore BPS Alpha
FROM RETURN TO EVIDENCE
Trace the reference. See what remains unverified.
Follow the reconstructed narrative reference while keeping clear that it is not an ingested source record.

DAILY VARIANCE
Find the first divergence.
See when Open first moved away from the published baseline. Select a day, inspect the recorded drivers, and understand what still needs review.
Daily Variance Calendar
Demo Direct Lending · August 2026
Select a date to compare Open with the published baseline.
Business days only · Daily Open vs Published Baseline · values in basis points
ECONOMIC TIME VS. KNOWLEDGE TIME
What happened and when you knew it are not the same thing.
Distinguish when an event happened from when it became known. Both dates matter to the performance story.
Current published result
+8.0 bp difference; proposed restatement awaiting approval
GOVERN THE OUTCOME
Official doesn't mean overwritten.
Keep the published result distinct from a proposed change. Evidence review and approval remain explicit.
Published result retained as the current official state.
Current Open value; not approved or published. Evidence is not independently assessed.
WHAT ELSE DID IT CHANGE?
What else would need assessment?
Understand where a proposed restatement could affect reporting before approval.
Reporting impact requires assessment before approval.
NOT ASSESSEDReporting impact requires assessment before approval.
NOT ASSESSEDReporting impact requires assessment before approval.
NOT ASSESSEDThese consumer categories are examples only. No downstream owner, integration, delivery, or action is represented as configured or completed.
ONE FRAMEWORK, EVERY ASSET
Different assets. One explanation framework.
BPS Alpha does not imply identical calculation models for liquid and private assets. The commonality is the governance and explainability layer above them.
PROVENANCE
Follow the reference chain.
Follow the evidence chain in business and technical terms. Keep reconstructed references and assessment limits visible.
As an investment team sees it
THE OPERATING SURFACE
Review the operational context around a difference.
Bring performance items and pending reviews into one management workspace.

SOLUTIONS / CANONICAL PORTFOLIO IDENTITY
Different systems.
One reviewed portfolio identity.
Bring in permitted source records from governed files. Live API connections require a validated adapter. BPS Alpha compares identifiers, holdings and portfolio attributes, recommends potential matches, and shows the evidence behind each recommendation. An authorized reviewer confirms the mapping before it becomes governed.
INTERACTIVE SYNTHETIC EXAMPLE
From source records to a reviewed identity
01 / BRING IN EVIDENCE
Governed files can supply portfolio identities and holdings without a vendor API connection.
02 / COMPARE & RECOMMEND
Node-and-line illustration · amber = proposed · green = confirmed
Confidence describes the suggested match. Coverage describes the evidence available to assess it.
03 / REVIEW THE OUTCOME
Awaiting comparisonMeridian Direct Lending Fund
PROPOSED IDENTITY / DEMO-MERIDIAN
Source labels alone do not establish that records refer to the same portfolio.
Add example data to inspect the recommendation.
Reconcile identities
Reduce repeated cross-system comparison with one evidence-backed mapping.
Trace decisions
Keep the recommendation, review and supporting evidence together.
Follow the outcome
Use consistent portfolio identity as the foundation for investigation, approval and delivery.
Keep the engines. Govern the outcome. Intended benefits will be measured with design partners; no vendor partnerships or certifications are claimed.
Explore your workflow with us →FROM SOURCE TO ACCOUNTABLE OUTCOME
Follow the evidence. Govern the handoff.
Each stage keeps the context for the next decision. Illustration of the product workflow; delivery follows an authorized approval.
- 01
Source
Permitted files or validated connections
- 02
Evidence
Compare identities and investigate differences
- 03
Approval
Independent review of the proposed outcome
- 04
Delivery
Publish the approved version and track receipts
Source → supporting evidence → reviewer decision → delivery receipt
See what changed.
Understand why.
Review the evidence.
Govern what becomes official.