My situation is too complicated for one question

The cursor blinks and you close the tab

You know the feeling. The box wants one clean question. Your situation has four people, two deadlines, an old grievance, and a thing you'd rather not say out loud. So you either dump 400 words or you type nothing and go make tea. Both feel like failure. Neither is.

The dilemma (a composite of the kind we see in this category)

Meet Priya. She is not real — she's a composite of the tangled intakes we see under how-it-works. Here is what she pastes in, verbatim, at 11pm:

Okay so I don't even know how to ask this. My manager Rahul keeps 'restructuring' my team and last month he moved Anjali off my project without telling me which honestly is so like him, he did the same thing in 2022. Rent went up again, my landlord is a nightmare, and my lease renews in March. Meanwhile there's this other role at a smaller company — my old boss Dev works there now and he messaged me, said the team's great, but Dev also once took credit for my dashboard so I don't fully trust him. My sister thinks I should 'just be grateful I have a job.' My partner is neutral which isn't helpful. I make decent money but I feel invisible. I've been at this company four years. Do I stay and try to fix things with Rahul, or do I leave? Or do I wait until after March? Or do I just talk to Rahul first? I keep going in circles. Everyone has an opinion. I don't even know if leaving is about the job or about being tired of being overlooked. Help.

Four hundred words of true, tangled life. And buried in it: one real fork. Watch what the reading does.

The read: what the intake keeps, and what it sets down

The first job is not to answer. It's to find the decision. A sprawl like Priya's contains at least three separate questions wearing one coat. The reading splits them.

The tangents get set aside, not deleted. The landlord and the rent are context — they raise the stakes of any move, but they don't have two branches Priya controls. Rahul's 2022 restructure is history; it colors her read but isn't a fork. Her sister's opinion is weather. None of these get scored. They get parked as background so the actual choice can surface.

The buried second question gets named. "Do I talk to Rahul first?" is a real action — but it's a different decision than "stay or leave," and answering it first would just delay the fork, not resolve it. The reading flags it as a separate later question. "Wait until March" gets the same treatment: it's a stall dressed as an option, because nothing about March changes the facts.

What's left is the fork with two named branches:

• Option A: Stay and rebuild the relationship with Rahul.
• Option B: Take Dev's role at the smaller company.

Now the eight lenses have something to bite on. Three of them bite hard here.

Motive (−2 on Option B)

The lens in one line: what's the engine actually driving this, versus the reason you'd say out loud? On Option B, the stated engine is "better team." The buried engine is the sentence Priya wrote herself and then rushed past: "I don't even know if leaving is about the job or about being tired of being overlooked." That's not a job search. That's an exit from a feeling. Motive scores negative because the move is partly aimed at Rahul, not at the new role. A dump hides this line in paragraph three. A read pulls it to the front.

Discernment (−1 on Option B)

The lens: are you seeing the new thing clearly, or through the fog of the old thing? Dev "once took credit for my dashboard." Priya's escape hatch has the same defect she's fleeing — being made invisible. Discernment flags that she hasn't actually verified the new team is different; she's verified that it isn't Rahul. That's not information. That's contrast.

Duty (+2 on Option A, but conditional)

The lens: what does your role and your word actually oblige? Four years in, with a manager she has never once directly told, duty leans toward the conversation she keeps swapping for a resignation. But — and here is the tension — duty and motive disagree. Duty says the honest move is to name the invisibility to Rahul before quitting on it. Motive warns that if she's already left in her head, the conversation becomes theater. Two lenses, two directions. That gap IS the finding.

The committed verdict: Option B is a re-run of the wound, not an exit from it — have the direct conversation with Rahul first, because until she's said the invisible-sentence to the one person who can change it, she can't tell an escape from a decision.

Why this isn't the box that agrees with you

Paste that same 400-word sprawl into a general AI chatbot and watch it mirror your last paragraph. Lead with "I'm so tired of being overlooked" and it warms you toward leaving; lead with "I've built four good years here" and it talks you into staying — that agreeable-to-your-framing tendency is an observed behavior in these systems, and you can reproduce it yourself in two tries. KarmaLens works the other way by design: before the call, it asks the decisive unknowns first, then makes one committed call — not a reflection of whichever mood shaped your last sentence. Where the eight lenses of the Gita bear on your decision, they show the weighing honestly; they don't re-weight themselves to flatter how you typed things in. The call reads the same at 11pm and at 8am, because it is made once, on the facts, and it doesn't renegotiate when your wording shifts. A chatbot rewards the paragraph you dumped. The read is built to survive it.

The takeaway: the fork-and-park test (do it tonight, free)

You don't need us to try this on your own knot right now.

1. Dump it. Write the whole tangled thing. Every person, every grievance, every deadline. Don't clean it up.
2. Underline every distinct action you could actually take. Not feelings — verbs you control. "Talk to Rahul," "take Dev's role," "wait until March."
3. Cross out any verb that only delays without changing a fact. "Wait until March" changes nothing, so it goes. This kills the stalls.
4. Cross out any verb that's really a different decision. "Talk to Rahul first" is a separate question — park it on a second line to answer later.
5. What's left should be exactly two branches. If you have three, you have two dilemmas — pick the one with the nearest deadline and set the other down.

Then score just those two branches on motive — out-loud reason versus 2am reason — and read the flinch. If the sign flips between them, you found your real engine before you spent a word explaining yourself. The knot didn't get simpler. You just stopped scoring the noise.

The paradox

Here's the strange part: the messier your dump, the more the fork stands out once the tangents are parked — noise makes the signal obvious by contrast. You don't have to be articulate. You have to be willing to name the choice, and if you can't, the reading is built to find it under everything you wrote around it. When you're ready, bring your own knot to the door — the box is smaller than your situation, and that's the point. (Want to see it work first? Browse how other tangled inputs resolved in the gallery.)

What's the one verb in your dump that you keep circling and never actually cross out?