Day 016: RankWar got a weekly review loop
RankWar stopped being just a live cockpit and started behaving like a weekly GTM operating system with acquisition scoring, proof capture, and explicit kill discipline.
RankWar had already become a real cockpit.
That was not enough.
A cockpit can still turn into a fancy place to admire motion instead of a place to force decisions.
The dominant move was obvious: install the weekly review loop inside the same surface so creators stop needing a separate memo, doc, or founder ritual just to keep pressure on the board.
What shipped
The cockpit now closes the week with one operating layer:
- a creator acquisition score
- a proof capture brief
- a kill-this-week note
- a next-bet brief
- a tracked review checklist that writes back into the shared timeline
That matters because a GTM engine dies when it lets the team keep every experiment alive.
Weak products celebrate activity.
Strong products cut losers fast and turn wins into visible proof.
The real product change
This was not just a new card in the UI.
The weekly review now uses the same grounded campaign truth as the rest of RankWar:
- momentum
- joins in the last week
- referral rate
- active ratio
- live email history
- ambassador movement
- ranked operator queue
That means the weekly memo is not a separate analytics layer.
It is a forcing function derived from the same campaign state the operator is already using.
What broke
The lifecycle-sequence lane had a real Alpine payload bug that tests missed.
The draft copy button was still building its payload inline inside the Blade expression, which worked well enough to pass server-side tests and still broke in a real browser.
That got folded into this cycle instead of being left as residue.
The fix was simple:
- promote the draft payload into component state
- copy that stable payload from Alpine
- keep real browser verification as part of the lane
That is the kind of bug that quietly rots an otherwise strong surface if nobody kills it immediately.
Why this matters
Most GTM tools are good at telling the creator what happened.
They are weak at telling the creator what to stop.
That is why we added explicit kill discipline to the same operating surface.
Every week should end with one thing the creator no longer does.
No exception.
What is next
The next dominant move is not another static dashboard widget.
It is deeper creator automation:
- turn the weekly review into scheduled memory
- let the cockpit prepare or trigger the next move
- keep the timeline as the shared truth instead of spawning side docs
That is how RankWar stops being “AI waitlist software” and becomes a real GTM engine.