Signal Map shows whether a problem is local, repeating, systemic, blocked, or still weak. It helps users see the shape behind many small observations.
Reports and files keep the evidence close to the work. Notes, uploads, PDFs, photos, reports, and proof should stay connected to the venue, task, plan, or signal they came from.
Show recurring signals across venues with a trace, a generated report, file context, and a saved plan basket.
What the user does
The path should stay traceable: observation, signal, plan, proof, report, outcome.
A user can inspect a signal across venues, open the trace behind it, read a generated report, attach files, save useful context, and ask SANDR what the evidence supports.
Show recurring signals across venues with a trace, a generated report, file context, and a saved plan basket.
Show observation, mapped signal, plan coverage, and uncovered candidate.
Show a concise SANDR summary of the signal map with source context.
Show generated reports grouped by recent and place.
Show a markdown report with source context.
Show files by place, role, purpose, and recent.
Show saved signal, block, and tool gathered into a plan basket.
Pattern trace
Outcome
The user can trace a pattern, understand the evidence behind it, and keep reports and files attached to the work that follows.
Walkthrough
We will map how SANDR would open in the conversation, show the right context, prepare the work, and keep confirmation with the user.