02
BEARING
LICENSED
Bearing Licensed · into your infrastructure
Posture · audited
Trace · ends in your audit trail
Endpoints · three

Bearing wired into your own measurement infrastructure. Audited posture, internal analytical owners, trace chain ending in your audit trail.

Footprint · light
Discipline · heavy

For organisations that want the engine inside the stack, not as an external subscription. Light integration footprint. Heavy methodology discipline.

01 /WHAT IT
IS

The architectural distinction.

Same engine · different topology
01.1
DEPLOYED
INTO YOUR STACK

Bearing Licensed is Bearing operating against your named positions, integrated into your measurement infrastructure under your security perimeter, with the trace chain terminating inside your audit trail rather than in BearingA's. The engine is the same engine — same corpus, same statistical floor, same trace architecture, same cannot-be-wrong commitment. What differs is the operational topology and the audit-trail terminus.

This is the architecture institutional buyers select when their internal stack requires the substrate inside the perimeter rather than as an external dependency — banks whose risk-systems posture requires audited internal deployment, asset managers whose investment-committee infrastructure assumes internal analytical ownership, family offices whose private-market exposure analysis requires the engine operating against books the institution does not externalise.

Light integration footprint by design. Three endpoints. A senior engineer wires it in a week. The depth is in the methodology validation and the security perimeter, not the codebase. Heavy methodology discipline by design. BearingA's methodology team partners with the institution's risk-infrastructure team through deployment kickoff, methodology validation, and corpus-extension cycles where the institution's portfolio surfaces gaps in the canonical substrate.

02 /THREE TIERS
IN SCOPE

Foundation, Practice, Enterprise.

Tier scoped · in conversation
02.1
DEPTH OF
EMBEDDING

Foundation

Single workflow
The engine deployed into a single named analytical workflow. The configuration characterisation, the cascade engine, the trace to source on every claim, operating against the institution's named position. Full methodology validation at deployment kickoff.

Practice

Two–four workflows
The engine deployed with methodology partnership across two to four workflows. The cascade composition, the trace architecture, the corpus-grounded threshold management. Validation cycles against the institution's positions. Foundation depth extended.

Enterprise

Across analytical infrastructure
The engine deployed across multiple analytical workflows with full audit-trail integration. Corpus-extension cycles scoped into the contract. Methodology validation cadence defined. Joint analytical operations at production altitude.

Each tier carries the same engine and the same methodology discipline. The differentiation is in the depth of embedding, the breadth of workflows, and the contractual scope of the corpus-extension and methodology-validation cycles. The cannot-be-wrong commitment travels at all three tiers — what differs is how much of the institution's analytical infrastructure operates against the engine.

03 /TWO
CHANNELS

Direct and Partner.

Same engine · same trace
03.1
PROCUREMENT
SHAPE
A. Direct

The institution licenses the engine into its own measurement infrastructure.

Audited posture under the institution's own security architecture. Internal analytical owners. The trace chain ends inside the institution's audit trail. Annual contract directly between BearingA and the institution.
B. Partner

The engine is deployed by a consultancy or systems partner into their client base.

White-labelled where the partner's contract with the client requires. The partner operates the client-facing surface; BearingA validates the partner-built corpus extensions against the Method before the partner ships. The cannot-be-wrong discipline travels with the engine end-to-end.

Both channels operate against the same engine, the same methodology discipline, and the same architectural commitments. The choice is procurement-shape — the institution that prefers direct contractual relationship and internal deployment selects Direct; the institution working through an existing consulting or systems-integration relationship selects Partner. BearingA validates either deployment against the Method before production cutover.

04 /INTEGRATION
POSTURE

Three endpoints, one week.

Depth · in methodology + security
Not · in the codebase
04.1
WIRE
POINTS
01ENDPOINT
POSITION SUBSTRATE
Position substrate ingestion. The institution's named positions, audited Level 1 holdings, exposure surface composition. Authenticated. Encrypted in transit and at rest. Audit-trail logged.
02ENDPOINT
READ DELIVERY
Configuration read delivery. Bearing's output against the position substrate, rendered in the institution's required grammar (supervisor register, IRP register, operational register). JSON-structured with the trace chain composed in.
03ENDPOINT
TRACE RESOLUTION
Trace-to-source resolution. Every load-bearing claim drillable through the endpoint to the corpus citation and, where applicable, the primary document. The cannot-be-wrong commitment made operationally legible to the institution's diligence team.
Security posture
Composes against the institution's existing infrastructure standards. SOC 2 Type II reference architecture available; institution-specific compliance posture scoped at deployment kickoff. Penetration testing and security review composed jointly with the institution's security function before production cutover.
CTA The tier, the channel, and the integration shape compose in the onboarding instrument scoped to the institution's named deployment context. Pricing operates inside the populated specification. Speak to BearingA — Engine licensing