Submit your institution's URL or select your portfolio profile. Bearing renders the read against your named position, with trace to source on every claim.
The reads composed at production cadence under contracted deployment look exactly like what follows. The output is provenance-grade, supervisor-defensible, and trace-reachable on every load-bearing claim.
Name the position
Credit risk transmission · cumulative across material configurations
Market risk transmission
Operational risk transmission
What the engine is not characterising
Configurations the engine has not characterised against this position because corpus precedent does not exist, or because position composition substrate is not sufficient. The engine produces a null read, not a forecast, where the substrate does not support resolution. Two configurations currently sit in this state — neither is rendered above; both are reachable in the trace workspace.
This is what Bearing produces in a single configuration read against your stated portfolio. Bearing — the deployed product — does this continuously, against your audited Level 1 position, with daily refresh and supervisor-grade trace. It is the standing measurement substrate your ICAAP framework was supposed to have.
Bearing
For institutions ready to subscribe to Bearing operating against their named position from BearingA's infrastructure. Annual contract, daily refresh, supervisor-grade trace.
/bearing → B. Into your stackBearing Licensed
For organisations that want Bearing inside their own measurement stack with the trace chain ending in their audit trail. Foundation, Practice, Enterprise tiers.
/engine → C. ProgrammePartner
For consultancies and systems integrators with corpus-relevant client relationships beginning the partner conversation. Co-brand at Practice, white-label at Enterprise.
/partner →