01 Offline config governance
Keep the why
beside the config.
A small CLI that makes policy-sensitive settings carry their decision trail—without invalid comment keys, leaked values, or a new config language.
- JSON · YAML · TOML
- JSON Schema
- Zero telemetry
The config remains strict.
The reason remains attached.
The report reveals no values.
02 The review loop
A sidecar, not a side quest.
Human context gets its own typed record. Your source files keep every comment, space, and strict parser they already have.
- 1
Initialize
Create adjacent decision records for config leaves.
crg init agent.json - 2
Explain & stamp
Write the rationale, then bind it to the reviewed value with a one-way fingerprint.
crg stamp agent.json - 3
Guard the change
Fail CI on missing, orphaned, overdue, schema-invalid, or stale decisions.
crg check agent.json --schema schema.json - 4
Review the why
Render changed paths and rationale—not secret-bearing values.
crg diff old/agent.json agent.json
03 Browser proof
Try a decision check.
Runs entirely in this tab. Edit a value to make the existing rationale stale, or repair the rationale and stamp it locally.
04 Own the guardrail
One binary.
No account.
Build from source today. Release binaries can drop into any CI job; output is human-readable by default and JSON with one flag.
$ cargo install --git \
https://github.com/B-Divyesh/sf-config-rationale-guard
$ crg check agent.json --json
PASS 12 decisions · 100% coverage
05 Team unlock
Standardize the ritual.
The full guard is free. Pay once for maintainable policy presets and copy-ready CI review recipes for GitHub Actions and GitLab CI.
- Agent and CI policy path presets
- Pull-request decision summary recipes
- Future Team recipe updates
Already purchased?
Paste the license token from your receipt to restore Team recipes on this device.
Free edition active.
Team recipes unlocked
Your cached license keeps these available offline. Verification occurs at most once per day.