edict
🏛️ 三省六部制 · OpenClaw Multi-Agent Orchestration System, 9 specialized AI agents with real-time dashboard, model config, and full audit trails
Runssource: GitHubhomepagePythonMITcommit 14a207557719
Python, MIT licensed. The project labels itself: ai agents, ai orchestration, autonomous agents, claude, dashboard, kanban, llm and multi agent.
edict runs. An Argusic agent installed it in 8 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 68 tests pass on Python 3.12.3; the dashboard HTTP server serves the React frontend, health check, and all API endpoints correctly.
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 60 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.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- test_sync_symlinks fixture didn't patch OPENCLAW_HOME which is evaluated at import time2 minutes
- test_done/test_done_not_overwritable used invalid state transitions (Zhongshu -> Done via cmd_done)2 minutes
- Broken symlinks for agentrec_advisor.py and linucb_router.py pointing to developer's local machine1 minute
- Install time
- 8 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest tests/ exited 0, 68 passed; HTTP requests to dashboard server returned 200 on /healthz, /, /api/live-status, /api/agent-config, /api/model-change-log, and static JS/CSS assets
- Model tokens used
- 255,554
- Exact commit tested
- 14a207557719
- 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.
3. **`test_done` / `test_done_not_overwritable`** — created tasks in `Zhongshu` state and called `c…
**Verification:**
- All 68 tests pass: `python3 -m pytest tests/ -v` → 68 passed
- Dashboard server starts and serves all endpoints:
- `GET /healthz` → HTTP 200 (`{"status": "ok"}`)
- `GET /` → HTTP 200 (481b, React dashboard HTML)
- `GET /api/live-status` → HTTP 200
- `GET /api/agent-config` → HTTP 200
- `GET /api/model-change-log` → HTTP 200
- Static assets (JS/CSS) → HTTP 200
```json
```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.
- Recovered from all 3 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 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 8 minutes to install, slower than the median of the 20 comparable projects Argusic has measured.
Of the 21 ai-agents projects Argusic has installed and timed, edict was the 13th fastest to reach a running state, and 13 of 21 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 8 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 | 2/3 | Runs | 100.00 | 0.04 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.04 |
Topics (from GitHub)
ai-agentsai-orchestrationautonomous-agentsclaudedashboardkanbanllmmulti-agentopenaiopenclaworchestrationpythonworkflow-automation
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/edict)Questions
- Does edict run?
- Yes. edict runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test edict?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 14a207557719. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test edict?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does edict take to install?
- 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 edict need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing edict?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does edict compare with the alternatives?
- Of the 21 ai-agents projects Argusic has installed and timed, edict was the 13th fastest to reach a running state, and 13 of 21 reached one at all.
- Where is the evidence for edict?
- 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.