/**
 * Ansible YAML sort orders are semantic first, ansible-lint compatible second,
 * and documentation-shaped third. Plays flow from identity and target selection
 * to execution context, result controls, variables, selection, then the play
 * body.
 *
 * Task-like mappings intentionally differ: keep identity first, the module or
 * action body next, then execution context, result handling, conditions,
 * selection, notifications, and large nested bodies. ansible-lint enforces the
 * most important part of that shape: `name` first, and `block`, `rescue`, and
 * `always` last. Preserve that behavior because controls placed below a large
 * block are easy to confuse with nested task controls.
 *
 * Do not append the generic YAML sort fallback here. Module argument maps, role
 * variables, and many Molecule or metadata sub-maps are domain-specific and may
 * be intentionally grouped. Unknown task keys are treated as module/action keys
 * by default; update `ansibleTaskControlKeys` when adding a new Ansible control
 * keyword.
 */
import type { RuleYamlSortKeysOptions } from '../types/rule-yaml-sort-keys-options';
export declare const ruleYamlSortKeysOptionsAnsibleTasks: RuleYamlSortKeysOptions;
export declare const ruleYamlSortKeysOptionsAnsiblePlaybooks: RuleYamlSortKeysOptions;
export declare const ruleYamlSortKeysOptionsAnsibleMeta: RuleYamlSortKeysOptions;
export declare const ruleYamlSortKeysOptionsAnsibleRequirements: RuleYamlSortKeysOptions;
export declare const ruleYamlSortKeysOptionsMolecule: RuleYamlSortKeysOptions;
//# sourceMappingURL=ansible.d.ts.map