I recently built FateFolio (https://fatefolio.com), an AI-powered toolkit for structured Eastern metaphysics reports.
The idea is simple: take traditional systems like Bazi, I Ching, Feng Shui, palm reading, face reading, and auspicious date selection, then turn them into clear, reviewable, exportable reports instead of vague one-off answers.
I did not want FateFolio to feel like a mysterious black box. I wanted it to feel more like a structured analysis dashboard.
Why I built it
A lot of AI products in this space have the same problem.
You type a question into a chatbot, get a fluent answer, and then you are left wondering:
- What input did the answer rely on?
- Which part is traditional calculation and which part is interpretation?
- Can I save the result?
- Can I compare it with another report later?
- How confident should I be about the output?
That was the core product problem I wanted to solve.
FateFolio treats these traditional systems as frameworks for self-reflection and decision support. It is not designed to replace professional advice or guarantee outcomes. The goal is to make the output easier to understand, easier to revisit, and easier to use as a personal reflection tool.
What FateFolio does
FateFolio currently includes several modules.
Bazi
The Bazi module creates a Four Pillars report from birth date, optional birth time, gender, and timezone.
It focuses on things like:
- Four Pillars chart
- Heavenly Stems and Earthly Branches
- Five Elements balance
- Ten Gods
- Life themes
- 12-month rhythm
- Input uncertainty when birth time is missing
This was one of the most interesting modules to design because part of the result is deterministic calculation, while another part is explanation and interpretation.
So the product has to separate the two clearly.
I Ching
The I Ching module lets users ask a focused question, choose a casting method, and receive a structured reading.
The product supports multiple casting methods, including coin casting, time casting, character casting, Plum Blossom, yarrow stalks, direction casting, and sound casting.
The report is not meant to give a single absolute answer. It is meant to help users reflect on momentum, risks, timing, and possible next steps.
A good I Ching experience depends heavily on question quality, so the interface encourages open-ended questions instead of binary prediction questions.
For example, instead of asking:
Will I succeed?
A better question would be:
What should I consider before moving forward with this opportunity?
That small UX detail changes the quality of the whole experience.
Feng Shui
The Feng Shui module works with room photos or floor plans.
Users can upload an image, select the scene type, choose goals like sleep quality, career, relationships, focus, or energy flow, and receive practical suggestions.
The report focuses on visible layout issues first:
- Door and window positions
- Bed or desk placement
- Lighting
- Flow
- Furniture relationships
- Yin-Yang and Five Elements balance
I wanted this module to feel useful even for people who are not deeply familiar with Feng Shui. So the output tries to explain the reasoning behind each suggestion instead of only saying "move this object here."
Face Reading and Palm Reading
The face reading and palm reading modules are image-based.
For face reading, the product looks at observable facial features and turns them into self-observation notes. For palm reading, it detects palm lines, hand shape, and visual patterns, then generates a structured report based on traditional palmistry concepts.
These modules required extra care around privacy and boundaries.
Images are processed in memory and are not stored by default. The product also does not perform facial recognition, identity matching, or medical diagnosis.
That boundary is important.
The purpose is self-reflection, not labeling people.
Auspicious Date Selection
The date selection module helps users compare possible dates for events such as weddings, moving, business openings, travel, and other life events.
Instead of giving only one "best" date, it returns multiple date options with reasoning, cautions, and planning notes.
This is another place where product design matters.
A date may be symbolically favorable, but real-world constraints still matter: venues, people, travel, cost, preparation, and timing. The report makes that explicit.
Why structured output matters
The most important design decision in FateFolio is that the product is not just a chat interface.
Every module is designed around a report structure:
- Summary
- Details
- Recommendations
- Confidence
- Boundaries
- Exportable data
This makes the output easier to review later.
It also makes the product easier to improve because each module can follow a stable schema. The user is not just receiving a paragraph of text. They are receiving a report with sections, priorities, and uncertainty notes.
For deterministic inputs, FateFolio also uses input hashing to make outputs more stable and reproducible where possible.
That does not mean every AI-generated sentence will always be identical. But the underlying calculation and report structure can stay consistent.
The product principle: traditional input, modern constraints
One challenge with building this type of product is tone.
If the tone is too mystical, it can feel vague.
If the tone is too technical, it loses the cultural context.
If the product overclaims, it becomes irresponsible.
If the product underexplains, it becomes useless.
So the product principle became:
Traditional frameworks, modern constraints.
That means:
- Explain uncertainty clearly
- Avoid fear-based language
- Avoid absolute claims
- Keep professional boundaries
- Give practical suggestions
- Make reports saveable and exportable
- Make privacy part of the product, not an afterthought
FateFolio is for entertainment, self-reflection, and decision support. It is not medical, legal, financial, or professional advice.
Privacy was part of the product from the beginning
For image-based modules, privacy is especially important.
FateFolio processes uploaded images in memory and does not store them by default. Local history is stored in the browser unless the user chooses to export it.
That design choice affects the entire product experience.
It means users can try a reading without needing an account. It also means the product does not have to collect more personal data than necessary.
For a product that deals with birth data, personal questions, face photos, palm photos, and home layouts, this is not a small detail.
It is central to trust.
What I learned while building it
The biggest lesson from building FateFolio is that AI products need more than a prompt.
A prompt can generate text.
A product needs structure.
For this kind of AI application, the hard parts are:
- Input design
- Output schema
- Safety boundaries
- User expectations
- Privacy flow
- Error handling
- Explanation quality
- Repeatability
- Cultural sensitivity
The AI model is only one part of the system.
The real product is the workflow around it.
What is next
There are still many things I want to improve.
Some directions I am exploring:
- Better report comparison
- More transparent confidence scoring
- More multilingual support
- Better export formats
- More educational glossary content
- Follow-up questions after a report
- A cleaner history dashboard
The long-term goal is to make FateFolio feel less like a novelty tool and more like a structured personal insight workspace.
A place where users can ask a question, generate a report, review the reasoning, understand the limits, and come back later with more context.
Final thoughts
FateFolio is my attempt to combine traditional Eastern metaphysical systems with modern AI product design.
Not as a prediction engine.
Not as a replacement for real-world judgment.
Not as professional advice.
But as a structured, privacy-conscious, AI-assisted reflection tool.
For me, the interesting part is not just what the AI says.
It is how the product frames the question, structures the answer, explains uncertainty, and helps the user think more clearly.
Top comments (0)