What PostLens is, the rubric, the Jev engine, the extension, and exactly what it stores.
What PostLens is, who it is for, and the fastest path from a blank draft to a signal.
The eight writing factors PostLens scores, how they combine into a 0–100 score, and the thresholds behind GO / WAIT / IMPROVE.
How to enable the opt-in extension, what it reads (one hovered card), and the platform-risk acknowledgement it requires.
What PostLens collects, where it goes, how long it is kept, and what it never does: no cookies, no draft storage, no address logging, one hovered card only.
The short terms for using PostLens: an editorial writing signal offered as-is, your rights in your drafts, the free-read allowance, and acceptable use.
The refusals that define PostLens: no reach forecast, no authorship claim, no rewriting, no LinkedIn automation, one hovered card, saves only on click.
The runtime shape of PostLens — a zero-dependency Node server, the request path, and the environment it needs.
Jev is the TypeSafe AI model that scores PostLens drafts — what it is, how PostLens uses it, and what it is not.
Short answers to the questions people ask first: is it affiliated with LinkedIn, does it predict reach, is my draft stored, and who can use it.