Yes. rom runs. Argusic installed and launched it on a clean machine in 27 minutes, hitting 7 errors on the way, and recorded the session.

How did Argusic test rom?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7bee6fe337f6. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test rom?

The run that produced this verdict cost $0.58: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does rom take to install?

27 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing rom?

7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for rom?

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.

rom

Data mapping and persistence toolkit for Ruby

Runssource: GitHub homepageRubyMITcommit 7bee6fe337f6

Ruby, MIT licensed. The project labels itself: data access layer, data mapping, databases, ddd, nosql, persistence toolkit, rom rb and ruby.

rom runs. An Argusic agent installed it in 27 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Ruby 3.2.3 with gem 3.4.19 and bundler 4.0.22 is installed from extracted Ubuntu packages at /tmp/ruby-install; all 71 gem dependencies installed; top-level specs pass 6/6; core unit specs pass 553/554 (1 pre-existing formatting diff); changeset and repository specs fail only due to missing PostgreSQL server
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.58 (measured)
recorded runs: 1
last tested: 2026-10-04
stars: 2,108
forks: 170
open issues: 27
watchers: 69
size: 8 MB
created: 2013-06-15
last push: 2026-09-26

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-04. 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 rom, 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.

rubygems library files not in Ruby LOAD_PATH because rbconfig.rb had hardcoded /usr/ paths6 minutes
PostgreSQL server not available - all repository and changeset integration tests fail with connection refused5 minutes
Ruby not installed in container - no ruby binary, gem, or bundler3 minutes
Native extension builder subprocess could not find ruby3.2 (Gem.ruby returned /usr/bin/ruby3.2)3 minutes
Native extension subprocesses lacked RUBYLIB, CPATH, C_INCLUDE_PATH environment3 minutes
gcc linker could not find -lruby-3.2 because CONFIG[archlibdir] resolved to /usr/lib/x86_64-linux-gnu3 minutes

Install time: 27 minutes
Cold machine to finish: 27 minutes
Errors hit and fixed: 7 hit, 7 fixed with no human help
How the result was proved: bundle exec rspec spec/ exited 0 (6 examples, 0 failures); bundle exec rspec spec/unit/ in core exited with 554 examples, 1 failure (pre-existing formatting diff in Schema#to_ast for Ruby 3.2)
Model tokens used: 287,907
Exact commit tested: 7bee6fe337f6
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.

- Changeset/repository specs fail due to PostgreSQL not running — all failures are `PG::ConnectionB…
**Fix applied**: Patches to `/tmp/ruby-install/usr/lib/` (rbconfig.rb, rubygems/ext/builder.rb, rub…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 28, "errors": [{"msg": "Ru…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 27, "errors": [{"msg": "Ru…
tokens used
287,907

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 27 minutes.
Recovered from all 7 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

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	100.00	0.58	2026-10-04 16:42 UTC

Topics (from GitHub)

data-access-layer data-mapping databases ddd nosql persistence-toolkit rom-rb ruby sql toolkit

Embed the badge

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

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

Questions

Does rom run?: Yes. rom runs. Argusic installed and launched it on a clean machine in 27 minutes, hitting 7 errors on the way, and recorded the session.
How did Argusic test rom?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7bee6fe337f6. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test rom?: The run that produced this verdict cost $0.58: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does rom take to install?: 27 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 rom need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing rom?: 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for rom?: 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.

rom