Infernux runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 28 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test Infernux?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit d0eac0f2d29c. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test Infernux?

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

How long does Infernux take to install?

28 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 Infernux need a GPU?

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

What goes wrong when installing Infernux?

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 Infernux?

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.

Infernux

Building a Neural Network-Native Engine (3N). Python authoring, C++ runtime, Vulkan/WebGPU. Windows, Linux, Android and Web.

Runs with mockssource: GitHub homepagePythonMITcommit d0eac0f2d29c

Python, MIT licensed. The project labels itself: editor, game engine, physics, python, rendergraph and vulkan.

Infernux runs, with stand-ins for the services it depends on. An Argusic agent installed it in 28 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Python 3.13.16 environment with all dependencies installed. Infernux v0.4.0 installed in editable mode. Portable Hub test suite (337 tests) passes, covering project database, Python runtime binding, launch state, project paths, i18n, wheel refresh, and regression guide integrity.
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 56 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 56 / 100
cost of the verifying run: $0.50 (measured)
recorded runs: 2
last tested: 2026-10-07
stars: 1,574
forks: 82
open issues: 3
watchers: 6
size: 101 MB
created: 2025-06-22
last push: 2026-10-04

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

Python 3.13 required, system has Python 3.123 minutes
Native C++ compiled extension (_Infernux.so) could not be built: missing system packages (no root access)
CLI entry point (inx) and 279 native python/test tests unavailable without compiled native module

Install time: 28 minutes
Cold machine to finish: 25 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
How the result was proved: python -m pytest packaging/tests/ -q -ra: 337 passed, 6 skipped (Windows-only tests for Android support, uninstall helper, update partial copy)
Model tokens used: 210,655
Exact commit tested: d0eac0f2d29c
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
Behaviour against real services: this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

        }
    ],
    'test_depth': 'tier2_mock',
    'verified_how': 'python -m pytest packaging/tests/ -q -ra: 337 passed, 6 skipped (Windows-only …
    'final_state': 'Python 3.13.16 environment with all dependencies installed. Infernux v0.4.0 ins…
    'notes': 'The Portable Hub regression lane (documented in TESTING.md) runs without the compiled…
}
print('ARGUSIC_RESULT:' + json.dumps(result))
\"" in /work/repo
 succeeded in 0ms:
tokens used
210,655

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

Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed MIT, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Took 28 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.

Of the 5 editor projects Argusic has installed and timed, Infernux was the 5th fastest to reach a running state, and 4 of 5 reached one at all.

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	2/3	Runs with mocks	92.00	0.50	2026-10-07 05:01 UTC
Argusic Runner	1/3	Did not run	20.00	0.08	2026-10-07 04:31 UTC

Topics (from GitHub)

editor game-engine physics python rendergraph vulkan

Embed the badge

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

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

Questions

Does Infernux run?: Infernux runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 28 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test Infernux?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit d0eac0f2d29c. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Infernux?: The run that produced this verdict cost $0.50: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Infernux take to install?: 28 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 Infernux need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Infernux?: 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.
How does Infernux compare with the alternatives?: Of the 5 editor projects Argusic has installed and timed, Infernux was the 5th fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for Infernux?: 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.