fojin

Buddhist Digital Text Platform, 10,500+ texts, 660+ sources, trilingual cross-canon, AI Q&A (RAG), knowledge graph, full-text search · fojin.ai: paste a passage, see which lines come from the canon

Runs with mockssource: GitHubhomepagePythonApache-2.0commit b38d9cc3c87e

Python, Apache-2.0 licensed. The project labels itself: ai, buddhism, buddhist studies, chinese classics, digital humanities, docker, elasticsearch and fastapi.

fojin runs, with stand-ins for the services it depends on. An Argusic agent installed it in 18 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Backend 1929 unit tests pass, MCP server 45 tests pass, frontend builds with Node 22, app starts and responds 200 on /api/health

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 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.03 (measured)
recorded runs
1
last tested
stars
362
forks
68
open issues
12
watchers
1
size
28 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.

Time lost to each failure while testing fojin, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • Node.js 18 (system) can't build frontend — rolldown uses `styleText` from `node:util` which requires Node.js 21+5 minutes
Install time
18 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
pytest: backend 1929 passed, 29 skipped; mcp-server 45 passed; app /api/health returns 200; frontend npm run build succeeds
Model tokens used
172,766
Exact commit tested
b38d9cc3c87e
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- **Frontend** — `npm install` succeeded. System Node.js 18 was too old for rolldown (needs `node:u…
- **No external services needed** — All tests mock PG, ES, and Redis; no real credentials required
tokens used
172,766
All systems verified. Here is the final report:
**Summary of what was done:**
- **Backend install** — Created a Python venv, installed all deps from `requirements-dev.txt` (Fast…
- **Backend tests** — `pytest tests/` passed: **1929 passed, 29 skipped** (skips are expected: requ…
- **MCP server install & test** — Installed `fojin-mcp` package; **45/45 tests passed**
- **App launch verification** — The ASGI app creates successfully (43 routes registered, `/api/heal…
- **Frontend** — `npm install` succeeded. System Node.js 18 was too old for rolldown (needs `node:u…
- **No external services needed** — All tests mock PG, ES, and Redis; no real credentials required

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

  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Took 18 minutes to install, slower than the median of the 236 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 237 ai projects Argusic has installed and timed, fojin was the 202nd fastest to reach a running state, and 168 of 237 reached one at all.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.03

Topics (from GitHub)

aibuddhismbuddhist-studieschinese-classicsdigital-humanitiesdockerelasticsearchfastapifull-text-searchknowledge-graphnlpopen-sourcepaliparallel-readingragreactsanskritsemantic-searchtibetan

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/fojin.svg)](https://argusic.com/subject/fojin)

Questions

Does fojin run?
fojin runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 18 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test fojin?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b38d9cc3c87e. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test fojin?
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 fojin take to install?
18 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 fojin need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing fojin?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does fojin compare with the alternatives?
Of the 237 ai projects Argusic has installed and timed, fojin was the 202nd fastest to reach a running state, and 168 of 237 reached one at all.
Where is the evidence for fojin?
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