How Nudge works.

Use the authenticated dashboard or email Nudge like you would a teammate. "Can you swap the homepage photo?" "Please update our office hours." "Take down last weekend's event." Email contributors do not need CMS access. SMS is not available yet.

Nudge interprets the request as a conversation. It knows who you are, what you're allowed to do, and asks clarifying questions when it isn't confident about what you mean.

Every change gets a risk level: low (typo, expired event, alt text), medium (new page from a template, homepage callout), or high (nav changes, forms, brand). Risk settings determine routing, but no change may publish until required preview QA and exact-commit checks pass.

You get a plain-language plan back: what will change, where, and what it'll look like. Approvers can approve, revise, or reject from the application or supported email thread.

The production publishing and rollback workflow is still being completed. Preview QA fails closed and a merged pull request is not labeled published until live-site verification exists.

Automated health reporting is paused until route, link, accessibility, performance, repository, and deployment findings come from measured checks with stored evidence.