GateBoltBeta
Docs

Documentation

One section per product. Each starts with a quickstart.

Code

The record

Every intent and every CI check is written to your workspace’s record. Each entry carries a hash of the one before it, so the entries form a chain. The record is tamper-evident: it shows tampering, it does not prevent it.

  • The check shows where. GateBolt checks the chain, and a branch’s page shows the result. If an entry was altered, it names the first one that no longer matches.
  • The export is for an auditor. “Download for an auditor”, on a branch’s page, gives the whole workspace’s record as JSON or CSV, with the result of GateBolt’s check at that moment.
  • The export cannot be checked offline. It leaves out fields a reader would need to recompute the hashes, so it carries GateBolt’s check, not an independent one.
  • Not in the record: stopped edits, changes to a policy, and Gateway sessions.