Skip to content

Revert mutation-ratchet CI step (restore green main) #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
daniloc merged 1 commit into from
Jun 25, 2026
Merged

Revert mutation-ratchet CI step (restore green main) #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 0 additions & 18 deletions .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,24 +103,6 @@ jobs:
- name: Test
run: npm test

# Boundary-oracle mutation ratchet: a totality oracle only protects the system
# if it actually CATCHES a break at its chokepoint. This breaks each boundary's
# chokepoint with a compile-safe mutation and requires its oracle to fail
# (ANCHORED); an oracle that stays green under a broken floor (VACUOUS) — the
# exact rot that let the trust-split oracle pass a literal inversion before it
# was hardened — fails the gate. PR runs only edges whose chokepoint/oracle
# changed (incremental); push to main runs the full backstop. python3 is
# preinstalled on ubuntu-latest; the harness reverts every mutation via git.
- name: Boundary oracle mutation ratchet
if: github.event_name == 'pull_request' || github.ref == 'refs/heads/main'
run: |
if [ "${{ github.event_name }}" = "pull_request" ]; then
git fetch --no-tags --depth=1 origin "${{ github.event.pull_request.base.ref }}"
python3 scripts/invariant-mutation-probe.py --changed FETCH_HEAD
else
python3 scripts/invariant-mutation-probe.py
fi

# Ratchets: no new conventions, no new raw SQL interpolation sites, and the
# trust atlas stays in sync with the boundary claims (no managed chokepoint
# left off the atlas, no dangling edge).
Expand Down
Loading