# The algo records whose force is resilience_recovery

This index as JSON: https://banes-lab.com/json/api/facets/algo/force/resilience-recovery

## Entries

- [File Modification Recovery](https://banes-lab.com/records/algo/agent-workflow-file-modification-recovery.md): When a file modification conflict occurs, detect the error, re-read the current file, merge the intended delta into the current content, write the complete new version, verify persistence, and log recovery automatically without asking the developer.
- [Orchestrator Action](https://banes-lab.com/records/algo/orchestrator-action.md): Interpret handoff action as activate next agent, pause for the developer, or complete workflow; automatically continue unless a critical decision or repeated recovery failure requires the developer's involvement.
- [Workflow Recovery Loop](https://banes-lab.com/records/algo/workflow-recovery-loop.md): If an agent fails validation, read shared documents, identify unmet expectation, research the error pattern, relaunch the agent with adapted context, and pause for the developer after bounded recovery attempts.
- [Workflow Principles Mapping](https://banes-lab.com/records/algo/workflow-principles-mapping.md): Derive workflow principles from the agent sequence, first agent grounding role, final agent quality guarantee, intermediate agent contributions, automation, context awareness, recovery, scalability, hybrid execution, context forking, and workspace integration.
- [Workflow Creation Kernel](https://banes-lab.com/records/algo/workflow-creation-kernel.md): Load DSL and orchestration references, configure file recovery and context forking, discover workspace zones and agents, select shared documents, define dynamic agent sequence, classify execution mode, build 4D graphs, define handoff protocol, assemble coordination sequence, integrate checklist and capabilities, generate phase documentation, assemble template, and validate success criteria.
- [Event and Messaging Consistency](https://banes-lab.com/records/algo/event-and-messaging-consistency.md): For asynchronous systems, validate event contracts, message schemas, idempotent consumers, outbox publication, correlation metadata, ordering guarantees, retry behavior, and dead-letter handling.
- [State and Transaction Safety](https://banes-lab.com/records/algo/state-and-transaction-safety.md): Identify state mutation boundaries, enforce unit-of-work scope, validate invariants, apply concurrency control, guarantee idempotency where retries exist, and isolate side effects.
- [Resilience Policy](https://banes-lab.com/records/algo/resilience-policy.md): Classify failure modes, apply fail-fast, fail-safe, fail-secure, retry, timeout, circuit breaker, fallback, bulkhead, backpressure, health check, failover, and rollback policies according to dependency criticality.
- [Streaming Dataflow](https://banes-lab.com/records/algo/streaming-dataflow.md): Process data through forward-only stages, preserve bounded memory, apply backpressure, checkpoint state where needed, and prefer stateless processing unless state is explicitly modeled.
- [Idempotent Side Effect](https://banes-lab.com/records/algo/idempotent-side-effect.md): Assign a stable operation identity, check whether the effect was already applied, execute only once, and return the same semantic result for repeated requests.
- [Error Boundary](https://banes-lab.com/records/algo/error-boundary.md): Detect invalid state early, fail fast for programmer errors, fail safe for recoverable runtime faults, fail secure for security-sensitive failures, and return typed errors.
- [Resilience Control](https://banes-lab.com/records/algo/resilience-control.md): Wrap remote or unreliable calls with timeout, retry, circuit breaker, bulkhead isolation, fallback, and backpressure policies.
- [Recovery Deployment](https://banes-lab.com/records/algo/recovery-deployment.md): Continuously health-check services, isolate failed instances, fail over to redundancy, roll back unsafe releases, and use canary or blue-green deployment for controlled exposure.
- [Cache Correctness](https://banes-lab.com/records/algo/cache-correctness.md): Cache only data with defined freshness, key identity, invalidation triggers, consistency expectations, and fallback behavior.
- [Streaming Dataflow](https://banes-lab.com/records/algo/architecture-streaming-dataflow.md): Process data sequentially through bounded pipeline stages, preserve forward-only semantics where required, apply backpressure, and keep stages stateless unless state is explicitly modeled.
- [Static-to-Dynamic Readiness](https://banes-lab.com/records/algo/static-to-dynamic-readiness.md): Detect static implementation patterns, classify whether they are intentional or problematic, measure maintainability pressure, verify convention strength, and automate only when stability or fallback exists.
- [Capability Degradation](https://banes-lab.com/records/algo/capability-degradation.md): Declare required capabilities, probe availability, emulate missing behavior where safe, disclose unavailable capability, and downgrade confidence or block dependent operations.
- [Dynamic Extension Architecture](https://banes-lab.com/records/algo/dynamic-extension-architecture.md): Infer extension contracts, define discovery conventions, validate discovered implementations against the contract, preserve manual registration fallback, and report discovered, skipped, failed, and manual items.
- [Centralized Reference Resolver](https://banes-lab.com/records/algo/centralized-reference-resolver.md): Group duplicated hardcoded references, derive resolver names, define scope-safe resolution rules, provide configuration override fallback, and map each old reference to a resolver migration.
- [Manual Fallback Preservation](https://banes-lab.com/records/algo/manual-fallback-preservation.md): Keep explicit registration paths for non-conforming or exceptional implementations, order manual entries deterministically, and report manual items separately from auto-discovered items.
- [Automation Kernel](https://banes-lab.com/records/algo/automation-kernel.md): Load configuration, verify capabilities, initialize knowledge, detect static patterns, classify automation opportunity, analyze conventions, assess scale and performance, design dynamic architecture, optionally implement, validate, update knowledge, and report.
- [<Automation Concern>](https://banes-lab.com/records/algo/automation-concern.md): <Detect static coordination point> → <Classify intentional vs problematic> → <Measure scale pressure> → <Verify convention strength> → <Design dynamic contract> → <Preserve fallback> → <Validate performance and architecture> → <Capture knowledge>
- [Rollback-Centered Execution](https://banes-lab.com/records/algo/rollback-centered-execution.md): Before each destructive or high-risk phase, create a checkpoint, execute actions, verify results, and roll back immediately on critical action or verification failure.
- [Cross-Cutting Surface Coverage](https://banes-lab.com/records/algo/cross-cutting-surface-coverage.md): Gate the software surface beyond structure — security, performance, infrastructure and deployment, and resilience — so a change's threat, budget, config, and failure consequences are covered, not only its structural ones.
- [Repair Stage](https://banes-lab.com/records/algo/repair-stage.md): Route every finding to its earliest responsible owner stage, apply the fix, invalidate every dependent record downstream, and re-run from that stage — bounded to a fixed number of cycles, after which the run terminates as blocked with the remaining findings.
- [Bounded Repair Loop](https://banes-lab.com/records/algo/bounded-repair-loop.md): Cap the repair loop at a fixed cycle limit, and on each cycle repair from the earliest invalid stage, invalidate all downstream records, and regenerate them; exceeding the limit sets the run blocked with the remaining findings.
- [Severity Failure Routing](https://banes-lab.com/records/algo/severity-failure-routing.md): Use each finding's severity to choose its repair route — a blocker blocks and repairs, an error repairs, a warning requires a disposition, and anything lower is investigated.
- [Explicit Termination](https://banes-lab.com/records/algo/explicit-termination.md): Guarantee the generator stops with exactly one terminal — a written success artifact whose rendering integrity is verified, or a written blocked report — never a premature stop while the status is repairable and never a loop beyond the cycle bound.
- [File Modification Recovery](https://banes-lab.com/records/algo/file-modification-recovery.md): When a file mutation fails because state changed between read and edit, reread the current file, merge the intended delta into the current content, write the complete new version, and verify persistence.
- [Boundary Reconciliation](https://banes-lab.com/records/algo/boundary-reconciliation.md): Capture considerations during a phase but act on them only at the phase boundary — triage each open consideration against code and canon into a confirmed task or a dismissed resolved-false key, deduping new opens against the confirmed and dismissed sets before triage.
- [Governed Autonomous Plan Loop](https://banes-lab.com/records/algo/governed-autonomous-plan-loop.md): Drive a large task to completion under gates — seed per phase, investigate, execute, self-inform from canon and self-audit, capture considerations, reconcile at the boundary, and close only when the plan is a mechanically resolved state, then re-seed the next phase.
- [Persistence Fork](https://banes-lab.com/records/algo/persistence-fork.md): Specializing the Port Adapter, resolve the durable store by connection mode — an authoritative per-owner store when the trusted arm is connected, a read-only mirror otherwise — and write back only where accumulation is trusted.
- [Bounded Cascade Termination](https://banes-lab.com/records/algo/bounded-cascade-termination.md): Terminate the verify-remediate cascade on the completion AND-gate — a clean verdict, or bounded progress where findings strictly decrease within the pass bound — escalating when neither holds.