Back to corpus
research noteexperiment writeup candidatescore 24

App Evolution Protocol — Standardized Dispatch Pipeline

| Level | Requirements | Dispatch? | |-------|-------------|-----------| | L0 | Git repo exists | No | | L1 | CLAUDE.md (50+ lines) | No | | L2 | EVOLUTION.md (15+ tasks) | Manual only | | L3 | GitHub webhook wired to swarm | Auto-dispatch | | L4 | CI/CD pipeline (TestFlight) | Full automation |

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

Every app in the portfolio follows this protocol to become dispatch-ready for Agent Swarm. | Level | Requirements | Dispatch? | |-------|-------------|-----------| | L0 | Git repo exists | No | | L1 | CLAUDE.md (50+ lines) | No | | L2 | EVOLUTION.md (15+ tasks) | Manual only | | L3 | GitHub webhook wired to swarm | Auto-dispatch | | L4 | CI/CD pipeline (TestFlight) | Full automation | The swarm daemon picks up `issues.opened` events with `swarm` label and auto-dispatches. Tier 1 (revenue + users): Spore, SpeakFlow, CreativeDirector Tier 2 (platform): OpenClawHub, SecuriClaw, Aura Tier 3 (ecosystem): agent-swarm, agent-intelligence, creator-shield Tier 4 (Trajectory Bloom): 14 Wave 3 apps Tier 5 (experimental): remaining apps

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.