Back to corpus
research noteexperiment writeup candidatescore 32

Pulse Chain System — Living Documentation

A Pulse Chain is a **self-orchestrating multi-agent pipeline** that uses Discord as its execution spine. Work decomposes into **waves** (phases), each wave runs **parallel agents**, and completion of one wave auto-triggers the next.

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

> Last updated: 2026-02-16 18:25 EST > Status: Active sprint, Wave 8 in progress | Evo³ running on orchestration layer A Pulse Chain is a **self-orchestrating multi-agent pipeline** that uses Discord as its execution spine. Work decomposes into **waves** (phases), each wave runs **parallel agents**, and completion of one wave auto-triggers the next. **Constraint:** Discord allows Category → Channel → Message → Thread. No sub-sub-threads. Deep dives branch into sub-pulses (new threads on new messages within the same channel). > **Rule: NEVER dispatch a bare `claude -p` prompt. EVER.** > Learned 2026-02-16: Bypassing enrichment to "save time" produces inferior output and wastes more time re-doing poor work. | Script | Path | Version | What It Does | |--------|------|---------|-------------| | `chain-engine.py` | `[home-path]` | v1 (Evo³) | Declarative chain evaluator + state machine + dispatcher | | `wave-watcher.sh` | `[home-path]` | v4 (Evo³) | Cron orchestrator — delegates to chain-engine | | `enriched-dual-dispatch.sh` | `[home-path]` | v2 (Evo³) | Single task → enriched → routes to least-busy Max account | | `parallel-dispatch.sh` | `[home-path]` | v2 (Evo³) | Two tasks → both enriched → account1 + account2 simultaneously | | `enriched_spawn.py` | `[home-path]` | v1 | Prompt builder — injects AGENTS.md, SOUL.md, CLAUDE.md, DEP, skills | | `pulse-health-reporter.sh` | `Desktop/pulse-v1/` | v2 (Evo³) | Health check with chain-engine integration | | `pulse-health-reporter.sh` | `[home-path]` | Health check — agent status, stale detection, capacity |

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.