Yes. cadence runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 errors on the way, and recorded the session.

How did Argusic test cadence?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 33704b3a5fc2. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test cadence?

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

How long does cadence take to install?

4.5 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 cadence need a GPU?

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

What goes wrong when installing cadence?

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.

Where is the evidence for cadence?

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.

cadence

Cadence is a distributed, scalable, durable, and highly available orchestration engine to execute asynchronous long-running business logic in a scalable and resilient way.

Runssource: GitHub homepageGoApache-2.0commit 33704b3a5fc2

Go, Apache-2.0 licensed. The project labels itself: cadence, distributed systems, golang, java, orchestration engine, service bus, service fabric and services platform.

cadence runs. An Argusic agent installed it in 4.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Cadence server compiled all 8 binaries, installed SQLite persistence schemas, started all 4 services (frontend, matching, history, worker) into RUNNING state, and passed all unit tests across the codebase.
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

verdict: Runs
Argusic Score: 100 / 100
cost of the verifying run: $0.10 (measured)
recorded runs: 1
last tested: 2026-09-27
stars: 9,456
forks: 918
open issues: 193
watchers: 1,418
size: 91 MB
created: 2017-02-21
last push: 2026-09-25

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-27. 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 cadence, 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.

Go 1.25.14 not pre-installed — downloaded and installed from golang.org2.5 minutes
unzip not installed — downloaded .deb and extracted manually1 minute

Install time: 5 minutes
Cold machine to finish: 23 minutes
Errors hit and fixed: 2 hit, 2 fixed with no human help
How the result was proved: make build (compile-check all packages + tests) exited 0; make bins (all 8 binaries) exited 0; go test -count=1 on persistence/*, common/... frontend/... matching/... history/... worker/... all passed (0 failures across 100+ packages); cadence-server --zone sqlite start printed [Fx] RUNNING for all 4 services (frontend:7933, matching:7935, history:7934, worker:7939)
Model tokens used: 451,720
Exact commit tested: 33704b3a5fc2
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.

ok    github.com/uber/cadence/service/worker/scanner/shardscanner  0.274s
ok    github.com/uber/cadence/service/worker/scanner/tasklist  0.710s
ok    github.com/uber/cadence/service/worker/scanner/timers  0.021s
ok    github.com/uber/cadence/service/worker/scheduler  0.104s
?     github.com/uber/cadence/service/worker/worker  [no test files]
?     github.com/uber/cadence/service/worker/workercommon  [no test files]
Excellent — all tests pass across the board. Let me compile the final results.
**Summary: all builds succeed, the server starts, and the full suite of unit tests passes for every…
tokens used
451,720
Excellent — all tests pass across the board. Let me compile the final results.
**Summary: all builds succeed, the server starts, and the full suite of unit tests passes for every…

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 4.5 minutes.
Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
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.
A quick evaluation: it was running 4.5 minutes after the clone.

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	1/3	Runs	100.00	0.10	2026-09-27 19:38 UTC

Topics (from GitHub)

cadence distributed-systems golang java orchestration-engine service-bus service-fabric services-platform uber workflow-automation workflows

Embed the badge

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

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

Questions

Does cadence run?: Yes. cadence runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test cadence?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 33704b3a5fc2. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test cadence?: The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does cadence take to install?: 4.5 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 cadence need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing cadence?: 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.
Where is the evidence for cadence?: 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.