Tool documentation
Architecture
Guidance for sf-validate, aligned with the same reading rhythm, navigation model, and contrast system used across the rest of the site.
Architecture
The architecture section explains how sf-validate fits inside the broader SpanForge system and why its responsibilities remain intentionally narrow.
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
- Install the tool in the same environment where your build or validation steps run.
- Execute it locally against representative inputs before wiring it into CI.
- Promote the exact same command shape into automation so local and pipeline behavior stay aligned.
Example
sf-validate sample-events.jsonl --explain
Where this fits
sf-validate 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.