WENBU JOURNAL

Why Wenbu shows a chart before it writes a story

The product choices behind transparent calculations, optional AI interpretation and portable context in a free reflection tool.

Fluent prose can hide an earlier mistake

If a birth time was interpreted incorrectly, a long and thoughtful-sounding answer may still be discussing the wrong input. Wenbu starts with an earlier question: how did the information you entered become this chart?

The interface therefore presents pillars, palaces, original line values or actual cards first. You can stop there, inspect the convention, compare another calculator or take the structured data to your own agent.

Give each layer a clear job

Pinned open-source libraries handle calendar calculations. Explicit random procedures produce I Ching and tarot draws. Visualizations represent the result rather than altering it to look more reassuring.

DeepSeek receives that calculation and the background you choose to share. Its role is to organize a possible reflection, not reinvent a chart, estimate an accuracy percentage or announce a fixed outcome.

Free access needs a sustainable boundary

Charts, casts, draws and the local journal do not require payment. Optional AI readings have a published per-network daily allowance and a site-wide budget. When a limit is reached, the existing chart and journal remain usable.

The calculation and record should survive a failed model call. A timeout, busy provider or exhausted daily budget should not remove the result you already have.

Keep the last step with the person

Saving a journal entry, requesting an AI reading and exporting context are deliberate actions. Wenbu does not scan conversation history in the background or put personal questions in public links.

The product will continue to improve. If two calculations disagree, a useful report identifies the input range, conventions and exact discrepancy. Use synthetic examples or remove personal information before posting publicly.

Sources & further reading

lunar-typescript · calculation source and examples ↗iztro · documentation and calculation conventions ↗DeepSeek · API model update ↗

Traditional interpretations are not established predictions. See the source notes for context.

Try it with a clearer perspective ↗