Quickstart

This quickstart gets spanforge-secrets running with the minimum possible setup so teams can validate the workflow before deep integration.

Current status

This page is currently served from a generated fallback so the published documentation route remains usable. It provides the core context teams need while source markdown is being finalized.

Recommended workflow

1. Install the tool in the same environment where your build or validation steps run.
2. Execute it locally against representative inputs before wiring it into CI.
3. Promote the exact same command shape into automation so local and pipeline behavior stay aligned.

Example

spanforge-secrets sample-events.jsonl

Where this fits

spanforge-secrets belongs to the build phase of the SpanForge system. It should feel consistent with the rest of the platform: clear purpose, deterministic outputs, and documentation that helps teams move from experiment to governed production.