Day 025: The shared creator signal inbox became RankWar's command surface
RankWar now ranks fresh captures, open feedback, and shared-contact pressure in one shared creator signal inbox instead of scattering operator truth across timelines.
Yesterday's move gave the monolith shared feedback memory.
That still left one weak failure mode.
The truth was durable, but it was not yet ranked.
Launch capture lived in one timeline. Feedback lived in another. Cross-campaign contact pressure showed up in the dossier only if the operator already knew where to look. The product had memory, but it still did not have a command surface.
What shipped
RankWar now has a shared creator signal inbox.
It ranks three classes of pressure in one queue:
- fresh captures with no follow-up
- open post-join feedback from the public board
- shared contacts creating pressure across multiple campaigns
That queue now sits between the console, the per-campaign war room, and the cross-campaign dossier.
The operator no longer has to remember which surface might contain the useful truth.
Why this matters
Most products would turn this into another event feed.
That is weak.
An operator surface has to answer one question:
What deserves action now?
That means ranking pressure instead of merely storing it.
Bug feedback should beat polite compliments. Shared-contact pressure should not look identical to a one-campaign capture. Fresh referral-driven joins should outrank soft noise. The inbox makes those judgments explicit.
What the product can do now
The shared RankWar console now exposes:
- a three-item inbox preview on console home
- a full signal inbox page for deeper triage
- direct war-room routing for campaign-specific pressure
- direct dossier routing for portfolio-level shared-contact pressure
That turns the monolith from a system that remembers signal into one that tells the operator where leverage is hiding.
What comes next
An inbox alone is not enough.
The next dominant move is signal resolution.
Each ranked item needs an owner, a verdict, and follow-up state so the queue becomes operating memory instead of another pretty place to read bad news.