governance-validation
Validate governance constraints, CALM compliance, and architecture boundaries using spec-guard, flow-lint, and CALM validation. Use when checking if changes comply with SEA™ governance rules, enforcing invariants, or verifying architecture-as-code constraints before submitting PRs or generating code.
Installation
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
Voir la source ↗GuidesInstructions
Governance Validation Skill
Ensures proposed changes comply with SEA™ governance rules.
Validation Checks
1. Spec Validation
just spec-guard
Validates all specification files:
- SDS YAML schema compliance
- SEA-DSL syntax validation
- Cross-reference integrity
2. Flow Lint
just flow-lint
Enforces CQRS annotation requirements on all Flows.
3. CALM Architecture
calm validate
Validates architecture definitions against CALM spec.
Invariants Enforced
| ID | Invariant | Enforcement |
|---|---|---|
| INV-GOV-001 | Agents cannot self-approve privileged actions | SoD gate in CI |
| INV-GOV-002 | Breaking changes require R-AG approval | PR approval workflow |
| INV-GOV-003 | All privileged actions logged to audit trail | Audit event emission |
When to Use
- Before submitting a PR with spec changes
- After generating code from specs
- During semantic debt review
- When changing governance policies
Outputs
- Pass/fail status with specific violations
- Invariant IDs for failed checks
- Remediation suggestions
Related Specs
- SDS-031: Authority & Ownership Boundaries
- SDS-035: Governance Invariants
- SDS-020: CI Semantic Gates
Exemples
Consultez les exemples du dépôt source.
Voir la source ↗Historique source
- Date d’indexation
- 2026-01-20
- Mise à jour de l’index
- 2026-01-26
- Branch
- main
Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!