ziwei-doushu
紫微斗数开源排盘引擎, 基于倪海厦《天纪》体系,含完整排盘算法、四化系统、格局知识库、古籍原文数据
Runssource: GitHubhomepageTypeScriptMITcommit 9d98b3ae7fce
TypeScript, MIT licensed. The project labels itself: bazi, chinese astrology, divination, fortune telling, nextjs, open source, purple star astrology and typescript.
ziwei-doushu runs. An Argusic agent installed it in 5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Dependencies install, typecheck, build, the 5-suite regression test set, and both dev (next dev) and production (next start) servers all run; 13 routes answer HTTP 200 with rendered pages and the generateChart engine returns valid 12-palace charts.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- /knowledge/[star]/[topic] detail pages return 404 (NoFallbackError in server log)3 minutes
- Engine check script failed with MODULE_NOT_FOUND for './lib/ziwei/algorithm' when run from /tmp (relative import resolved against script dir)1 minute
- Production server appeared ready but was killed when the launching shell exited, so curls returned 000 connection refused1 minute
- Install time
- 5 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test exited 0 (5 suites: 768-chart pan-integrity, DST 24106-day diff, lichun boundary 10 assertions, hongluan-tianxi, 11 famous samples); curl on live Next servers returned 200 for /,/chart,/heming,/knowledge,/library,/library/gusuifu/0,/library/search?q=紫,/preview,/privacy,/terms,/robots.txt,/sitemap.xml; npx tsx engine check printed 12 palaces and 命宫 stars 武曲,天府
- Model tokens used
- 136,704
- Exact commit tested
- 9d98b3ae7fce
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
elapsed_min=4
?? package-lock.json
Elapsed ~4.6 min (bucket: 5). Working tree is clean except the new `package-lock.json` from install…
exec
/bin/sh -lc "cd /work/repo && curl -s -o /dev/null -w \"final_home_status=%{http_code}\\n\" http://…
succeeded in 55ms:
final_home_status=200
All checks done. Final report:
2026-11-03T20:42:07.535962Z ERROR codex_core::session: failed to record rollout items: thread 01a1a…
tokens used
136,704
All checks done. Final report:Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 5 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
bazichinese-astrologydivinationfortune-tellingnextjsopen-sourcepurple-star-astrologytypescriptzi-wei-dou-shuziwei-doushu
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ziwei-doushu)Questions
- Does ziwei-doushu run?
- Yes. ziwei-doushu runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test ziwei-doushu?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9d98b3ae7fce. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ziwei-doushu?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ziwei-doushu take to install?
- 5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does ziwei-doushu need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ziwei-doushu?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for ziwei-doushu?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.