Skip to content

Explore market signals before they become outcomes.

Explore public market context, save the view, and promote decision-critical signals into scoped outcomes.

Outcome Receipt
Example result
Vendor coverage check
sample receipt
Method
Coverage mapped
owned and public sources
Method
Exceptions reviewed
human check attached
Source
Source file
client-provided material
Source
Public record
retrieval details retained
Receipt checkedchecks / sources / full trail

What are CMD+RVL Signals?

CMD+RVL Signals is a public-data workspace for market context. Teams use it to test timing hypotheses, preserve source-aware state, and identify views worth promoting into discovery or a working outcome.

Evidence-aware exploration

Signals is CMD+RVL's discovery layer. Analysts and agents use it to explore timing, behavior, and regime shifts with trusted public series before any view becomes an outcome.

  • Curves & calendars

    Rates, events, and timing together.

    Unify Treasury, SOFR, mortgage rates, CPI, auctions, and policy calendars into short-horizon views. Built to show when conditions change, not just whether series correlate.
  • Shareable analytical state

    One view. One context. No drift.

    Saved Signals preserve series selection, parameters, time window, and lineage so collaborators see the same context from a shared link.
  • Fast iteration

    Test, compare, and discard quickly.

    Compare regimes, overlay events, change horizons, and capture snapshots in minutes without locking conclusions in too early.
Signal Library

Public examples, not abstract demos.

The library starts with bounded public-data examples that show the shape of a CMD+RVL signal: the question, inputs, threshold, current read, and path to a working outcome when the view becomes decision-critical.

Public-data beta

Resin Procurement Watch

A procurement signal page for HDPE resin pass-through pressure, built from public inputs and published with a clear utilization gate.

Published read

The published proof page shows a yellow: wait read because utilization sits below the pass-through confidence gate.

Why it matters

It shows how a real market question can become a shareable signal with visible assumptions before any client-specific data enters the workflow.

Signals is a low-commitment practitioner surface. Discovery and workshops are where CMD+RVL qualifies whether a signal should become a client-specific outcome with receipts, operating mode, and delivery scope.

How Signals fits into outcome delivery

Signals is exploratory. It helps teams decide what is worth shaping in Cairn, qualifying in discovery, or turning into a working outcome.

Explore

Use Signals to test hypotheses, understand timing, and separate noise from signal using explainable, event-aware views.

Align

When a view stabilizes, Signals preserves sources, assumptions, freshness, and coverage so the next conversation starts from the same context.

Promote

When a signal becomes decision-critical, bring it into discovery so CMD+RVL can qualify the outcome, evidence needs, operating path, and proof record.
  1. Identify when rate moves begin translating into real borrower or issuer behavior.

  2. Distinguish narrative shifts from actual regime change using a small, trusted set of indicators.

  3. Decide which views are important enough to turn into working outcomes.

Signals help you explore what is changing. Discovery decides whether the view should become a working outcome with receipts.

Signals questions

How does Signals help teams use public data?

CMD+RVL Signals is a public-data workspace for market context, timing hypotheses, and shareable analytical state before a view becomes an operated outcome.

Is Signals an operated outcome?

No. Signals is exploratory. It shows public-data context, assumptions, and current reads; discovery is where CMD+RVL decides whether a signal should become a client-specific outcome with receipts and operating scope.

What data does Signals use?

Signals uses bounded public market and event data, such as rates, calendars, policy events, and selected source-backed series that help explain timing and context.

When should a signal move into discovery?

A signal should move into discovery when the view becomes decision-critical, needs client-specific evidence, or needs repeatable delivery into an internal workflow.

Built for scrutiny, not screenshots

Signals applies the same discipline used across CMD+RVL outcomes: explicit sources, visible assumptions, and explainable context, while keeping exploration separate from authority.

  • Explainable context

    Lineage, coverage, freshness, and latency are visible on every view so exploration can be checked and shared.
  • Methodology transparency

    Derived measures include clear methodology notes so assumptions are explicit before conclusions harden.
  • Clear boundary to outcomes

    Signals never claims authority. When certainty is required, outcomes take over with scoped delivery commitments and receipts.
Built for
  • Hedge Funds
  • Asset Managers
  • Credit & Structured Finance
  • Macro Strategy
  • Risk Management

Explore freely. Promote to outcomes when it matters.