KADE / Intelligence infrastructure
The embedded intelligence infrastructure layer for capital markets.
An architecture that connects an institution’s existing data, systems and workflows, with each analytical read retained beneath the result.
01 / The problem
Context is lost between systems.A stack
built for record.
Market data, risk models, portfolio systems and research each supply a different read. The desk still has to assemble them into a view of the position.
The hand-offs create reconciliation work and make the path from source to decision harder to reconstruct. Consolidating the records into one system resolves the reconciliation. It does not resolve whether the assembled position should be held.
02 / Architecture
Systems of record remain authoritative.One intelligence layer.
Above the existing stack.
Permitted sources connect through governed interfaces. The intelligence layer returns its result into the applications and workflows the institution already uses.
Read the systems
already in place.
Market data, portfolio systems, risk models, research and internal records supply the permitted inputs. The institution retains its systems of record and the rights attached to each source.
The interfaceGoverned connections and source permissions.
Keep each read
beneath the result.
Individual lenses resolve specific questions. Optional TELESCOPE synthesis retains the underlying reads, including their agreement, conflict and confidence. Optional Policy Intelligence applies institutional rules.
The analytical recordRead, contributing factors, configuration and version.
Return intelligence
to the workflow.
Results can be consumed through the customer platform and chat, through APIs and SDKs, or within existing applications and white-label products.
Explore the Developer Centre ↗︎
The delivery surfaceSelected for the institution’s existing way of working.
Synthesis core: production-ready and running in staging. Lens suite: specified and mapped. No certified sovereign runtime is in production today. Policy Intelligence: specified for Phase 3.
03 / Intelligence
Independent reads. Shared context.Use one Lens.
Or synthesise many.
Specified · Available through the Pilot Programme
Use an individual lens for a specific question. Optional TELESCOPE synthesis combines several reads while preserving the evidence beneath each one.
Portfolio lens
Exposure intelligence
01 / 08What is the book actually exposed to?
A continuous structural read of every holding, weight and classification, resolved into one exposure map.
Exposure · Diversification · Dependency · Drift
Factors and configuration
Factors read
- Position weights
- Sector and geography
- Factor loadings
- Issuer linkage
- Concentration
- Drift
Mandate configuration
Classification scheme, factor model, concentration limits and drift thresholds.
Eight lenses. Different roles. Six provide directional reads. Correlation conditions Risk and Volatility; Liquidity gates proposed action. The institution chooses whether to synthesise them.
Lens suite: specified and mapped. Discuss a pilot ↓
Policy LensesOptional overlays · Phase 3 roadmap
The policy boundary
The institution’s rules.
Applied and evidenced.
Policy lenses are optional overlays that condition every read against a rule set and define the permissible region of the Decision Matrix.
Shariah / Phase 3 roadmap specification.
Roadmap specification. The preview shows the rule boundary; it does not calculate a screening result.
Select a lens to inspect its policy interaction. The institution chooses which lenses to use.
- Rule applied
- The adopted Shariah methodology and screening criteria.
- Configuration
- Screens, thresholds and status rules set for the adopted methodology.
- Evidence retained
- Screening status, reasons, evidence and ruleset version.
04 / Governance
Read → Factors → Configuration → VersionEvery read
opens up.
Retrieval answers what the book holds. Assessment answers whether the position still fits the mandate, and retains the reasoning that produced the answer.
Follow one illustrative position from permitted context to conflicting reads, retained evidence and an institutional decision.
Institutional exampleOne position, from source to decision.
Review the existing position.
A portfolio team asks whether to increase, maintain or reduce exposure. The review brings the position, its mandate and permitted source material together. Systems of record remain authoritative.
- Position and mandate
- Holdings, weights, classifications and the institution’s limits.
- Permitted context
- Market data, risk models, research and internal records, through governed interfaces.
Five reads support.
Three constrain.
The thesis remains validated, but the regime is building, co-movement is tightening and exit capacity is thinning. Those constraints change the combined result; the supportive reads remain visible.
- Supportive reads
- Portfolio, Momentum, Trend, Risk and Opportunity.
- Constraints
- Volatility, Correlation and Liquidity.
Open the constraint
beneath the result.
The Liquidity read reports thinning exit capacity. Its depth, turnover, spread and other contributing factors can be inspected alongside the configuration and retained record.
- Method and context
- Execution horizon, urgency, participation limits and impact tolerance.
- Retained record
- Contributing factors, configuration, ruleset version and run timestamp.
Return the read.
Retain the decision.
Optional synthesis returns REDUCE for this illustrative position, with its supporting reads and constraints attached. The portfolio team reviews the result in its existing workflow and determines the action.
- Analytical result
- REDUCE: the constraints outweigh the supportive reads in this example.
- Institutional decision
- Remains with the portfolio team. No trade or institutional action is specified.
Volatility / Retained read
Calm to building
A building regime is one of three constraints that outweigh otherwise supportive reads.
Volatility / Evidence
The regime is shifting from calm to building.
- Factors
- Realised volatility, implied surface, leverage, clustering, drivers and events.
- Configuration
- Regime definitions, measurement windows, transition thresholds and event calendars.
- Record
- Ruleset version and run timestamp retained. Numeric settings and runtime identifiers are unspecified in this illustrative example.
Provenance ledgerVolatility read · Illustrative
- Institutional context
- Permitted systems of record
- Authoritative at source
- Analytical method
- Volatility lens configuration
- Specified for this example
- Example data
- Website demonstration
- Illustrative
- Record design
- Ruleset version and run timestamp
- Specified record field
VolatilityChanges the synthesis through the regime constraint.
Five supportive reads; three constraints. Illustrative position; no live instrument or recommendation.
05 / Deployment
Three profiles. Set by contract.One platform.
Three deployments.
The institution controls where its data and analytical workloads reside. Select a profile to inspect its processing and data boundary.
Direct institutional engagement. Data residency, analytical processing and access controls are set in the deployment contract.
Technical profile / Select the processing boundary
Hosted
- Processing
- The analytical workload runs in a KADE-controlled environment.
- Data boundary
- Systems of record remain authoritative. Permitted inputs and transfers are defined by the contracted configuration.
- Model and service dependencies
- Hosting, model execution and connected services follow the contracted hosted configuration.
Runtime status. No certified sovereign runtime is in production today.
Commercial scope
Platform access, intelligence entitlement, usage, integration depth, embedding and white-label arrangements are defined separately from the technical deployment profile.
Institutional enquiries
Intelligence infrastructure
for capital markets.
Every collaboration starts
with a conversation.Select your enquiry. Shape your brief.
Tell us about your institution, intended use and preferred deployment setting.
Or contact info@kadetechnologies.com directly.