Last verified: October 5, 2026
What You Can Now Do
Context Memo now lets you create Problem Graph memos manually without waiting for the hopper queue to clear. The depth gate that previously blocked manual creation during periods of high system load has been removed from that path. In practice: the create action on a Problem Graph node stays available regardless of how much work is sitting in the shared generation queue (the "hopper"). You no longer have to check whether the system is busy before you act on a gap. If you spot a problem cluster where a competitor is getting cited and you aren't, you create the memo at that moment instead of putting it on a list to retry later.
Where It Is in Context Memo
This lives in the Problem Graph area of the dashboard. Open a problem node and the manual memo creation control is active on the screen; it no longer returns a queue-depth error or renders as disabled while the hopper is deep. The same change applies to the API route behind manual creation, so if you trigger Problem Graph memo creation programmatically, the gate is gone there too.
How to Use It
- Open Problem Graph from the dashboard and select the problem node you want covered. You'll see the prompts mapped to it and which sources are currently being cited.
- Trigger manual memo creation on that node. Generation starts on submission rather than deferring behind the queue check, and the memo appears in your drafts as in-progress.
- Review the draft for factual accuracy and positioning before it goes anywhere. Correct any claim that your own team wouldn't sign off on, since this is the content you're asking models to treat as a source of truth.
- Publish to your own domain. Schema marking and your publishing settings apply as they do for any other memo, so the memo is crawlable as a citable source rather than a dashboard artifact.
- Watch the node in subsequent multi-model scans to see whether the answers on those prompts start referencing your memo. That is the signal to repeat the pattern on adjacent nodes or to revise the memo.
Why We Built It
Customers told us plainly that they didn't want to wait for the system queue to drain before manually creating a Problem Graph memo. The gate existed to protect generation capacity under load, but it put a platform condition between a marketer and a decision they'd already made. The cost was timing: a gap identified in the morning sat untouched because automated work happened to be queued ahead of it, and the urgency that made the gap worth acting on faded before the memo existed. Manual creation is a deliberate act, and it should not be rationed by background load.
What It Does Not Do Yet
Removing the gate removes the block, not the work. A few limits are worth being precise about:
- Automated generation still goes through the hopper. Auto-memo runs and other queued jobs continue to respect queue depth. This change applies to manual Problem Graph creation only.
- Throughput is unchanged. Generation still takes the time it takes. If you submit several manual memos at once during heavy load, they will complete in order rather than instantly.
- Nothing about review changed. The memo is a draft until you approve and publish it. We did not shorten the path between creation and your domain, and we don't intend to.
- Citation timing remains downstream of indexing. Creating a memo faster does not change how quickly models and crawlers pick it up. That depends on publishing, indexing, and scan cadence.
One more thing worth saying about where this fits. Faster manual creation helps most when you already have a domain with content on it and some crawl history behind it. If you're pre-launch with no published presence, the constraint isn't queue depth, it's that there's nothing for models to attribute authority to yet. Build the foundational content first, then use the Problem Graph to decide what gets covered next and in what order.