skill-system-gate

A fail-closed gate check validates experiment artifacts, logs, and configurations against predefined rule sets to prevent unsafe registrations and gate failures before registry actions proceed.

Run the validation script with the experiment name and optional phase root to check code and logs against gate_bank rules, producing a markdown verdict and machine-readable summary for registration safety.

Yes, you can verify registry safety before resets by detecting RUNNING states and stale entries through read-only queries that monitor registry health without mutating any state.

Yes, the gate validation process performs read-only database queries to satisfy gate-rule checks and monitor registry health, ensuring no mutations occur during safety verification.

The validation operates as a read-only health overview, meaning it detects RUNNING states and stale entries for operator awareness but does not perform automatic state cleanup or registry mutations.

Registration fails when artifacts, logs, or configurations violate gate_bank rules, triggering fail-closed checks that prevent unsafe registrations and ensure pipeline safety compliance.