Expand description
Scope-bound HTTP collection for the decision runner.
§Runtime scope
- Build: default via
scanning. - Execution: Surface B (metered executor for the decision runtime).
- Default
termivar scan: yes, throughStandardWebDecisionRuntime. - Support: implemented and tested.
See docs/internals/runtime-map.md.
This executor performs one bounded discovery request and emits immutable, typed observations. It does not classify vulnerabilities, follow redirects, choose follow-up actions, or mutate the knowledge base directly.
Structs§
- Http
Evidence Executor - Real HTTP executor that produces typed evidence for the decision runner.
- Http
Evidence Policy - Scope, resource, and evidence policy applied to every HTTP probe.
- Http
Header Payload Binding - Binds a header-valued payload strategy to the HTTP evidence executor.
- Http
Probe - One validated, bodyless discovery request.
- Subject
Http Probe Provider - Default provider that interprets
endpoint:<absolute-url>subjects.
Enums§
- Http
Body Capture - Response-body representation allowed to enter the knowledge base.
- Http
Evidence Error - Configuration and execution failures for HTTP evidence collection.
- Http
Probe Method - Discovery-only HTTP methods supported by the evidence executor.
Constants§
- DEFAULT_
HTTP_ BODY_ LIMIT - Default maximum number of response-body bytes read by one probe.
- HTTP_
EVIDENCE_ EXECUTOR_ ID - Stable executor identity used by the standard HTTP evidence collector.
- MAX_
HTTP_ BODY_ LIMIT - Hard guard preventing an individual evidence probe from buffering too much.
Traits§
- Http
Probe Provider - Host-owned mapping from a decision case to an HTTP discovery request.