Skip to content
Scoutica Protocol

scoutica resolve

resolve reads a public GitHub repository, raw URL, or direct HTTPS card location and presents the available Scoutica artifacts. It never follows HTTP redirects.

Command Syntax

Section titled “Command Syntax”
Terminal window
scoutica resolve <card-url> [save-to-dir]

Execution Flow

Section titled “Execution Flow”
  1. Security Isolation: Requires HTTPS, rejects URL credentials and every non-public or mixed DNS answer, pins the connection to the validated address, disables proxies, and rejects redirects.
  2. Path Normalization: If you pass https://github.com/traylinx/agent, it automatically reformats strings logically into fetching from raw.githubusercontent.com.
  3. Bounded Target Discovery: It checks optional scoutica.json, then the four card artifacts. Every request has a 10-second connect timeout, 30-second total timeout, 2 MiB body cap, supported content type, and strict UTF-8/JSON validation where applicable. A discovery card_url re-enters the same boundary.
  4. Summary Aggregation: If retrieved successfully, the CLI compiles a rapid Python extraction showcasing:
    • User Name, Title, and Seniority
    • Experience Length and Domains
    • Engagement Constraints (Base salary floors, Remote Policies)
    • The total number of provable evidence links

Why use it:

  • Instantly verify the authenticity of someone’s published card.
  • Download a candidate’s complete professional structure to your hard drive locally with the [save-to-dir] argument to analyze inside your own internal AI pipeline.

Use Case: Offline Analysis

Section titled “Use Case: Offline Analysis”

You are parsing 50 candidates heavily for an upcoming contract gig. Instead of running scripts manually, you execute:

Terminal window
scoutica resolve https://github.com/john-doe/scoutica-card ./candidates/john-doe/

The CLI writes only the validated artifacts that the remote card actually exposes; optional files may be absent.