Multi-Step Autonomous Web Workflow Chain and State Transition Spec

Role: Principal Agent Systems Architect specializing in stateful browser workflows and deterministic agent orchestration.

Context

• End-to-end user journey: {{user_journey_target}}
• State persistence mechanism: {{state_store_technology}}
• Checkpoint intervals: {{checkpoint_frequency}}
• Failure fallback strategy: {{fallback_strategy}}
• Allowed side effects: {{allowed_side_effects}}

Task

Author a comprehensive workflow execution specification detailing the directed state machine, step transitions, node validation criteria, and rollback policies for executing {{user_journey_target}}.

Method

1. Deconstruct {{user_journey_target}} into discrete, idempotent execution states and sub-agent milestones.
2. Define unambiguous state transition triggers, input requirements, and exit conditions for each node.
3. Structure snapshot serialization protocols to {{state_store_technology}} at intervals defined by {{checkpoint_frequency}}.
4. Formalize guardrails isolating irreversible operations strictly governed by {{allowed_side_effects}}.
5. Design compensatory transaction nodes to undo partial web mutations when encountering catastrophic workflow exceptions.
6. Detail branch-pruning and cycle-detection rules to prevent recursive agent execution loops.
7. Specify telemetry events emitted at every node entry, validation check, and transition completion.

Constraints

• State transition schemas MUST be purely deterministic and mathematically acyclic except where explicitly configured.
• Irreversible actions outside {{allowed_side_effects}} MUST halt execution and request human-in-the-loop intervention.
• Intermediate state snapshots MUST be fully recoverable from {{state_store_technology}} without data corruption.
• Every transition MUST specify a maximum execution TTL before triggering {{fallback_strategy}}.

Output format

• 1. State Machine Topology Diagram (Mermaid.js state diagram syntax)
• 2. Node Execution Contract Table (columns: State Name, Input Preconditions, Permitted Actions, Exit Invariants)
• 3. Checkpointing & Persistence Protocol (schema definitions targeting {{state_store_technology}})
• 4. Rollback and Recovery Ruleset (compensatory logic configured for {{fallback_strategy}})

Self-review

1. Does every terminal failure state link directly to an explicit compensatory or rollback mechanism?
2. Are all checkpoint boundaries aligned with {{checkpoint_frequency}} without inducing prohibitive latency?
3. Are side effects strictly restricted to {{allowed_side_effects}} with explicit validation gates?