PaperSpine
PaperSpine5, local-first, evidence-bound paper research, writing, figures, review and delivery. Download: https://wubing2023.github.io/PaperSpine/v5/
Runssource: GitHubPythonMITcommit f7e3dabaf499
Python, MIT licensed.
PaperSpine runs. An Argusic agent installed it in 1 minute and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 317 tests pass on Python 3.12 with all runtime dependencies installed in a .venv; ruff lint clean; web core absent but expected for source-tree-only workflow.
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. 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.
- PEP 668 blocks system-level pip install1 minute
- TEST_TEMP_ROOT targets /work/90_临时工作/ which cannot be created without root1 minute
- lxml module missing for word_guard font-repair tests0.5 minutes
- test_workspace context manager is collected as a pytest test function0.2 minutes
- .venv directory pollutes scan for private paths in source files0.2 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pytest tests -q returned 317 passed, 1 skipped, 187 subtests passed in 17.7s
- Model tokens used
- 97,691
- Exact commit tested
- f7e3dabaf499
- 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.
|---|---|
| PEP 668 blocked system-level pip | Used `python3 -m venv .venv` to install inside the container |
| `test_suite_hardening.py` tried to create `/work/90_临时工作/` (no root) | Changed `TEST_TEMP_ROOT` t…
| `test_workspace` context manager collected as a pytest test function | Renamed from `test_workspa…
| `.venv/` files polluted `test_no_obvious_local_private_paths_in_reusable_files` scan | Added `".v…
| `lxml` missing for `word_guard.py` font-repair tests | Installed `lxml` via pip |
### Verification
- **Test suite**: `pytest tests -q` returned **317 passed, 1 skipped, 187 subtests passed** in 17.7s
- **Lint**: `ruff check src/scripts tests` — all checks passed
- **Web UI**: `src/scripts/paperspine5_web.py status` returns `{"status":"FAIL","error":"The standa…
The web workspace requires a download that's unavailable in this offline container, but the test su…
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 1, "er…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 1 minute, faster than the median of the 22 comparable projects Argusic has measured.
- Recovered from all 5 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 23 Python projects Argusic has installed and timed, PaperSpine was the 3rd fastest to reach a running state, and 12 of 23 reached one at all.
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 1 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/paperspine)Questions
- Does PaperSpine run?
- Yes. PaperSpine runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test PaperSpine?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f7e3dabaf499. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test PaperSpine?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does PaperSpine take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does PaperSpine need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing PaperSpine?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does PaperSpine compare with the alternatives?
- Of the 23 Python projects Argusic has installed and timed, PaperSpine was the 3rd fastest to reach a running state, and 12 of 23 reached one at all.
- Where is the evidence for PaperSpine?
- 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.