Last verified: September 15, 2026
What You Can Now Do
Context Memo now has QA demotions automatically reopen available slots and retire prompts that violate quality standards on the same day, without manual intervention. When a memo fails QA review and gets demoted, two things happen without you touching anything: the slot it occupied returns to the pipeline as available, and the prompt configuration that produced the violation is marked retired so it cannot be picked up in a later run. The decision this changes is what you do after a demotion. Before, a demotion opened a cleanup task. Now it opens a question worth answering: does that slot need a replacement prompt, or should the coverage move elsewhere?
Where It Is in Context Memo
This lives in the memo generation pipeline, on the QA review step for a run. Open a run, and demoted memos now display the slot they vacated along with the retirement status of the prompt behind them. The run summary for that same pipeline shows reopened slot counts and retired prompt counts alongside your published memos, so the QA activity is on the same screen as the output it affects.
How to Use It
- Open the current run and go to QA review. Memos flagged for demotion appear with the slot number each one held and the prompt configuration that generated it.
- Confirm the demotion. The slot flips to available in the pipeline immediately, and the next queued candidate becomes eligible for it within the same day rather than the next cycle.
- Check the retired prompt entry attached to that demotion. The violating prompt is marked retired and excluded from future generation, with the QA reason recorded against it.
- Add a replacement prompt if the topic still belongs in your coverage plan. The new configuration enters the queue and can fill the reopened slot without a separate scheduling step.
- Review the run summary before publishing. Reopened slots and retired prompts are counted there, which gives you a running read on how much of your prompt set is failing QA and on which themes.
Why We Built It
Customers told us the same thing in different words: QA demotions no longer leave slots blocked or require manual cleanup to prevent violating prompts from being reused in future runs. Before this shipped, a demotion cost two things. The slot sat blocked until someone noticed and released it, which quietly shrank the volume of memos a run actually produced. And the prompt that caused the violation stayed live, so the same failure could resurface in the next run under a different memo title, burning another QA cycle to catch it again.
That is capacity lost on work you already paid for. Citation-grade memos only move AI answers once they are published and indexed, and a blocked slot is a memo that never reached a model.
What It Does Not Do Yet
Retirement is scoped to the specific prompt configuration that triggered the violation. If you have written near-duplicate prompts elsewhere in your set, those are untouched and can still produce a similar failure. Review your prompt library by theme after a cluster of demotions rather than assuming one retirement covers the pattern.
Replacement prompts are still authored by you. The system reopens the slot and tells you what was retired, but it does not draft a compliant prompt to take its place, and it does not decide whether that coverage area is worth keeping. That judgment stays with your team.
A reopened slot also fills only if there is a queued candidate. If your prompt queue is thin, the slot will sit available until you add something to it, which shows in the run summary as a reopened count without a matching publish.
