Strata
Qwen3.8-Flash-Next on any consumer hardware: one-click install for Windows / Linux. Strata inference engine, OpenAI/Anthropic API on localhost, optional image input.
Runs with mockssource: GitHubC++MITcommit 1678de333d0e
C++, MIT licensed.
Strata runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The repo installs Python dependencies, compiles the C++ engine (CPU-only targets) with GCC 13.3 on Ubuntu 24.04, and passes all unit and integration tests: 132 setup tests, 88 server tests (MockEngine), all tool tests, and 11 C++ test binaries.
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 92 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.
- AMD test hardcoded 'strata.exe' which fails on Linux where setup.EXE='strata'
- Golden tests failed: normalize() replaced setup.EXE in log paths changing 'strata-iq3_xxs.log' to '<EXE>-iq3_xxs.log', and Enter-only test hit risk warnings for Unsloth UD-Q4_K_XL on low-RAM PCs
- Install time
- under a minute
- Cold machine to finish
- 27 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- 132 setup tests pass (python -m unittest discover -s tools -p test_setup_*.py: OK), 88 server tests pass (python -m unittest serve.test_server: OK), 22 MCP tests pass, 11 C++ test binaries pass (expert_multi_test and pool_test skipped AVX512, rest pass), all tool test suites pass
- Model tokens used
- 214,283
- Exact commit tested
- 1678de333d0e
- 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.
"install_minutes": 0,
"errors": [],
"test_depth": "tier2_mock",
"notes": "All setup, server, tool, and C++ engine tests pass. No real GPU available; MockEngine w…
"verified_how": "132 setup tests pass, 88 server tests pass, 22 MCP tests pass, 11 C++ test binar…
"final_state": "The repo installs its Python dependencies, compiles the C++ engine (CPU-only targ…
}
exec
/bin/sh -lc "cd /work/repo && echo \"ARGUSIC_RESULT:{\\\"install_succeeded\\\":true,\\\"launch_succ…
succeeded in 0ms:
tokens used
214,283Replay 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
- Installed in 0 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
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.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 5 C++ projects Argusic has installed and timed, Strata was the 1st fastest to reach a running state, and 2 of 5 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.19 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/strata)Questions
- Does Strata run?
- Strata runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test Strata?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1678de333d0e. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Strata?
- The run that produced this verdict cost $0.19: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Strata take to install?
- 0 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 Strata need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Strata?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does Strata compare with the alternatives?
- Of the 5 C++ projects Argusic has installed and timed, Strata was the 1st fastest to reach a running state, and 2 of 5 reached one at all.
- Where is the evidence for Strata?
- 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.