arrive-resident-check

To verify resident-check governance gates, run arrive check --strict to inspect advance files under arrive/systems/*/advances and validate Owner Approval, Invariant Impact, Rollback, and Evidence links for touched resident components.

An ARRIVE resident-check gate is a compliance validation step that ensures touched resident components have documented Owner Approval, Invariant Impact Statements, Rollback Plans, and Evidence links before merging.

Check compliance by inspecting advance files within arrive/systems/*/advances to confirm required governance sections exist, then generate guidance to address missing gates and document remediation steps.

No specific dependencies are required to run resident-check verification, as the Skill operates independently to inspect advance files and validate required governance sections for touched resident components.

Validation is limited to inspecting advance files under arrive/systems/*/advances and requires the SKILL.md frontmatter to declare name and description, with the body describing gate checks and recommended remediation actions.

Yes, you can use strict mode by running arrive check --strict to enforce governance compliance, which verifies that all required gates are satisfied when resident components are touched during an advance.