Corbel links source records to the accounts, strategies, policies and people they belong to. Permissions and review history carry through to each solution.
ContactThe Corbel Foundation
Start with source records and quality checks. Link them to investment entities and policies, then use those relationships in reviews, controls and reporting.
Coordinate decisions and action across teams, with a clear owner and permitted scope.
Review · Approve · Assign · Act · Record the outcome
Use the same records, policies and permissions across reviews, controls and reporting.
Mandate oversight · Strategy review · Risk Gateway · Reporting
Evaluate exposure, limits and scenarios against the agreed rules and current evidence.
Limits · Calculations · Scenarios · Data freshness
Define how portfolios, strategies, accounts, positions, policies and review cases relate to one another.
Portfolio → Strategy → Account → Position · Mandate → Policy → Case
Bring source data into a consistent record, with quality checks and traceable history.
Accounts · Orders · Transactions · Ledgers · Documents
Scoped permissions · Isolated access · Approval boundaries · Evidence & audit
Source records connect to investment entities, policy checks and the teams responsible for action. Permissions, isolation and audit apply across all five layers.
A governed loop
A case carries its source, policy and owner. The response stays with the record so the next review starts with context.
A source record and its timestamp.
The account and policy it belongs to.
The approved rule and current evidence.
Update the case and notify its owner.
Evidence and the response return to the record for the next review.
Agent responsibilities
Check each account every five minutes. At 80% limit usage, update the open case for the same account and cause, or create one and notify Risk Ops. Data 60 seconds old or more goes to a data review, never a normal result.
Human responsibilities
The risk owner reviews the evidence, records the response and assigns follow-up. The agent’s permitted actions stop at reading data, updating cases and notifying owners.
Operating principles
Source, timestamp, quality and transformation history stay with the record. Missing or stale data remains visible.
Separate viewing, exporting, approving and executing. Define isolated scopes, approval points and stop conditions for teams and agents.
Keep the policy version, evidence and responsible owner. Define incident handling, suspension and recovery, then retest affected controls when requirements change.
Corbel, configured for you
Share your data sources and goals. We’ll map the connections, controls and next steps.