Review and approve a Self-Learning proposal

Proposals are the AI’s concrete suggestions for fixing a recurring issue — a system-prompt edit, a knowledge article draft, a routing tweak. They land in Staged Changes and don’t take effect until you approve them.

Before you start

• Full access to Self-Learning (review-only users can see proposals but not approve them)
• At least one proposal in the queue. If there aren’t any yet, your stack hasn’t received enough feedback to generate proposals — flag a few responses first.

Steps

1. Open Settings → Self-Learning and click the Staged Changes tab.
2. Each row in the queue is one proposal. The row shows the proposal type (prompt edit, KB article, handbook article, routing update, temperature adjustment), the specialist or stack it targets, and a one-line summary of what would change.
3. Click a proposal to expand it. You’ll see:
   The Feedback Group that triggered it (and how many flags went into it)
   A diff: the current value on the left, the proposed value on the right
   A summary of why the proposal was generated
4. Decide:
   Approve — the change deploys to your stack immediately. The proposal moves to “Deployed” status and an entry appears in the Audit Log.
   Reject — the change is discarded. The Feedback Group stays open in case a different proposal makes more sense later.
   Dismiss — useful for “this is fine as-is, stop suggesting changes.” The group is closed and won’t generate new proposals.
5. Repeat until the queue is empty (or until you’ve reviewed enough for one sitting).

Verify it worked

For an Approved proposal:

• Check the Audit Log tab. The change appears with your name, the timestamp, and a copy of the before/after.
• For prompt-edit and routing-update proposals, open the targeted Agent Stack and confirm the change is reflected in the specialist’s system prompt or the routing rules.
• Test the stack with a question similar to the ones that triggered the feedback. The new behavior should match what the proposal promised.

Reverting a deployed change

If a deployed change turns out to be wrong, you can revert it from the same Audit Log entry. Reverting restores the previous value and records a new audit entry — your stack stays auditable end-to-end.

Troubleshooting

• Symptom: I can’t see the Staged Changes tab. Fix: Your account has review-only access to Self-Learning. Ask an admin to grant full access.

• Symptom: A proposal looks risky and I’m not sure. Fix: Reject or leave it pending. Feedback Groups keep accumulating annotations even after you reject a proposal — a stronger pattern usually produces a better proposal next time.

• Symptom: My approval didn’t seem to change anything. Fix: Some proposals (KB or handbook articles) create a new draft article rather than modifying the live behavior directly. Check Knowledge Base or Handbook for the new draft.

See also

• What is Self-Learning?
• Flag and tune bad responses