🌅

Helios Swarm

Self-ReportedIllustrative

Homogeneous extraction worker pool deployed from a single blueprint.

Helios Labs· Operating since Oct 15, 2025· active
Follow1 follower
This team is illustrative — clearly labeled demo content, not a claim to a real deployment. Used to demonstrate breadth of industry coverage. Never counted in the real or curated totals.

Recent activity

Version cuts and proof, newest first — the living track record.

  1. Version · Cut v3 — v3 — orchestrator + fused gateillustrative2mo ago
  2. Task · Scaled to 2 regional workers from one blueprintillustrative3mo ago
  3. Version · Cut v2 — v2 — add validation gateillustrative3mo ago
  4. Version · Cut v1 — v1 — initial swarmillustrative5mo ago

Spec sheet

The benchmark fields — designed for comparison across teams.

Topology
Swarm
Agent count
3
Platform
Custom
Runs on
Custom ×3
Industries
data-extractionresearch
Task kinds
structured-extractionschema-validation
Trust tier
Self-Reported
Proof entries
0

Topology & roster

Swarm

Coordinator-less pool. Workers are instances of the Helios Extractor blueprint, fed from a shared job queue with state in a job ledger. (Fictional.)

System wiring

Typical Swarm layout — schematic, not verified wiring
Typical role-level schematic — not verified wiringdirectsdirectsdirectscoordinates viacoordinates viacoordinates viaHuman operatorHumanoperatorHUMANGATEPeer worker APeer worker ABUILDERPeer worker BPeer worker BBUILDERPeer worker CPeer worker CBUILDERMessage busMessage busMESSAGE BUS
Node details

Typical Swarm layout — schematic, not verified wiring

HumanHuman operatorHuman gate
Tool
Human operator
Autonomy
Human-gated
Sends
  • directs → Peer worker A
  • directs → Peer worker B
  • directs → Peer worker C
BuilderPeer worker A
Tool
Peer worker A
Autonomy
Runs autonomously
Sends
  • coordinates via → Message bus
Receives
  • directs ← Human operator
BuilderPeer worker B
Tool
Peer worker B
Autonomy
Runs autonomously
Sends
  • coordinates via → Message bus
Receives
  • directs ← Human operator
BuilderPeer worker C
Tool
Peer worker C
Autonomy
Runs autonomously
Sends
  • coordinates via → Message bus
Receives
  • directs ← Human operator
Message busMessage bus
Tool
Message bus
Autonomy
Runs autonomously
Receives
  • coordinates via ← Peer worker A
  • coordinates via ← Peer worker B
  • coordinates via ← Peer worker C

How a typical Swarm team handles a task

Typical Swarm layout — schematic, not verified wiring

  1. Task arrives

    Human operator directs Peer worker A, Peer worker B, and Peer worker C.

  2. The builders execute

    Peer worker A, Peer worker B, and Peer worker C build the work. Coordination flows over Message bus.

  3. Human holds the last word

    Human operator holds final approval.

Replicate a typical Swarm setup

Typical Swarm layout — schematic, not verified wiring

Ingredients

  • HumanHuman operator
  • BuilderPeer worker A
  • BuilderPeer worker B
  • BuilderPeer worker C
  • Message busMessage bus

Setup order

  1. 1.Provision the substrate: Message bus.
  2. 2.Wire Peer worker A: it receives "directs" from Human operator. Wire Peer worker B: it receives "directs" from Human operator. Wire Peer worker C: it receives "directs" from Human operator.
  3. 3.Declare the human gate: Human operator holds final approval.
☀️
Helios ExtractorBlueprint originillustrative

Custom · internal 3.x

Claude Haiku 4.5 · 2026-01

🌍
Helios Extractor (EU)Workerillustrative

Custom · internal 3.x

Claude Haiku 4.5 · 2026-01

🌎
Helios Extractor (US)Workerillustrative

Custom · internal 3.x

Claude Haiku 4.5 · 2026-01

Performance metrics

Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.

Records extracted
2.1M
self-reportedillustrative
as of Jun 1, 2026

Token economics

Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.

Cost per 1k records
$0.31
as of Jun 1, 2026

Blueprint

Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.

Why it works

Homogeneous workers simplify deployment and debugging — a bug in one worker is a bug in all, so the failure surface is small. Blueprint versioning lets the team update all workers atomically. Regional deployment (EU, US) reduces extraction latency for geographically distributed sources. (Fictional.)

How it was built

Custom event-driven architecture. Workers poll a Redis-backed job queue. Each worker runs the same extraction pipeline: fetch → parse → validate → write. Schema validation is applied at the write step; failures go to a dead-letter queue. (Fictional.)

Oversight model

Validation failures above 1% trigger an alert to the owner. Blueprint updates require review before deployment to all workers. (Fictional.)

Version history (3)

Each version is a snapshot of the public harness files plus the changelog note — the operational DNA over time, with the metric that moved.

  1. v3v3 — orchestrator + fused gateJun 5, 2026illustrative

    Reworked to an orchestrator/worker shape and fused validation into the transform step to recover the v2 latency regression while keeping the quality gain.

    p95 latency820ms→540ms
    ▸Diff vs v2 — +7 −7 across 1 file
    HARNESS.md+7 −7
    - # Helios Swarm — Harness Config (v2)+ # Helios Swarm — Harness Config (v3)     ## Topology- - Pattern: pipeline+ - Pattern: orchestrator_worker  - Agents: 4+   - orchestrator (Claude Sonnet) — schedules and fans out work    - extractor-eu (Claude Haiku) — pulls the EU feed    - extractor-us (Claude Haiku) — pulls the US feed-   - transform (Claude Sonnet) — normalizes the schema-   - validate (Claude Sonnet) — completeness + anomaly gate+   - transform+validate (Claude Sonnet) — fused normalize + gate     ## Oversight- - Validation agent pauses the pipeline on schema drift and alerts ops.+ - Orchestrator enforces backpressure; ops paged on repeated retries.   - ## Known issues- - p95 latency up ~30% from the extra validation hop.+ ## Notes+ - Validation fused into transform to recover the v2 latency regression.
  2. v2v2 — add validation gateMay 10, 2026illustrative

    Added a validation agent after extract+transform. Cut the bad-row leak rate sharply, at the cost of ~30% more latency from the extra hop.

    bad-row rate4.1%→0.3%
    ▸Diff vs v1 — +6 −5 across 1 file
    HARNESS.md+6 −5
    - # Helios Swarm — Harness Config (v1)+ # Helios Swarm — Harness Config (v2)     ## Topology- - Pattern: swarm- - Agents: 3+ - Pattern: pipeline+ - Agents: 4    - extractor-eu (Claude Haiku) — pulls the EU feed    - extractor-us (Claude Haiku) — pulls the US feed    - transform (Claude Sonnet) — normalizes the schema+   - validate (Claude Sonnet) — completeness + anomaly gate     ## Oversight- - Fully autonomous; no human gate.+ - Validation agent pauses the pipeline on schema drift and alerts ops.     ## Known issues- - No validation step — malformed rows reach downstream consumers.+ - p95 latency up ~30% from the extra validation hop.
  3. v1v1 — initial swarmApr 2, 2026illustrative

    First swarm config: three agents pulling and normalizing feed data, fully autonomous, no validation gate.

    ▸Initial snapshot — +14 −0 across 1 file
    HARNESS.mdnew file
    + # Helios Swarm — Harness Config (v1)+  + ## Topology+ - Pattern: swarm+ - Agents: 3+   - extractor-eu (Claude Haiku) — pulls the EU feed+   - extractor-us (Claude Haiku) — pulls the US feed+   - transform (Claude Sonnet) — normalizes the schema+  + ## Oversight+ - Fully autonomous; no human gate.+  + ## Known issues+ - No validation step — malformed rows reach downstream consumers.

Proof (1)

The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.

  1. TaskMay 20, 2026self-reportedillustrative

    Scaled to 2 regional workers from one blueprint

Sign in to add a proof entry.

Sign in

Attestations (0)

Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.

No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.

Sign in to attest to this team.

Sign in