nanoc
A powerful web publishing system
Runssource: GitHubhomepageRubyMITcommit 10191952d081
Ruby, MIT licensed. The project labels itself: nanoc, ruby and static site generator.
nanoc runs. An Argusic agent installed it in 16 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Ruby 3.2.3 extracted from debs, bundle installed 177 gems, nanoc 4.14.8 compiles sites, all test suites pass with 0 failures across 13 packages.
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.
- Ruby not found in container: no ruby, gem, or bundler available5 minutes
- GH-1572 regression test: permission bits lost when copying binary files5 minutes
- psych gem native extension failed: libyaml-dev headers missing2 minutes
- nanoc-cli NO_COLOR test expected true but NO_COLOR=1 was set in container env
- Install time
- 16 minutes
- Cold machine to finish
- 21 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- bundle exec rspec on all 13 packages: 0 failures on ~3310 total tests; bundle exec nanoc create-site + bundle exec nanoc compile produced valid output/index.html, output/robots.txt, output/stylesheet.css
- Model tokens used
- 120,643
- Exact commit tested
- 10191952d081
- 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.
unset NO_COLOR; bundle exec rspec 2>&1 | grep -E "''^[0-9]+ examples|Finished"' in /work/repo succeeded in 67290ms: Finished in 19.77 seconds (files took 1.36 seconds to load) 594 examples, 0 failures, 9 pending Finished in 13.226383s, 22.0015 runs/s, 59.8047 assertions/s. 291 runs, 791 assertions, 0 failures, 0 errors, 11 skips Finished in 27.79 seconds (files took 1.11 seconds to load) 1893 examples, 0 failures All good. Let me now write the final result. tokens used 120,643 All good. Let me now write the final result.
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 16 minutes.
- Recovered from all 4 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.
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/nanoc)Questions
- Does nanoc run?
- Yes. nanoc runs. Argusic installed and launched it on a clean machine in 16 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test nanoc?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 10191952d081. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test nanoc?
- The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does nanoc take to install?
- 16 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 nanoc need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing nanoc?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for nanoc?
- 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.