What it does
FailWarden Orchestrator is built for documented remediation workflows that still need
to be executed consistently and audited afterward. Its current scope includes runbook
validation, strict variable rendering, linked step orchestration, retries and branching,
notifier support, execution history, and dry-run previews.
- YAML runbook model with compile-time validation
- SSH execution for Linux and Windows PowerShell over SSH
- Slack webhook and SMTP email notifications
- SQLite-backed execution and step history with audit artifacts
- Five shipped runbooks for common remediation scenarios
Current maturity
The repository README reflects V1 implemented, V1.5 implemented, and planned V2 scope.
Current release packaging and CI improvements landed in v0.2.0.
- V1 includes the core runbook engine, notifiers, persistence, audit logging, and dry-run mode.
- V1.5 adds stronger CLI output, JSON exports, local integration coverage, and GitHub Actions CI.
- Planned V2 scope includes PSRP, HTTP execution, optional dashboarding, metrics, and notifier fault isolation.
Validation status
The validation claim is intentionally narrow. The project has strong unit coverage and
controlled local integration coverage, but it has not yet been validated
against real production infrastructure or live notifier endpoints.
This distinction matters. The current state supports credibility for engineering review
without overstating operational readiness.
Why it is worth featuring
This project shows the clearest combination of infrastructure context, practical Python
design, quality gates, release discipline, and honest solo-maintainer positioning.