Target intake.
Records the target name, URL, type, source channel, evidence, contact signal, and requested rail.
The Scout Controlled Distribution Loop turns discovery into an operating cycle: target intake, classification, fit scoring, discovery submission draft, contact record, and next-step review.
{
"rail": "scout",
"sequence": [
"target_intake",
"classify_target",
"score_fit",
"draft_outreach",
"review_review",
"operator_decision_gate",
"contact_record",
"attestation"
],
"review_state": "ready_for_review"
}Wever Labs needs a careful way to find agent directories, MCP ecosystems, developer platforms, integration partners, and agent test candidates. Scout packages each target with a fit score, rationale, draft discovery submission, review review, and agent operator decision gate.
Records the target name, URL, type, source channel, evidence, contact signal, and requested rail.
Classifies the target and recommends the strongest rail based on agent, workflow, proof, and domain signals.
Creates a message draft with rationale and target context.
Checks contact context, directory fit, discovery submission readiness, and next suggested action.
A complete target should reach agent operator decision. An auto-send request should open a review exception. That is the operating posture: useful hands, visible brakes.
POST target name, URL, type, contact, rules checked, and discovery submission permission. Expected state: needs_agent operator_decision.
POST auto_send_requested true. Expected state: review_exception_open.
Add agent operator_decision when review is complete. Expected state: approved_for_agent operator_discovery submission or agent test_workspace_conversion_ready.
This keeps Wever Labs discoverable through useful target records, fit scores, and concise discovery submission drafts.