Skill

integrity-check

Structural integrity verification — monotonic counters, service health, and evidence store operability

Install

npx claudepluginhub supportersimulator/3-surgeons --plugin 3-surgeons

Tool Access

This skill uses the workspace's default tool permissions.

Preview

The CorrigibilityGate's integrity verification mode. Detects state corruption, counter tampering, and service degradation.

SKILL.md

Similar Skills

design-system

Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.

team-skills-platform

163.7k

ui-demo

Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.

team-skills-platform

163.7k

kotlin-patterns

Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.

team-skills-platform

163.7k

Stats

Stars0

Forks0

Last CommitMar 15, 2026

Actions

View Source View Plugin View on GitHub View README

Integrity Check

The CorrigibilityGate's integrity verification mode. Detects state corruption, counter tampering, and service degradation.

When to Use

After a crash or unexpected restart

When state values seem inconsistent

After manual state modifications

Periodic health verification (beyond what gains-gate checks)

What It Checks

Monotonic counters — event counts should only increase. A decrease signals data loss or tampering.

Service health — state backend is responding to pings.

Evidence operational — evidence store can be queried.

How It Works

The integrity check reads integrity:* keys from the state backend:

integrity:events_count vs integrity:events_count:prev

If current < previous → something decreased a counter → FAIL

Without a state backend, integrity checks are skipped (passes with "skipped" message).

Output

Standard GateResult:

passed — true if all checks pass

checks — individual check results with names and messages

duration_ms — how long the check took

Relationship to Other Gates

Gate

Purpose

When

GainsGate

Infrastructure health

Between phases

CardioGate

Quality review + rate limit

Automated quality checks

CorrigibilityGate.run()

Text safety (regex)

Before destructive ops

CorrigibilityGate.check_integrity()

Structural integrity

After crashes, periodic

Integrity Check

The CorrigibilityGate's integrity verification mode. Detects state corruption, counter tampering, and service degradation.

When to Use

After a crash or unexpected restart
When state values seem inconsistent
After manual state modifications
Periodic health verification (beyond what gains-gate checks)

What It Checks

Monotonic counters — event counts should only increase. A decrease signals data loss or tampering.
Service health — state backend is responding to pings.
Evidence operational — evidence store can be queried.

How It Works

The integrity check reads integrity:* keys from the state backend:

integrity:events_count vs integrity:events_count:prev
If current < previous → something decreased a counter → FAIL

Without a state backend, integrity checks are skipped (passes with "skipped" message).

Output

Standard GateResult:

passed — true if all checks pass
checks — individual check results with names and messages
duration_ms — how long the check took

Relationship to Other Gates

Gate	Purpose	When
GainsGate	Infrastructure health	Between phases
CardioGate	Quality review + rate limit	Automated quality checks
CorrigibilityGate.run()	Text safety (regex)	Before destructive ops
CorrigibilityGate.check_integrity()	Structural integrity	After crashes, periodic