Observed or sourced
A source link, timestamp, runtime event, or model output exists. The interface can point back to where it came from.
It helps readers inspect AI safety signals, source movement, perception robustness, and runtime state without filling gaps with invented telemetry.
A realtime operational surface for source-backed AI updates and runtime state.
A ledger of source claims, telemetry frames, collector state, and unavailable data.
Browser-side COCO-SSD inference under real input degradation.
Source-backed safety concepts, frameworks, and public references.
A source link, timestamp, runtime event, or model output exists. The interface can point back to where it came from.
A summary, grouping, or trace built from source activity, telemetry, or model-output history. It should still show its inputs.
A teaching example that explains a risk or system behavior without claiming it happened in a deployed system.
A parameter-driven demo. Useful for learning, but not evidence about the outside world unless real inputs are attached.
SIGNALWATCH is a public, operational interface for inspecting evidence around AI systems. It combines source monitoring, runtime telemetry, safety references, and browser-side robustness tests while keeping each data type labeled.
The goal is not to dramatize AI. The goal is to make evidence easier to read: what was observed, where it came from, when it appeared, and what remains unknown.
Must include real source data, links, timestamps, or provenance.
Describes SIGNALWATCH infrastructure state, not facts about the AI ecosystem.
Come from real browser-side inference. Missing outputs remain missing.
Are labeled education surfaces, not operational measurements.