fable51-worlds

worlds via code, from fable 5.1

Runssource: GitHubJavaScriptMITcommit d24028466530

JavaScript, MIT licensed. The project labels itself: 3d reconstruction, ai agents, claude, digital twin, openstreetmap, procedural generation, san francisco and threejs.

fable51-worlds runs. An Argusic agent installed it in 15 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Three Three.js worlds (Kyoto Higashiyama, Death Star Trench Run, Union Square SF) install from npm, build with vite, serve via vite dev server at HTTP 200, and render interactive 3D scenes in Playwright headless Chromium

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.35 (measured)
recorded runs
1
last tested
stars
532
forks
33
open issues
3
watchers
0
size
417 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 fable51-worlds, 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.

  • death-star-trench-run package.json missing all runtime dependencies5 minutes
  • union-square-sf vite 8 requires Node >=20 but container has Node 183 minutes
  • Playwright 1.62 requires Node >=20, incompatible with Node 182 minutes
Install time
15 minutes
Cold machine to finish
64 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
Playwright headless Chromium verified each world loads, renders canvas, and exposes correct build metadata; vite dev server returns HTTP 200 for all worlds
Model tokens used
1,402,271
Exact commit tested
d24028466530
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.

      "msg": "Playwright 1.62 requires Node >=20, incompatible with Node 18",
      "fix": "installed [email protected] which supports Node 18",
      "minutes": 2
    }
  ],
  "test_depth": "tier1_real",
  "notes": "All three worlds (Kyoto, Death Star Trench Run, Union Square SF) install, build, and re…
  "verified_how": "Playwright headless Chromium verified each world loads, renders canvas, and expo…
  "final_state": "Three Three.js worlds (Kyoto Higashiyama, Death Star Trench Run, Union Square SF)…
}
tokens used
1,402,271

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 15 minutes.
  • Recovered from all 3 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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.35

Topics (from GitHub)

3d-reconstructionai-agentsclaudedigital-twinopenstreetmapprocedural-generationsan-franciscothreejsurban-simulationwebgl

Embed the badge

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

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

Questions

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