How Scout fits together
Protocols provide data. Scout provides the monitoring language.
- Your request
- Scout understands it
- Data source
- Monitoring rules
- Verified live Watch
Your request
You describe the activity and conditions. Scout identifies the data and tools needed and asks about missing details.
Data sources
Adapters turn protocol-specific activity into a consistent form Scout can evaluate. The capability registry records what each source provides and its limitations.
Monitoring rules
Scout combines reusable conditions over that activity. It checks compatibility and verifies the whole Watch before activation.
A live Watch
The worker follows finalized activity, checks the rules, investigates matches and delivers alerts according to your settings.
Adding protocols
A new protocol adapter supplies data to the same monitoring engine. It does not require a separate Watch system. New sources must establish their capabilities before they are offered as supported.
What Scout can monitor now
Technical details
Internally, Scout represents the request as a typed WatchProgram and validates every required capability before activation. The Capability Planner separates data acquisition from the generic runtime. Availability is not proof of whole-program acceptance or live stream health.
- Intent Resolver
- WatchProgram
- Capability Planner
- Data Adapter / Substreams
- Normalized Events
- Generic Runtime
- Investigation
- Decision
- Delivery
Watch details retain the capability plan, selected packages, modules, pipeline strategy, verification and historical evidence. General arbitrary pipeline generation is not currently implemented.