StoryShell should know what happened on the public site.
NoodleNet should help the business decide what to do about it.
That boundary keeps the whole thing from becoming a bloated control room.
A click, a page view, a form open, a form submit, a scroll signal, those are web facts. StoryShell is the right place to collect them because StoryShell owns the public surface.
But a fact is not a workflow.
Signals need somewhere to go
A landing page gets visits but no form submissions.
That is a signal.
What happens next is operating work. Someone needs to review the offer, compare the CTA, look at the traffic source, maybe draft a clearer section, maybe ask whether the wrong people are arriving.
That is where NoodleNet belongs.
It can turn the signal into a task, a note, a review, a draft, a follow-up, or a small approved publishing change. AI workers can help prepare the analysis. Humans decide what the signal means.
The loop matters more than the chart
The useful pattern is publish, observe, review, improve, follow through.
If the statistics engine stops at a chart, it is only half useful.
The value comes when the business can turn public behavior into better public knowledge. A strong post becomes a follow-up article. A weak form becomes a repair task. A repeated question becomes an FAQ. A stale page becomes a draft update.
StoryShell watches the web surface. NoodleNet helps carry the work around it.
That is the ecosystem shape.