An operation is the conceptual unit that sits between a skill (the high-level discipline) and a shortcode (the 11ty implementation mechanism). It is the human-readable form of a shortcode — the contract that says "this is what to do," in language a contributor or Claude Code can reason about without having to read 11ty syntax.

In Claude Code's workflow:

1. Determine which skill applies (which discipline).
2. Determine which operations are needed (what to do, abstractly).
3. Determine the shortcode invocation (how to write it in 11ty).

For 1:1 cases — most current operations in the system — an operation maps to one shortcode. For 1:N cases (like the changeProposal operation, which has three modes each backed by its own rendering partial), an operation aggregates multiple shortcodes that share a conceptual purpose.

The architectural promise of the operation layer: Claude Code reasons about operations (high-level), not about shortcodes (low-level 11ty). When the implementation changes — a refactor, a mode added, a partial swapped — the operation's contract stays stable so the higher-level reasoning doesn't churn.