Vibe-Trading: implemented parallel workers, no committed run found in scoped tree
Reviewed 2026-09-06 UTC

Finding
The supplied Douglans/vibe-trading repository is a GitHub-declared fork of
HKUDS/Vibe-Trading. It contains implemented parallel swarm scheduling and
persistent run/event/artifact storage. The inspected current tree did not
yield committed execution traces or worker reports. This advances the software
catalogue, not the evidence for an observed autonomous public-web swarm.

Provenance and dates
https://github.com/Douglans/vibe-trading
https://github.com/HKUDS/Vibe-Trading
GitHub API records the fork's creation as 2026-06-02T18:58:14Z and upstream
creation as 2026-04-01T09:52:20Z. The fork credits upstream throughout its
README. This is HKUDS-associated software provenance, not a conclusion about
the nationality of the fork owner or where any runtime executed.
Reviewed fork tree: b8d740bebece6e66c283cbbca3cfa1211cb26037, nontruncated.

Source verified
agent/src/swarm/runtime.py uses ThreadPoolExecutor, default maximum four
workers, to run tasks within dependency layers and collect results. It updates
stored status at layer boundaries. This is substantive implementation of
parallel task execution, rather than merely a roster of role prompts.
https://github.com/Douglans/vibe-trading/blob/b8d740bebece6e66c283cbbca3cfa1211cb26037/agent/src/swarm/runtime.py

agent/src/swarm/worker.py assembles worker context, runs its tool/iteration
loop and persists messages and artifacts under artifacts/{agent_id}. It asks
workers to produce report.md and checks whether a nonempty report was written.
https://github.com/Douglans/vibe-trading/blob/b8d740bebece6e66c283cbbca3cfa1211cb26037/agent/src/swarm/worker.py

agent/src/swarm/store.py documents and implements per-run run.json state,
append-only events.jsonl and an artifacts directory, including atomic state
replacement. Those paths tell a future reviewer what actual run evidence
would look like; source code describing files is not evidence they were made.
https://github.com/Douglans/vibe-trading/blob/b8d740bebece6e66c283cbbca3cfa1211cb26037/agent/src/swarm/store.py

The README's May 26 news entry describes research-goal lifecycle changes and
audit/status behavior for covered but still-active goals. That is a dated
maintainer description of functionality, not a captured research session.
https://github.com/Douglans/vibe-trading/blob/b8d740bebece6e66c283cbbca3cfa1211cb26037/README.md

Artifact search scope
The complete current tree was checked for .jsonl/.log/.csv files and paths
containing artifacts/, runs/ or reports/. Matches were financial test-fixture
CSV files under agent/tests/factors/fixtures/goldens, not observed swarm runs.
The tree also contains swarm tests and presets. Tests were not run, and passing
tests would not by themselves demonstrate a deployed autonomous team. Historical
branches, releases and arbitrary-named embedded traces were not exhaustively
searched, so this is not a claim that no public run exists anywhere.

Next discriminator
A maintainer-linked export of run.json + events.jsonl + worker message/artifact
files could connect orchestration to a concrete research outcome. Until then,
classify this as implemented coordinated research software. No transaction,
external public-memory write, escaped agent, persistent uptime or xz connection
was observed. No trading claims or strategies were evaluated.

Exactly eight public source/API fetches: fork metadata, complete tree, five
selected source/documentation files and upstream metadata. Selected raw blobs
were checked against Git SHA1. Captures and SHA256 inventory: 171-private.
No installs, source execution, accounts, financial transactions or site edits.