profile-backed feedback: every flag now has to explain itself
profile-backed feedback: every flag now has to explain itself
the editor had a gap.
it could mark a phrase. it could say the phrase sounded generic, too polished, too soft, too long, or too far away from the profile. but a user still had to trust the flag without seeing the evidence behind it.
that is not enough. if the product says a sentence does not sound like you, it should also say what it used to make that call.
what changed
profile-backed feedback adds a small evidence layer to the editor. not a new workflow. not another screen. the same highlighted text now explains whether the signal came from the profile, the samples, the selected format, a known ai pattern, or the user's own accept and dismiss history.
get started for $1 — create your account and scan your first draft in minutes.
get started for $1 →
why does the source of a flag matter?
a flag without a reason trains people to ignore flags. users either accept every suggestion or dismiss the whole system. neither behaviour improves the writing.
source labels make the boundary visible. an ai-pattern flag is a different claim from a profile mismatch. one points to a construction that often reads as machine-made. the other says this sentence does not match the writer's own baseline.
what counts as evidence from a profile?
the profile is built from the writing samples and the decisions made while using the editor. it can show that you tend to use shorter openings, concrete nouns, fewer transitions, or a particular level of directness.
that evidence should stay modest. a profile can describe a pattern in your writing. it cannot turn a preference into a law. the editor should explain the signal and leave the final call with you.
how should you use the new feedback?
start with the flags that have the clearest evidence and the biggest effect on the draft. repair one line, rescan, and keep the original if the rewrite loses something useful.
the goal is not a clean dashboard. the goal is a draft where you understand every change you accepted.
writes about brand voice, ai writing patterns, and the craft of sounding like yourself. built hold your voice after watching his own voice flatten across six months of heavy ai drafts.
co-written with ai as sidekick. shashank drafted the observations; the ai pressure-tested the structural claims. if something reads too smooth, that's the ai's fault.