Select the coverage
A market has chosen sources, an analytical focus and a publication schedule. Coverage is deliberate rather than exhaustive.
The product · How it works
How Signal Engine works
Signal Engine follows a selected set of sources for a specialist market, records relevant developments as they appear, and keeps their context available over time. Briefs, live views and questions all draw on that retained record.
01
From source to usable context
Each market has a defined scope. The platform turns material from that scope into a record that can be revisited as new developments arrive.
Record developments
Relevant source material becomes structured signals. The reported development, source context and capture time are retained together.
Connect the context
Named actors, market forces and earlier signals help a reader see activity around an organisation or subject over time.
Review the outputs
Briefs, Live Signals, Ask and Market Forces provide different views of the same evolving record.
What appears in each view depends on the sources and time period covered by the selected market.
02
Read a signal in layers
A signal brings the reported development and Signal Engine’s interpretation together. The two should remain easy to distinguish as you read.
Signal · anatomy view
Illustrative only
What the source reported
The development is presented as a concise observation. Open a current signal in the product for the actual claim and its supporting material.
Why it matters
The platform explains the possible relevance to this market. This is an interpretation to assess alongside the source material — not a verified claim on its own.
Sourcepublication
Captureddate and time
Evidenceextract
Assessmentrelevance · certainty
Anatomy only · no fabricated market event
Source and capture time
Show where the material came from and when it entered the record. A source-site link may lead to a publication or feed rather than the exact article; inspect the captured extract for what was actually recorded.
Relevance and certainty
These describe the platform’s assessment of a signal. They are not an external verification of every claim.
Why it matters
A market-specific reading of the development. Keep it visibly separate from what the source reported.
Activity over time
Recent-versus-prior counts describe activity within the monitored coverage. Repeated coverage may refer to the same underlying event.
03
What you can check
The product should make it straightforward to inspect a result before relying on it.
A practical reading checklist
01What is directly reported, and what is interpretation?
02Can I inspect the captured material and its date?
03Is this a new development, or repeated coverage of an earlier one?
04Does the source coverage fit the question I am asking?
A high score or a large count is a reason to look closer. It does not, on its own, establish that a conclusion is correct.
04
Explore the record
Different views help with different questions. Their content is scoped to the selected market and the material available to it.
↗
Briefs
A dated synthesis of developments selected for that edition, with source notes and evidence controls.
↗Live Signals
Browse signals and named entities, with source details, interpretations and recent activity.
↗Ask
Search the stored record. Review the matched signals as well as the short answer.
↗Market Forces
Examine a market force, its explanation and the signals presented as its supporting evidence.
Signal Engine · How it works
A short orientation to the current product