SemIf-OpenJev
Semantic ifs from open models, on a 3090 at home. Independent; not affiliated with Jev or TypeSafe.
Runssource: GitHubPythonMITcommit 23cf1f39fc95
Python, MIT licensed.
SemIf-OpenJev runs. An Argusic agent installed it in 2.8 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The `semif-phase1` package installs from the standard `pip install -e '.[test]'` command, `semif-score --help` prints usage, the offline test suite passes (67 passed, 3 skipped), all 23 raw-result checksums verify OK, and `verify_published.py` reports 69 verified summary claims.
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 96 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.
- Install time
- 3 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- tier1_real double check: pytest -q (67 passed, 3 skipped) and sha256sum -c results/raw/SHA256SUMS (23 files, all OK) and benchmarks/verify_published.py (status ok, 69 claims). Actual 4B model scoring not possible without CUDA/GPU or GGUF weights in this container.
- Model tokens used
- 113,581
- Exact commit tested
- 23cf1f39fc95
- 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.
113,581 Everything is verified. Here is the report: **What I did** - Followed the README's standard procedure exactly: created a Python 3.12.3 venv and ran `pip insta… - Confirmed the CLI exists and executes: `.venv/bin/semif-score --help` printed the full usage. - Ran the full test suite: **67 passed, 3 skipped in 1.88s**. The 3 skips are environment-gated, no… - Ran both repo-recommended validations: `sha256sum -c results/raw/SHA256SUMS` → all 23 files `OK`;… - Decoded the bundled demo media as a real-content check: `ffmpeg -v error -i demo/assets/semif-pha… **Errors encountered** - None. The install, tests, checksum, and published-claims verification all succeeded on the first … **Not checked** - Could not launch scoring against a real model (no CUDA GPU, no GGUF weights, and the repo command…
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.
- Nothing broke on the way: zero errors between clone and running.
- 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 did not, or is not known
- Took 2.8 minutes to install, slower than the median of the 46 comparable projects Argusic has measured.
Of the 47 Python projects Argusic has installed and timed, SemIf-OpenJev was the 28th fastest to reach a running state, and 32 of 47 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2.8 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.03 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.03 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/semif-openjev)Questions
- Does SemIf-OpenJev run?
- Yes. SemIf-OpenJev runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test SemIf-OpenJev?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 23cf1f39fc95. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test SemIf-OpenJev?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does SemIf-OpenJev take to install?
- 2.8 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 SemIf-OpenJev need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing SemIf-OpenJev?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does SemIf-OpenJev compare with the alternatives?
- Of the 47 Python projects Argusic has installed and timed, SemIf-OpenJev was the 28th fastest to reach a running state, and 32 of 47 reached one at all.
- Where is the evidence for SemIf-OpenJev?
- 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.