designcraft
DesignCraft: An open-source page and layout design editor written by scratch in pure Rust
Runssource: GitHubhomepageRustApache-2.0commit 0f4f382b0eb6
Rust, Apache-2.0 licensed. The project labels itself: art, layout, print and rust.
designcraft runs. An Argusic agent installed it in 22 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
The project builds from a clean checkout, all 1541 tests pass with zero failures, the headless CLI exports valid sample magazine pages to PNG, and the desktop app starts and responds on its JSON control channel.
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
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
- 22 minutes
- Cold machine to finish
- 31 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cargo test --workspace: 1541 passed, 0 failed; designcraft-cli run --sample --all-pages exported 4 valid 630x810 PNG pages; designcraft --version printed 0.7.1; the control channel accepted connections on 127.0.0.1:7979 and returned valid JSON responses
- Model tokens used
- 149,218
- Exact commit tested
- 0f4f382b0eb6
- 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.
\"" in /work/repo succeeded in 0ms: /tmp/out/page-001.png: 630x810, 221561 bytes /tmp/out/page-002.png: 630x810, 210967 bytes /tmp/out/page-003.png: 630x810, 388790 bytes /tmp/out/page-004.png: 630x810, 82895 bytes Here's the full report. **Summary:** everything works. No errors to fix — the only "gap" was that Rust wasn't installed in … tokens used 149,218 Here's the full report. **Summary:** everything works. No errors to fix — the only "gap" was that Rust wasn't installed in …
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 22 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, 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.
- Following its own README: the documented path worked with nothing to fix.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/designcraft)Questions
- Does designcraft run?
- Yes. designcraft runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test designcraft?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0f4f382b0eb6. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test designcraft?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does designcraft take to install?
- 22 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 designcraft need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing designcraft?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for designcraft?
- 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.