# Project: SF Autonomous Self-Healing

## What This Is

This project implements self-healing capabilities for the Singularity Forge (SF) autonomous execution loop. It addresses the issue of the loop halting silently when encountering blocking states, such as "needs-attention" validation verdicts, by introducing graduated escalation (notifications, self-feedback) and automated recovery (auto-remediation, auto-deferral).

## Core Value

The autonomous loop should never sit silently stuck. Every halt must be communicated to the operator and, where safe, attempts should be made to resolve the blockage autonomously.

## Current State

The SF autonomous loop identifies terminal states (action: "stop") in its dispatch rules, but the loop simply ceases execution without proactive notification. Stuck detection exists for cycles (sliding-window) but not for persistent "stop" states.

## Architecture / Key Patterns

- **Auto-Loop**: `src/resources/extensions/sf/auto/loop.js` manages iteration and phase dispatch.
- **Dispatch Rules**: `src/resources/extensions/sf/uok/auto-dispatch.js` determines the next action based on milestone/slice state.
- **Self-Feedback**: `src/resources/extensions/sf/self-feedback.js` provides the registry for anomalous behavior.

## Capability Contract

See `.sf/REQUIREMENTS.md` for the explicit capability contract, requirement status, and coverage mapping.

## Milestone Sequence

- [ ] M003: Autonomous Self-Healing and Escalation — Implement loop watchdog, notification plumbing, and validation-recovery policies.
