abm9111/Chamber Verify — docs drift gate
Fail the build when the ground moves under a written claim — hash-checks every pinned citation. No model, no network.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Aug 20, 2026
- License
- MIT
Pinned Snippet
uses: abm9111/chamber@0bc194e2723e3f7ee4ae8a22401c24f223fa2ead # v0.1.5tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| docs-path | Directory of markdown to ingest as citable passages. | no | docs |
| code-path | Directory of code to index as citable passages (TypeScript/JavaScript/ Python). Empty skips code indexing. | no | "" |
| database | Path to the Chamber SQLite database holding the pinned beliefs. This must persist across runs (commit it, or restore it from a cache) — a fresh database has zero beliefs and verify has nothing to check. | no | .chamber/chamber.sqlite |
| node-version | Node.js version (23.6+ — type stripping outside node_modules). | no | 24 |
Outputs
| name | description |
|---|---|
| report | The full verify --json object (beliefs, pins, failure reasons). |