Trust / Dogfooding
StateAnchor runs StateAnchor
The StateAnchor GitHub Action runs on every push to stateanchor-hq/StateAnchor. The gate engine evaluates our own spec changes before they ship.
Every push to the StateAnchor repository is gated by StateAnchor itself. The same pipeline, the same gate engine, the same artifact generation that our users rely on.
If it's not good enough for our own repo, it's not good enough for yours. Every breaking change in StateAnchor's own API goes through the same gate engine our users rely on.
Latest gate evaluation
a7f3c91on mainALLOW
Gate score
94
Duration
11.2s
Sync run
sr_9f2a4c1b8e7d
Artifact hashes
TypeScript
sha256:e4a1f8c2...Python
sha256:7b3d9e01...Go
sha256:2c8f5a94...MCP
sha256:d1e7b3f6...Mar 27, 2026, 02:32 PM UTC
How it works
- A developer pushes to
stateanchor-hq/StateAnchor - GitHub Action triggers
stateanchor-sync-action - StateAnchor reads
stateanchor.yaml, generates IR, evaluates the gate - If the gate score is below threshold, the PR is blocked
- Artifacts are regenerated and stored with content-addressed hashes
Live feed from stateanchor-hq/StateAnchor coming after public launch.