iowarp/spotter
SPOTTER's forensic watcher: provider-aware execution and artifact lineage across Flowcept, CMF and CLIO's native journal, captured-attention inspection, and skills for investigating and alerting on unexplained deviations in a watched CLIO session.
How SPOTTER reports an unexplained deviation in the watched session - the evidence an alert needs, the raise_alert_card call, how CLIO's clearance barrier holds the session's next change while a review runs, and why the person decides what happens next. Load before raising an alert.
Read captured model attention for the watched session with spotter_list_attention_calls and spotter_inspect_attention - exact response ids, recorded decode steps, versioned profiles, coverage and uncertainty - and carry the evidence into a finding or an alert card without guessing coordinates. Load when a question is whether an input steered a model call.
Answer an execution or artifact-lineage question from the configured provenance stores (Flowcept, CMF or CLIO's native journal) with the spotter tools - discover what the active providers can answer, move from summaries to exact tasks and lineage graphs, join the two sides through a correlation id, and report coverage honestly. Load when a wake or a question needs evidence of what the watched session ran or produced.