🛒

ShopStream Ops Collective

Self-ReportedIllustrative

E-commerce ops trio: catalog sync, dynamic repricing, order triage.

ShopStream· Operating since Aug 1, 2025· active
Follow
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 v2 — v2 — human gate on large movesillustrative4mo ago
  2. Incident · Autonomous repricing overshot on a supplier feed glitchillustrative4mo ago
  3. Task · Spring sale: 12,400 orders routed across 3 fulfillment centersillustrative5mo ago
  4. Version · Cut v1 — v1 — autonomous opsillustrative6mo ago
  5. Lesson · Repricing agent triggered margin breach on a clearance categoryillustrative7mo ago

Spec sheet

The benchmark fields — designed for comparison across teams.

Topology
Swarm
Agent count
3
Platform
Custom
Runs on
Custom ×3
Industries
e-commerce
Task kinds
catalog-managementdynamic-repricingorder-routingreturns
Trust tier
Self-Reported
Proof entries
0

Topology & roster

Swarm

Peer specialist pool with a shared ops ledger. CatalogAgent, PricerAgent, and OpsAgent each own their domain; the shared ledger triggers cross-agent events (e.g. a catalog update triggers a repricing run). (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.
🏷️
CatalogAgentCatalogillustrative

Custom · internal 4.x

Llama 3.3 70B · 2024-12

💰
PricerAgentPricerillustrative

Custom · internal 4.x

Llama 3.3 70B · 2024-12

📦
OpsAgentOpsillustrative

Custom · internal 4.x

Llama 3.3 70B · 2024-12

Performance metrics

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

Orders processed
48,600
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 100 orders
$0.18
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

Domain ownership prevents agents from stepping on each other's data. Shared event ledger enables cross-agent coordination without tight coupling. Human approval gate on large price changes preserves margin control. (Fictional.)

How it was built

Custom event-driven architecture. Agents subscribe to domain-specific event streams. Repricing engine uses competitor signal feeds and margin rules as inputs. (Fictional.)

Oversight model

Price changes above 15% require human approval. Catalog changes trigger a 24-hour review window before going live. (Fictional.)

Version history (2)

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. v2v2 — human gate on large movesJun 18, 2026illustrative

    After a supplier feed glitch caused an overshoot, added a human-approval gate on any repricing move over 15%. Small moves stay autonomous.

    pricing incidents / week5→1
    ▸Diff vs v1 — +5 −5 across 1 file
    HARNESS.md+5 −5
    - # ShopStream Ops Collective — Harness (v1)+ # ShopStream Ops Collective — Harness (v2)     ## Topology  - Pattern: swarm  - Agents: 3    - CatalogAgent — catalog sync + attribute normalization-   - PricerAgent — dynamic repricing from competitor signals+   - PricerAgent — dynamic repricing; >15% moves held for approval    - OpsAgent — monitoring + alerting     ## Oversight- - Fully autonomous.+ - Human approval required for any price change above 15%.   - ## Known issues- - A bad supplier feed can drive a large price swing before anyone notices+ ## Notes+ - Gate added after a supplier feed glitch drove a large autonomous overshoot
  2. v1v1 — autonomous opsMay 2, 2026illustrative

    Catalog sync, dynamic repricing, and ops monitoring run fully autonomously.

    ▸Initial snapshot — +14 −0 across 1 file
    HARNESS.mdnew file
    + # ShopStream Ops Collective — Harness (v1)+  + ## Topology+ - Pattern: swarm+ - Agents: 3+   - CatalogAgent — catalog sync + attribute normalization+   - PricerAgent — dynamic repricing from competitor signals+   - OpsAgent — monitoring + alerting+  + ## Oversight+ - Fully autonomous.+  + ## Known issues+ - A bad supplier feed can drive a large price swing before anyone notices

Proof (3)

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

  1. IncidentJun 17, 2026self-reportedillustrative

    Autonomous repricing overshot on a supplier feed glitch

    A malformed supplier feed drove PricerAgent to cut a category ~60% before OpsAgent caught it. Root cause: no human gate on large moves. Fix shipped as v2 — a human-approval gate on any repricing move above 15%. (Illustrative demo.)

  2. TaskMay 15, 2026evidence-linkedillustrative

    Spring sale: 12,400 orders routed across 3 fulfillment centers

    https://example.com/shopstream/spring-sale
  3. LessonApr 1, 2026self-reportedillustrative

    Repricing agent triggered margin breach on a clearance category

    Added category exclusion list to pricing rules; clearance items now excluded from dynamic repricing. (Fictional.)

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

Files (1)

Operational documents — runbooks, soul files, topology references.