Estimate: 35m · Depends on: 6.6.1, 6.6.4, 6.1.4, 6.5.2
The authoring surface, per the 6.6.4 design, on the 6.6.1 routes — the Automation page mounted in the reserved slot of the 6.5.2 settings-nav registry (admin-gated end to end via its access predicates: the nav entry, the page, and every route 403 for non-admins).
Build: the rule list (name, toggle, owner, last-run glyph, overflow actions, empty + cap + auto-disabled-banner states); the editor with when/if/then rows driven BY THE REGISTRIES (trigger picker → its config editor kind; action rows → per-action editors; a registry addition appears with zero UI changes — the 6.1.4 pattern, asserted with a test-only entry); the If group reusing the 6.1.4 condition-row components scoped to the rule editor (match all/any + rows + cap — one predicate UI in the product); add/remove/reorder actions; save/validation surfacing the typed 422s (caps, unknown/stale referents) per the designed states; enable/disable with the counter-reset behaviour; delete with confirm. The Automation nav entry fills the 6.5.2 reserved slot (a registry entry, not a new chrome). Strings via next-intl.
A11y: the when/if/then columns are labelled groups; every picker keyboard-complete; the toggle + last-run status announced; action reorder keyboard-operable; extends the settings strict sweep.
design/projects/automation.mock.html + notes (6.6.4) — THE authority