impeccable has not been fully verified yet. No recorded run has produced a verdict yet.

How did Argusic test impeccable?

On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.

Where is the evidence for impeccable?

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.

impeccable

The design language that makes your AI harness better at design.

Not yet verifiedsource: GitHubJavaScriptApache-2.0commit e103efe779e2

JavaScript, Apache-2.0 licensed.

impeccable has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 20 of 100 (the mean of this project's run scores).

At a glance

verdict: Not yet verified
Argusic Score: 20 / 100
recorded runs: 1
last tested: 2026-10-04
stars: 75,455
forks: 0
open issues: 0
watchers: 0
created: -
last push: -

Subject data from GitHub, linked at the top of this page. 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 most recent recorded attempt, which did not reach a verdict. Every line is a recorded value, not an estimate.

Cold machine to finish: 23 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
Exact commit tested: e103efe779e2
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.

Install time: the run did not report one
How the result was proved: runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Model tokens used: not recorded for this run
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
Whether it works at all: this run verified nothing, so this page makes no claim either way

The end of the recording

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

cd /work/repo
export IMPECCABLE_BIN=\"/work/repo/node_modules/@impeccable/cli-linux-x64/bin/impeccable\"
# Directly run the oracle run.mjs to see what happens
node tests/oracle/run.mjs 2>&1 | head -30" in /work/repo
 exited 137 in 171ms:
 exited 137 in 174879ms:
 exited 137 in 99839ms:
v18.19.1
Usage: node [options] [ script.js ] [arguments]
       node inspect [options] [ script.js | host:port ] [arguments]
Options:
  -                           script read from stdin (default if no

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.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Did not run	20.00	0.08	2026-10-04 11:01 UTC

Embed the badge

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

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

Questions

Does impeccable run?: impeccable has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test impeccable?: On a fresh, disposable machine, with every command recorded. One attempt is recorded, and the full method is on the methodology page.
Where is the evidence for impeccable?: 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.