Intelligence infrastructure for capital markets

One intelligence layer across the systems you already run.

Your systems keep their roles.

Every read keeps its evidence.

See where perspectives agree – and where they differ.

SCROLL ↓
01020304

KADE / Within your workflow

Independent perspectives.
Evidence in view.

KADE is being developed to help portfolio and risk teams examine a market question using multiple analytical lenses. The intended output brings the findings, supporting evidence and differences together for review within the institution’s existing workflow.

Every institution has its own way
of seeing the markets.

Its people work from a shared picture,
however many screens they sit behind.

Questions move from room to room,
each one weighed with care.

KADE brings the wider picture into view,
leaving the decision in your hands.

KADE homepage film

KADE / Intelligence infrastructure

Evidence

Keep the working in view.

KADE in practice

One question.
Different perspectives.

Follow an illustrative portfolio review, from the institution’s question to the evidence considered before a decision.

KADEILLUSTRATIVE WORKFLOW · SYNTHETIC DATA

THE INSTITUTION’S QUESTION

Where could this portfolio become difficult to exit under stressed conditions?

A fictional $100m portfolio. A full-exit scenario over five trading days.

SIMULATED FINDING

Holding C takes 20 days in the assumed stress scenario.

It takes 10 days at the baseline volume assumption. Halving traded volume doubles the estimated exit time to 20 days, beyond the five-day review horizon.

Holdings A and B take two and five days respectively under the same stress assumption.

Human review Check the volume assumptions, market impact and mandate before considering any action. This arithmetic is an explanation of an intended workflow, not a KADE engine result or an execution forecast.

FICTIONAL INPUTS · USD MILLIONS

HoldingPositionDaily traded valueStressed value
A$40m$200m$100m
B$40m$80m$40m
C$20m$10m$5m

Assumptions: sell the full position; daily sales capped at 20% of traded value; stress halves that value. The cap and stress are illustrative choices, not recommended trading parameters.

THREE PERSPECTIVES · DIFFERENT LIMITS

Liquidity

The volume assumptions identify C as the longest exit: 20 stressed trading days.

Volatility

No price-return series is supplied. Volatility cannot be assessed from these inputs; the volume scenario alone does not establish a volatility regime.

Correlation

No joint-return history is supplied. The example does not establish diversification or how correlations change under stress.

Review point A liquidity finding does not establish agreement across the other lenses. Those perspectives remain unassessed until the required evidence is available.

TRACE THE CALCULATION

Estimated days = position value ÷ (daily traded value × 20%). Round up to whole trading days.

HoldingBaseline daysStressed days
A12
B35
C1020

For C under stress: $20m ÷ ($5m × 20%) = 20 trading days.

Source and limits All inputs are invented for this website example. No external market feed or KADE runtime is used. Constant volumes, prices and participation are assumed. Market impact, spreads, costs, settlement constraints and available buyers are not modelled.

Synthetic worked example · intended workflow · no live product output.

Deployment & build status
KADE is in development. The synthesis core is in staging; the initial eight analytical lenses are specified and mapped. No certified sovereign runtime is in production. Hosted deployment is proposed, subject to technical validation and agreement. Hybrid sovereign and fully sovereign profiles are specified and in development; each institutional configuration requires validation.
View build status and deployment options ↗

Select a route to see the proposed onward journey.

KADE / Your institution

Control

The decision stays with the institution.

Let’s talk about
your institution.

Start with the question your team needs to examine. We’ll discuss the relevant systems, information and deployment requirements, then establish whether an evaluation is appropriate.

Request a technical briefing
INSTITUTIONAL PERSPECTIVES

A useful place to begin.

Five questions for retaining the context and evidence behind institutional review.

Get the evidence checklist

Discuss your workflow

Tell us about the question your team needs to examine and the systems it uses. We’ll discuss the requirements, then establish whether an evaluation is appropriate.