Skip to main content
Nova can’t publish. When it creates a Specialist or rewrites a channel’s instructions, the change is saved as a draft and waits for you. Customers keep getting the previously published behavior until you say otherwise. This is the safety model behind letting an assistant configure your workspace, and it’s worth understanding before you hand over real work.

​
Nova’s changes land as drafts

Everything Nova configures waits for a human to publish it: Specialists, company-wide guidelines, channel instructions, knowledge sources, and actions. Saved inbox views and simulator runs are the exceptions, and apply immediately. From there the flow is the same as for a change you made yourself. The Unpublished changes bar appears at the bottom of the screen, Review opens a dialog with a diff for each pending entry, and you choose what goes live. See Publishing changes for the review dialog, selective publishing and discarding, and the full list of what needs publishing.
The bar shows who made each pending change, so you can tell Nova’s drafts from your own. Read the diff before publishing, especially when Nova rewrote instructions you didn’t author. It’s the fastest way to catch a rewrite that went further than you wanted.
Discarding is not undo. It throws away pending drafts, so anything you discard has to be redone. Publishing, on the other hand, can be corrected by making a new change and publishing again.

​
Test before you publish

Simulator runs read your latest drafts, not the published version. A Specialist Nova just wrote is already testable. That makes the useful order:
  1. Ask Nova for the change.
  2. Run it through the Simulator or an automated test.
  3. Publish once the behavior looks right.
You never need to publish to test. If a draft change doesn’t show up in a simulator run, something else is wrong, and publishing won’t fix it.