zensical
A modern static site generator by the Material for MkDocs team
Runssource: GitHubhomepageRustMITcommit 27fa3105d2f2
Rust, MIT licensed. The project labels itself: documentation and static site generator.
zensical runs. An Argusic agent installed it in 18 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
zensical is installed and functional: the CLI responds to --help and --version, 'zensical new' creates a bootstrap project, 'zensical build' generates a complete static site in site/ with valid HTML/CSS/JS, 'zensical serve' hosts the site on an HTTP server returning 200, and 1271 of 1307 unit tests pass.
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.
- Unit tests failed with 'zensical.zensical' import error (repo shadowing installed module) and missing bs4/pandas2 minutes
- Rust toolchain not installed1 minute
- Externally-managed Python environment prevents system pip installs1 minute
- UI templates missing (zensical/templates/ was gitignored, empty)1 minute
- Initial build failed because Cargo not on PATH for maturin0.1 minutes
- 31 pandas table-reader tests fail on pandas 3.x API changes
- Install time
- 18 minutes
- Cold machine to finish
- 22 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- zensical --version returned 0.0.65; zensical build on a bootstrap project completed in 0.16s with 'No issues found'; zensical serve --dev-addr=127.0.0.1:9876 started, curl returned HTTP 200 with valid HTML; pytest --import-mode=importlib python/tests/unit/ returned 1271 passed, 31 failed, 5 skipped
- Model tokens used
- 158,148
- Exact commit tested
- 27fa3105d2f2
- 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.
9. **Served the site**: `zensical serve --dev-addr=127.0.0.1:9876` → `curl` returned **HTTP 200** w… 10. **Ran the test suite**: `python -m pytest --import-mode=importlib python/tests/unit/` → **1271 … 11. **Cleaned up** the background server No third-party credentials were required. No mocks were needed — the system was tested with real be… exec /bin/sh -lc "cat <<'EOF' EOF" in /work/repo succeeded in 0ms: Result output complete. tokens used 158,148 Result output complete.
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 18 minutes.
- Recovered from all 6 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.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/zensical)Questions
- Does zensical run?
- Yes. zensical runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test zensical?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 27fa3105d2f2. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test zensical?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does zensical 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 zensical need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing zensical?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for zensical?
- 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.