The short version
The core BaZi content is currently written mainly by Xiaohe and reviewed by Xiaohe and Yuxuan together. It draws on BaZi books, teaching materials and real cases, and is rewritten in Destiny Book's own structure rather than copied from the source.
1. Who is accountable for the content
Destiny Book is not an anonymous, bulk-generated article library.
The core BaZi knowledge, terminology, worked cases and methodology notes on the site are written in-house, with named people responsible for both writing and review.
2. Xiaohe | Product and content lead
Xiaohe is mainly responsible for
- Product design and direction
- What the product does, how it is organised, and where each capability stops.
- BaZi fundamentals and terminology
- Definitions, lookup methods and source attributions for the fundamentals and the glossary.
- Organising different analytical frameworks
- Keeping the conventions of different schools separate and noting where each applies.
- Case selection and question design
- Which cases to include, how to break them down, and how to phrase the questions.
- Article writing
- Knowledge articles, methodology notes and product copy.
- Final content review
- Final sign-off on knowledge content.
Official accounts
- Threads
- @xiaohe5568 · Destiny Book's official account
- Xiaohongshu
- Destiny Book's official account
Xiaohe is the product and content lead. The work covers product design, knowledge structure, topic selection, organising BaZi knowledge, writing articles, organising worked cases and final content direction.
The existing content draws on BaZi books, teaching materials and real cases. The work is not to copy the source text, but to understand and reorganise it in Destiny Book's own structure.
3. Yuxuan | Engineering lead and content review
The work covers website and server development, integrating the chart engine, server and service reliability, the multilingual system, technical releases and other infrastructure. For content about system capabilities, calculated results, field meanings and actual product behaviour, Yuxuan checks the technical side.
Yuxuan builds and maintains the core technical system behind Destiny Book, and takes part in reviewing knowledge content.
4. Marketing and operations
Destiny Book also works with a marketing collaborator on content promotion, channel operations and collecting user feedback.
We do not invent job titles to look bigger. This page is updated as responsibilities change.
5. Bylines and attribution
Knowledge articles are, in principle, attributed to an author and a reviewer.
We want readers to be able to see who wrote a piece, who checked it, and when it was last updated.
Article pages show the author, the reviewer and the update date.
Where an article quotes a classical source, the citation points to the volume and section so readers can check the original.