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 0.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

npm install completes, tsc --noEmit passes, 5 test suites pass (pan-integrity 768 charts, dst-cn, sizhu-lichun-boundary, hongluan-tianxi, famous-hour-consistency), dev server starts on port 3000 and serves HTTP 200.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
1
last tested
stars
4,318
forks
870
open issues
7
watchers
22
size
0 MB
created
last push

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.

Install time
under a minute
Cold machine to finish
3 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
npm test exited 0 (5 suites all passed); curl -s -o /dev/null -w HTTP_%{http_code} localhost:3000 returned HTTP 200 with rendered HTML
Model tokens used
18,528
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.

import { generateChart } from '../../lib/ziwei/algorithm';
import type { BirthInfo, ZiweiChart } from '../../lib/ziwei/types';
const BR = ['子','丑','寅','卯','辰','巳','午','未','申','酉','戌','亥'];
const PALACE_12 = ['命宫','兄弟','夫妻','子女','财帛','疾厄','迁移','仆役','官禄','田宅','福德','父母'];
let failures = 0;
Everything installed, built, and ran without a single error. Here's the final report:
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 0…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 0.47, "errors": [], "test_…
tokens used
18,528

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 0.5 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 0.5 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.01

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.

[![Tested by Argusic](https://argusic.com/badge/ziwei-doushu.svg)](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 0 minutes, hitting 0 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. One attempt is 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.01: 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?
0.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?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for ziwei-doushu?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion