Spec — turn the idea into something engineering can scope
Paste the idea once. It stays in this box across all three lanes, so the spec, the roadmap placement and the stakeholder update are all about the same thing.
It cannot see anything you did not paste
Not your roadmap tool, not your analytics, not your org chart, not the thread this idea came from. A claim that would need one of those is reported as an unknown rather than stated as a fact.
It never invents a number
No engineer-week estimates it made up, no user counts, no dates, no percentages the paste does not support. If your idea carries a number it is used and attributed; if it does not, the gap is named.
It cannot bump an initiative it never saw
Items the roadmap lane moves are drawn verbatim from what the in-browser parser found in your paste. If the parser could not read your board with confidence, the lane says so and bumps nothing — and the reconciliation panel says so again if the model tries anyway.
It is a drafting aid, not a decision
Feasibility belongs to engineering, the experience to design, and anything touching regulated data to legal. When the idea implies one of those, the lane routes it rather than answering it — and you stay accountable for the spec that goes into planning.