Signals
Devplan extracts signals from connected meetings, discussions, tickets, and documents. A signal captures a customer problem, request, constraint, or decision with links to its sources, so useful details are easier to find after the original conversation.
Signals are not raw messages or a list of commits. Code changes have their own summaries in Changelog.
Review signals
Open Knowledge → Signals, use the available search and filters to find relevant observations, and inspect their source references. Read the original context when the exact wording, speaker, or timing matters.
A signal may capture a customer problem, a request, a constraint, or a decision discussed by the team. It can inform insights, proposals, project analysis, and answers from Weaver.
Interpret the evidence
Check the period covered and whether multiple observations come from the same event. A summarized request is not proof of widespread demand, and a decision discussed in a source is not necessarily an approved commitment.
If expected signals are missing, check the source's configured scope and processing status. Not every source item produces a separate signal.