seam-check · you already own this

A GitHub Action that collapses a pull request's intent against your org's own repos — and says so in the thread, before the merge. Teams and their AI tools rebuild what the org already holds; this is the check that was missing. Advisory by default. Deterministic. Nothing leaves your org.

witness 50/50 · CLEAN · zero baselines κ = 0.618 · exact to the bit source + CI

Add it in two minutes

One step in any workflow. The shadow is built from your org's described repos at run time via the built-in token — or point shadow: at a committed file and skip the API entirely.

# .github/workflows/seam-check.yml
name: seam-check
on: [pull_request]
permissions: { contents: read, pull-requests: write }
jobs:
  own:
    runs-on: ubuntu-latest
    steps:
      - uses: sjgant80-hub/seam-check@v0.1
        # with:
        #   org: your-org            # default: the repo's owner
        #   fail-on: already-owned   # default: none (advisory)
        #   always-comment: "true"   # default: novel stays silent

Try the verdict

This page runs the same gated kernel the Action runs — against a real shadow of 1,400+ described repos. Type a PR title, get the exact comment the Action would post. Or load your own shadow.json (node build-shadow.mjs --org your-org) — it is read in your browser, uploaded nowhere.

Claims and limits

PROVEN — GATED, 50/50

  • deterministic — same PR, same shadow, same verdict; no model, no mood
  • the κ boundary is exact to the bit: 0.618 owns, 0.617 does not
  • the comment is marker-first — reruns edit one comment, never spam the thread
  • a thin PR title is never a red build; a broken shadow is never a silent green
  • advisory by default; the wall (fail-on) only when your org asks for it

NOT CLAIMED

  • it reads titles and descriptions, not diffs — a mislabelled PR gets a mislabelled answer
  • it cannot see repos your org never described — an undescribed repo is invisible, and the Action says so rather than guessing
  • no learning, no telemetry, no uploads — your shadow is read where it lives

The pair

Before you merge AI-written code, two questions deserve a deterministic answer: did it survive its own tests? — that's witness, a mutation gate with no dependencies. And did you already own it? — that's this. Both run in plain CI, both refuse to guess.