# The algo records whose force is state_transaction

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

## Entries

- [Non-Destructive Domain Investigation](https://banes-lab.com/records/algo/non-destructive-domain-investigation.md): Prepare static investigation, optionally prepare safe executable analysis, prohibit source mutation, execute or emulate analysis, and merge observable outputs into domain intelligence.
- [Replacement Safety](https://banes-lab.com/records/algo/replacement-safety.md): If replacing an existing artifact, require prior approval, archive existing artifacts, verify archive persistence, and block new persistence if archival cannot be confirmed.
- [Hybrid Workflow Orchestration](https://banes-lab.com/records/algo/hybrid-workflow-orchestration.md): Classify workflow phases by execution verb, run discovery and investigation agents in parallel forked contexts, run action and mutation agents sequentially, and coordinate all agents through shared artifacts and handoff signals.
- [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.
- [Context Forking Configuration](https://banes-lab.com/records/algo/context-forking-configuration.md): Assign forked context to discovery, investigation, and documentation agents; assign normal context to action and validation agents; preserve model and parallel eligibility metadata per agent class.
- [Sequential Agent Execution](https://banes-lab.com/records/algo/sequential-agent-execution.md): Execute state-changing or validation agents one at a time in normal context, pass handoff context from the previous phase, wait for completion signal, then activate the next agent.
- [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.
- [<Workflow Orchestration Concern>](https://banes-lab.com/records/algo/workflow-orchestration-concern.md): <Load orchestration grammar> → <Discover workspace config> → <Select shared documents> → <Define agents> → <Classify parallel vs sequential> → <Fork discovery contexts> → <Serialize action phases> → <Build 4D graphs> → <Create handoff protocol> → <Coordinate shared-document refinement> → <Integrate checklist and capabilities> → <Validate template>
- [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.
- [Transaction Boundary](https://banes-lab.com/records/algo/transaction-boundary.md): Define atomic state-change boundaries, isolate concurrent mutation, enforce consistency rules, and commit or roll back as a unit.
- [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.
- [Automation Operation Mode](https://banes-lab.com/records/algo/automation-operation-mode.md): Detect operation mode, bind allowed actions, prohibit source mutation outside implementation mode, and emit analysis, design, implementation, or validation artifacts accordingly.
- [Operation Mode Gating](https://banes-lab.com/records/algo/operation-mode-gating.md): Detect the requested operation mode, bind permitted capabilities, reject source mutation outside execution mode, and emit only artifacts valid for the current mode.
- [Atomic Refactor Phase](https://banes-lab.com/records/algo/atomic-refactor-phase.md): Divide the refactor into ordered phases, attach actions, attach verification criteria, attach rollback behavior, and prevent progression until the phase verification passes.
- [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.
- [Early Success Exit](https://banes-lab.com/records/algo/early-success-exit.md): If verification has no errors, report successful compliance and terminate without remediation.
- [Phase-Separated Execution](https://banes-lab.com/records/algo/phase-separated-execution.md): Detect the current workflow phase, bind allowed operations to that phase, reject operations outside the phase contract, and emit only the artifact valid for that phase.
- [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.
- [Living Plan State](https://banes-lab.com/records/algo/living-plan-state.md): Treat the plan as durable append/update-only state — tasks carrying status and grounding, a considerations backlog, and a dismissed-key set — maintained every turn and re-delivered on restart, so anything discovered mid-pass is retained instead of falling out of scope.
- [Phase Close Gate](https://banes-lab.com/records/algo/phase-close-gate.md): Make completion a gated state of the plan rather than a judgment call — a phase closes only when all tasks are done, a dry reconciliation pass holds, verify is clean for the chosen scope, and the coverage graph confirms the ripple set; otherwise the loop returns to execution.
- [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.
- [<Governed Plan Concern>](https://banes-lab.com/records/algo/governed-plan-concern.md): <Seed the phase> → <Investigate and execute under gates> → <Self-inform from canon and self-audit> → <Capture and reconcile considerations at the boundary> → <Close only on a mechanically resolved gated state> → <Re-seed the next phase>
- [Idempotent Merge](https://banes-lab.com/records/algo/idempotent-merge.md): Specializing the Idempotent Side Effect, assign each fact a stable identity, apply the delta per field kind, deduplicate and cap, and guarantee that re-applying the same delta yields the same document.
- [<Living Accumulation Concern>](https://banes-lab.com/records/algo/living-accumulation-concern.md): <Compose prior memory as disclosed evidence> → <Capture only same-turn verified deltas> → <Merge idempotently by stable identity, bounded> → <Version and log only real change> → <Persist against the connection fork> → <Overlay onto the immutable baseline>
- [Loop-Owned Mode Selection](https://banes-lab.com/records/algo/loop-owned-mode-selection.md): The loop assigns the (phase, activity) mode that selects which contract a response is validated against; the model's output carries no contract-selecting field, so a model can never grade itself against a contract it chose.
- [Versioned Turn Provenance](https://banes-lab.com/records/algo/versioned-turn-provenance.md): Persist each accepted model turn as an append-only, mode-tagged, schema-versioned, causally ordered record with change-only provenance, so the turn history is a queryable, auditable log and a turn is never graded against a schema version its stored state never saw.
- [<Pattern Distillation Concern>](https://banes-lab.com/records/algo/pattern-distillation-concern.md): <Initialize evidence workspace> → <Measure current architecture> → <Group semantic families> → <Extract behavioral signatures> → <Detect duplicate/inconsistent behavior> → <Score anti-patterns> → <Evaluate abstraction boundary> → <Compose reusable schematic> → <Migrate with rollback> → <Verify old-pattern elimination> → <Record ROI>
- [Custom-Rule Derivation](https://banes-lab.com/records/algo/custom-rule-derivation.md): Derive a candidate rule from repeated evidence through anti-pattern classification, boundary-principle evaluation, and candidate selection, migrate with rollback, verify elimination, and admit a tightening rule while routing a self-certifying or loosening rule through the developer's gate.