scoutica publish

The publish command securely and swiftly stages your Scoutica profile arrays, commits them with an automated message, and pushes them straight to your main branch.

Command Syntax

scoutica publish [directory]

How It Works

This command does not push your massive raw CV PDFs, unencrypted data, or temporary validation artifacts to the internet.

When you run scoutica publish:

1. It actively verifies that a .git repository exists in the current directory.
2. It detects exactly 5 files for the payload:
   • profile.json
   • rules.yaml
   • evidence.json
   • SKILL.md
   • scoutica.json
3. It ignores everything else (ensuring resume.pdf or scoutica_prompt.txt never leak online).
4. Forms the git tree: git add <files>.
5. Prompts you heavily if you haven’t validated the card (scoutica validate beforehand is technically required!).
6. Commits with an elegant timestamp message and pushes to your remote origin cleanly.

Why use it:

• A simple wrapper around git that guarantees no sensitive parsing secrets or raw text ever touches the public web.
• Encourages rapid iteration of your profile. Changing jobs? Scan the new job title in, and scoutica publish right immediately.

Routine Workflow

Most professionals hook this up automatically. You scan your files, quickly sanity check them, ensure validation passes, and then publish to make the Card discoverable by LLM recruiters:

scoutica scan ~/CV/ ./ && scoutica validate ./ && scoutica publish ./