From your request to a live Watch
Scout finds the data and checks the conditions behind your request before it starts monitoring.
- Your request
- Scout understands it
- Data source
- Monitoring rules
- Verified live Watch
Understand your request
Scout identifies what you want to watch. If the token, chain or scope is unclear, it asks for the detail it needs.
Check data and monitoring tools
Scout checks every condition against its installed capabilities. If something is missing, it explains that part before attempting to build.
Find and reuse blockchain data
Scout looks for existing data pipelines it can reuse. Finding a package is only a starting point; its data must satisfy the request.
Verify the data and create the rules
Scout checks real blockchain output and tests whether the Watch preserves your conditions. Failed or incomplete verification blocks activation.
Monitor and explain matches
Once the stream is healthy and the Watch is verified, Scout monitors live activity. Matches retain their evidence, historical context and delivery status.
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.