Why the read starts with a verdict, not a menu

You already have the list.

You've had it for two weeks. On one side: say nothing, keep the peace. On the other: report it, blow things up. You know the pros. You know the cons. You have read them in your own head so many times they've gone smooth, like a worn coin. And you are no closer to moving than you were on day one.

That is the thing no menu will fix. The list isn't the shortage. The decision is.

The dilemma

What follows is a composite — the kind of workplace dilemma we see often in this category, assembled from the common shape rather than any one person.

Call her Ira, a mid-level product designer three years into a company she mostly likes. A teammate — call him Vikram, warm, well-liked, the one who remembers everyone's coffee order — shipped a flow last quarter that got singled out in the all-hands. Leadership loved it. Ira loved it too, right up until a freelancer she follows posted the original: same layout, same micro-interactions, same empty-state copy, published four months before Vikram's "redesign." Not inspired by. Lifted. Rotated two degrees and renamed.

Ira has the receipts. A side-by-side would take ninety seconds.

Here is the detail she keeps circling, the one she hasn't said to anyone: the flow Vikram got praised for is the flow she was supposed to own and handed off when she was underwater. If she reports it, the first question in the room will be why didn't you catch this. And a smaller, uglier voice notices that Vikram's praise was praise that might have been hers.

So she doesn't want advice. She wants a clean reason not to look like the person who missed it — and a clean reason not to feel like the person protecting herself by staying quiet. She wants someone to decide.

The read

When this goes into a reading, the eight lenses aren't a scoreboard that spits out a number. They're eight ways of looking at the action — reporting, or not reporting — until one way of looking clearly carries more weight than the others. Three of them bite hard here. Watch two of them disagree.

Honesty: is a false thing standing uncorrected?

The lens, plainly: truth that's cheap to tell and expensive to withhold is a debt, not a choice. What it sees here is stark. A piece of credit is sitting on the wrong desk. Leadership is making decisions — about Vikram, about headcount, about what "good work" looks like here — on a fact that is false. Ira isn't being asked to manufacture an accusation. She's being asked whether to let a known falsehood keep earning interest. This lens pulls hard toward the side-by-side.

Non-harm: who gets hurt, and how badly?

The lens, plainly: weigh the real injury each action does, not the injury you'd rather avoid feeling. And here it pulls the other way. Vikram is well-liked. A plagiarism finding doesn't just dent a quarter — in most shops it's the kind of thing that ends a tenure. That's a heavy, possibly irreversible cost landing on a real person. This is where most stuck people stall out, because honesty and non-harm are now standing on opposite sides of the table, and both are telling the truth.

So the reading doesn't pretend the tension away. It asks what non-harm is actually protecting. Is it Vikram — or is it the discomfort of being the one who says it out loud? Because non-harm that quietly launders your own exposure isn't non-harm. It's self-protection wearing a kinder word.

Motive: what's the engine under the wanting?

The lens, plainly: the same action is clean or rotten depending on the fuel. And this is the one that actually settles it. Ira notices she's a little glad about the receipts — glad she has leverage, glad there's a version where Vikram's praise drains out of the room. That's the small ugly voice. If the engine of reporting is "he took what might have been mine," the action is payback holding a document. If the engine is "a false thing is sitting in the record and I can correct it cleanly," the same action is repair.

The lens doesn't tell Ira not to report. It tells her the record has to be corrected for the record's sake — which means the move is the dated side-by-side sent to the person who owns the credit decision, stated flat, with zero adjectives about Vikram as a person. No all-hands callout. No moral framing. The fact, to the one desk that can act on it.

That same framing, by the way, is what lets non-harm back off: a flat factual correction sent privately does far less damage than a rumor Ira lets curdle by saying nothing.

The verdict: report it — privately, factually, to the credit owner, and strip every sentence of the version where this is about you. The first step is the ninety-second side-by-side, sent today, before the praise compounds into a promotion.

Notice what just happened. Honesty and non-harm genuinely disagreed, and the read didn't hand you both and wish you luck. It named the engine, used it to shape the how, and committed.

That's the mechanical difference, and it's worth saying plainly. Ask a general AI chatbot this and it will likely build you the most balanced list you've ever read — then lean the way you lean. Tilt toward silence and it agrees that peace matters; tilt toward reporting and it agrees that integrity matters. Having watched a lot of those answers, the pattern is hard to miss: a tool tuned to be agreeable tends to argue whichever side you're already on. KarmaLens is built to do the thing that tool structurally won't: ask for the facts that would change the answer first, make one committed call after them, lay the real options beside it with what each costs, quote a verse verbatim only where one actually fits — and then, when you push back on Sarathi, hold the line instead of folding into "well, it depends on you." The call gets made once, after the facts, and it doesn't renegotiate itself to make you feel better about the version you were already leaning toward.

And the verdict isn't a coin flip. It's the endpoint of eight separate reads of the same action, where the lens that bites hardest — here, motive — decides the shape of the move. You can disagree with it. You can't mistake it for a shrug.

Try this tonight, free

You don't need us to feel the difference between a menu and a call. Run the engine-swap test on your own stuck decision.

1. Write your leaning action as one flat sentence — the actual move, not the feeling. ("Send the side-by-side.")
2. Finish it twice, out loud, with two different engines: "...because a false thing needs correcting" and "...because of what it does for me."
3. Read both. One of them will feel true and one will feel like a line you rehearsed. That's your motive lens, uncoached.
4. Now here's the part that ends the loop: if the clean engine is the real one, the next question is never whether — it's how, so the ugly engine can't ride along. Private, not public. Factual, not adjectival. To the one person who can act, not to the room.

A menu keeps you deciding whether. A verdict moves you to how. The instant your question flips from "should I" to "how do I do this cleanly," you've left the loop — and you did it by committing to an engine, not by adding a seventh option.

If you've been reading your own list for two weeks, you don't have an information problem. You have a decision that won't make itself. Write the real one and get the committed call — not a tidier menu. Or read more about how the read is built, or walk through worked readings before you bring your own.

So: what's the one decision you've already listed to death — and which engine have you been too careful to say out loud?