How Your Question Changes What Bokki Actually Shows You

"What brings you here today?" looks like small talk before the real reading starts. On Bokki's home screen it is a routing decision — one of seven fixed branches, each pointing at a calculation that already exists.

Bokki Editorial

The short answer

Bokki's home entrance offers seven question branches — work, money, love, exams, health, picking a good day, or just today with no particular question — and reads your chart through whichever lens you pick first. None of the seven creates a new calculation: work, money, love, exams and health each point to one field of the same rich per-topic reading Bokki already computes; picking a day points to the dedicated date-scoring tool; today falls back to the general personality reading. Type a free-text question instead of tapping a card, and Bokki matches it against the same seven branches by keyword — with one honest limit: if nothing matches, the answer is "I don't know which one you mean," not a guess.

The arithmetic — keywords derived, not hand-copied, and checked in one direction only

Bokki doesn't maintain a second, hand-written keyword list for the free-text box. Each branch's keyword set is derived on the spot from two things that already exist: the search keywords that branch's linked tool page has already committed to answering (from a shared table also used for SEO), and the branch's own label text in whichever language the user is on, split on separators like the middle dot and comma. Any resulting word shorter than two characters is dropped. The matching check then runs in exactly one direction: the code asks "does the typed sentence contain one of this branch's keywords?" — never the reverse. That direction matters. The Korean label for the work branch, "일·이직," splits into "일" (one character, work/day) and "이직" (two characters, job change); the one-character word gets dropped by the length filter specifically so it can't fire on an unrelated sentence like "money-making trip to 일본 (Japan)" — the sentence contains the substring "일," but "일" itself was never a live keyword to begin with, and "이직" isn't in that sentence at all, so nothing matches.

Worked example — three real inputs, three real outcomes

Running the actual matching function on realistic input: "이직 고민중이야" (thinking about changing jobs) contains "이직," so it lands on the work branch, which links to the career reading. "돈 벌러 일본 갈까" (should I go to Japan to make money) matches nothing — it's the exact case the source code's own comment warns about, and the one-way, length-filtered check keeps it from a false hit. "이사 날짜 언제가 좋을까" (when's a good date to move) contains a keyword from the picking-a-day branch and links to the date-picking tool — honestly, though, that branch has no matching field in the rich per-topic reading at all (moving and dates fall outside the seven fields wealth, career, love, study, health, personality and relationships cover), so rather than inventing a moving-specific reading, Bokki only ever points it at the existing tool. A sentence that matches nothing, or simply tapping through without typing, falls back to the "just today" branch, which reads the general personality field with copy that acknowledges no specific question was asked.

Seven doors, and a one-way keyword checkBokki's home entrance offers seven fixed question branches — work, money, love, exams, health, picking a day, or just today — each pointing at a calculation that already exists (a field of the rich per-topic reading, or a dedicated tool screen). Free-text input is matched against keywords derived from those same seven branches, but only in one direction: the code checks whether the typed sentence contains a branch's keyword, never the reverse. That single-direction rule is what keeps a short keyword like 이직 (job change) from firing on unrelated text, while a longer sentence that happens to contain it still matches."contains a keyword?" — one direction only"이직 고민중이야"→ work"돈 벌러 일본 갈까"→ no match (not 일)"이사 날짜 언제가 좋을까"→ picking a daythe seven fixed branches: work · money · love · exam · health · days · todayno match → null, not a guess

What we don't compute

The free-text sentence itself is never saved — matching happens on the visitor's own device and only the matched branch id, if any, is kept, the same privacy stance Bokki takes with other free-text inputs. The system never scores how well an input matches, only whether it matches at all — there's no "70% confident this is about money." And when several branches' keywords could technically be found in one long sentence, the branch that happens to come first in a fixed internal list wins; that's an implementation detail Bokki isn't dressing up as intelligence, and the far more common outcome by design is either one clean match or none at all.

Closing note — a routing question, not a new fortune

In short: Bokki's entrance question isn't a personality quiz bolted onto the reading — it's a keyword router built entirely from tables that already exist, checked in one direction to avoid short-keyword false hits, and honest about the one branch (picking a day) that has nowhere existing to plug into a rich reading. "이직 고민중이야" and a tap on the work card land in exactly the same place; a sentence that matches nothing gets told so instead of a guessed answer.

← Get my reading

Read next

Get a real Saju reading →
How Bokki picks today's one-line message
Your daily fortune radar: how the six numbers are calculated

Questions people actually ask

Does typing a free-text question compute something new?

No. All seven branches — including free-text matches — point at a calculation Bokki already runs, either one field of the existing rich reading or an existing tool screen.

Why didn't my typed question match any branch?

If the sentence doesn't contain a keyword derived from one of the seven branches, Bokki says so honestly instead of guessing — the fallback is "I don't know which one you mean," not a made-up answer.

Why does a short word like '일' (day/work) not trigger a false match inside longer words?

Keywords shorter than two characters are dropped before matching, and the check only asks whether your sentence contains a branch's keyword — never the reverse. That combination is what keeps a one-character word from firing inside an unrelated word like 일본 (Japan).

Is my typed question saved anywhere?

No. Matching happens on your own device, and only the matched branch (if any) is kept — the original sentence itself is not stored.