Slipmark Cloud

A record of what your AI agents checked, that can't be quietly edited.

Every CI run that uses Slipmark can write its verdicts to an append-only ledger. Each entry is bound to the exact files the agents read and chained to the one before it, so history can't be rewritten without it showing.

Turn it on

Two lines in the workflow you already have. No account and no secrets: GitHub vouches for which repository and commit each record came from.

jobs:
  verify:
    permissions:
      contents: read
      id-token: write
    steps:
      - uses: actions/checkout@v4
      - uses: founder-ship-it/Slipmark@v0.4.0
        with:
          cloud: "true"

The job summary links to the run's proof page. Public repositories are free. Private repositories, rules enforced as a required GitHub check, and audit evidence packs come with the Team and Business plans.

What a record holds

Which agent gave which verdict, the SHA-256 of every file it was based on, whether those files still matched when CI ran, and the commit, workflow and pull request it belongs to.

Why it can be trusted

Records are only accepted with a GitHub-signed token for that repository and run. Entries can't be changed or deleted, and each one includes the hash of the one before, so any rewrite breaks the chain.