What problem does it solve? Operating Fluent Order Management (Fluent Commerce) safely is hard because every order, fulfilment, and payment is driven by the Rubix rules engine with at-least-once event delivery, so a wrong commit, capture, or ruleset deploy can double-charge customers, oversell inventory, or re-orchestrate the entire fleet. This Skill gives an AI agent the operator judgment to classify each action as read, reversible write, committing write, or destructive, and to know the edge states and recovery paths before acting. ## Core Features & Use Cases - Risk-classified operation matrix: Maps every Fluent OMS operation family (booking, sourcing, capture, refund, appeasement, ruleset deploy, inventory feed load) to a read / write / destructive gate with the reasoning behind each classification. - Gotcha causal chains: 26 documented failure chains covering ATS vs on-hand, the IQ ledger, event idempotency, auth expiry, split fulfilment, DSV cancels, and inventory feed re-baselining. - Edge states and recovery playbooks: Handles click-and-collect, backorders, advance exchanges, multi-tender payments, escalated fulfilments, and explains what can and cannot be undone. - Use Case: Before releasing a fraud hold or deploying a sourcing ruleset change to a live retailer, the agent consults this Skill, recognizes both as destructive-tier actions, re-reads ATS and gateway state, and pauses for named human approval instead of executing blindly. ## Quick Start Ask the agent whether it is safe to cancel a Fluent OMS order that has already been captured and what steps the cancellation requires.
