Capabilities

We do not write capabilities as adjectives. Each one maps to an executable, inspectable stage—and states what it does not do.

Four capabilities

Four capability pillars

Capability 01

See the full chain

Quotes, filings, news and macro data move along one chain, so any conclusion traces back to its source and timestamp. Content without a source never reaches the conclusion layer.

Capability 02

Pass validation

Factors and hypotheses clear four checks: backtest, forward behaviour, directional stability and cost. Fail any one and it stays in observation, outside the formal view.

Capability 03

Follow through

A published view enters lifecycle tracking. Later facts test whether it holds, needs revision, or has failed—and the outcome is recorded rather than removed.

Capability 04

You decide

The system outputs research, reasoning and boundaries. It connects to no broker, places no orders, holds no position, and owns no outcome. The final action is yours alone.

Workflow

What each step processes

The pipeline matters because the intermediate results are visible. The table lists input, action and output for every step.

StepInputProcessingOutput
01 Market regime Index and volume data; macro and external inputs Regime identification, bull/bear assessment, counter-evidence checks Regime call + invalidation conditions
02 Sector focus Industry moves and capital flows; constraints from step 01 Heat attribution, main-line persistence, rotation detection Focus areas + avoid list
03 Validation Factor library, historical sample, forward window Backtest, forward behaviour, directional stability, cost Passed / Observing / Retired
04 Integrated view Role conclusions, validation status, risk boundaries Merge, record disagreement, set boundaries Integrated view + invalidation conditions
05 Continuous tracking Published views; subsequent market facts Review, mark as held or revised Lifecycle record

Multi-role collaboration

Multiple roles, not one model output

Research is divided across five roles with distinct remits, then integrated by the lead. The point is to surface disagreement: when one role says the regime does not support a view and another says the direction holds, both are recorded rather than averaged into a midpoint.

The goal is not to think one step less for you. It is to make the step you take defensible.

See how the five roles divide the work →

See how the system is validated

After capabilities, the thing worth reading is the bar: the conditions under which we let a conclusion into a formal view at all.

Validation & thresholds System overview