arc.codes

The Architect web site! 🌩

Runssource: GitHubhomepageJavaScriptApache-2.0commit 0adb642eaebd

JavaScript, Apache-2.0 licensed. The project labels itself: api gateway, arc, aws, docs, dynamodb, lambda and sns.

arc.codes runs. An Argusic agent installed it in 0.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

npm dependencies install, all 11 tests pass, and the Architect sandbox serves the doc site with 200 responses on the homepage, LLM texts, docs, and API package routes.

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.01 (measured)
recorded runs
1
last tested
stars
315
forks
110
open issues
11
watchers
9
size
19 MB
created
last push

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
under a minute
Cold machine to finish
4 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
npm install exited 0; node --test --test-concurrency=1 passed 11/11; sandbox served 200 on GET /, GET /llms.txt, GET /llms-full.txt, GET /docs/en/get-started/quickstart, GET /api/package
Model tokens used
102,291
Exact commit tested
0adb642eaebd
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.

I have all the data I need. Let me compile the final report.
## Summary
**Install**: npm install succeeded with Node 22 and npm 10 (system had Node 18 which didn't meet th…
**Tests**: All 11 unit tests pass — 11 passed, 0 failed in ~6.8s. The link checker validates all in…
**Server launch**: The Architect sandbox starts and serves:
- `GET /` → 200, 532KB HTML homepage with rendered content
- `GET /llms.txt` → 200, text/plain, 5KB
- `GET /llms-full.txt` → 200, ~515KB
- `GET /docs/en/get-started/quickstart` → 200, 40KB rendered HTML
- `GET /api/package?arc=...` → 200, valid CloudFormation JSON
- `GET /docs/en/getting-started` → 404 (no markdown file at that exact path — expected, the docs co…
**Errors**: Node version mismatch (system v18, needed >=22) — worked around via `npx -p node@22`. N…

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 0.1 minutes, faster than the median of the 31 comparable projects Argusic has measured.
  • 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.

Of the 32 api-gateway projects Argusic has installed and timed, arc.codes was the 6th fastest to reach a running state, and 22 of 32 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 0.1 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.01

Topics (from GitHub)

api-gatewayarcawsdocsdynamodblambdasns

Embed the badge

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

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

Questions

Does arc.codes run?
Yes. arc.codes runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test arc.codes?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0adb642eaebd. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test arc.codes?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does arc.codes take to install?
0.1 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 arc.codes need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing arc.codes?
Nothing did, in the recorded run: zero errors between clone and running.
How does arc.codes compare with the alternatives?
Of the 32 api-gateway projects Argusic has installed and timed, arc.codes was the 6th fastest to reach a running state, and 22 of 32 reached one at all.
Where is the evidence for arc.codes?
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.

Discussion