Share approved strategy records without exposing the live portfolio. Corbel checks read-only connections, controls when and to whom records are released, and compares the agreed snapshot with source data.
ContactTrading and reviewed operating records
Approved scope · Agreed delay · Read-only access
Historical evidence for the investment discussion
Agreed snapshot. Defined period. Recorded findings.
Read access within agreed source limits
Selected records, released on your terms
A source check with a defined scope
Product view
Follow Strategy A from read-only sources through its release policy to a source-checked historical snapshot.
What it covers
Keep data collection separate from recipient access. Agree what can be read, when it can be shared and what the final source check covers.
Check existing read-only access, timestamps and opening records against the agreed scope. Keep collection within the source request budget, with clear credential and incident ownership.
Release only approved accounts, fields and periods after the configured delay. Give each recipient separate viewing and export rights without sharing source credentials.
At the final review, compare the selected historical snapshot with available source records. Record matched items, gaps and definitions with the reviewer and verification time.
In practice
Consider a quant manager presenting its own market-neutral strategy to a prospective allocator. The prospect reviews approved historical records while the manager keeps trading through its existing systems.
Check read access and select the accounts and historical period.
Publish approved records after the agreed delay.
The recipient reviews the permitted evidence and raises questions.
Compare the agreed snapshot with source records and retain the findings.
Implementation
Define the inputs, responsibilities and checks for your operation.
Corbel, configured for you
Share your strategy records and disclosure goals. We’ll define the prospect view, release policy and final source check.