01
Discover
Identify potentially material developments across primary sources, official statements, filings, data, and reputable specialist reporting.
Editorial and data discipline
Methodology
Signal is designed to preserve source authority, uncertainty, limitations, and correction history while still producing useful operational intelligence.
Publishing workflow
From external development to Signal record
Every published item moves through the same evidence-to-publication sequence.
02
Verify
Check the source, publication time, event date, authority, current status, jurisdiction, and any material conflicts or limitations.
03
Classify
Assign a source type, source status, topics, entities, jurisdictions, impact level, confidence, and commercial data value.
04
Synthesize
Write an original factual summary, domain impact assessment, and separate Keelbase relevance analysis.
05
Link
Connect every published brief to its normalized Signal records so the editorial and structured layers remain traceable.
06
Correct
Preserve material history, publish correction reasons, and use reciprocal supersession fields rather than silently replacing facts.
Controlled vocabulary
Source type is not source status
Source type describes where the information came from. Source status describes what the information currently establishes.
Source types
Primary OfficialPrimary FilingPrimary DataOfficial StatementTrade PressReputable SecondaryCommentary
A source can be primary and still contain only one party’s allegation, proposal, or interpretation.
Source statuses
ConfirmedAnnouncedAllegationProposalCommentaryUnresolved
A complaint is not a judgment. A bill is not enacted law. A proposal is not an operative platform rule. An anomaly is not proof of manipulation.
Information architecture
Four layers stay visibly separate
The interface and record model intentionally prevent factual reporting, interpretation, and known limits from collapsing into one statement.
Factual summary
An original account of the development supported by the cited source and current verification state.
Domain impact
An assessment of the likely operational consequence for agent governance, authorization, commerce, regulation, platform frameworks, infrastructure, or security.
Keelbase analysis
A separate interpretation of why the development may matter to Keelbase systems, references, schemas, guides, agents, or product direction.
Limitations
Missing evidence, source constraints, unresolved facts, incomplete jurisdictional coverage, or other reasons the conclusion must remain bounded.
Corrections and supersession
Material records are never silently overwritten.
The original record remains reconstructable. A replacement identifies what it supersedes, the prior record identifies its replacement, and the correction reason is published.