Two months from a JobEmber.ai VPS that ran out of memory at 3-5 parallel claude-print agents to a feature-complete agentic runtime. v1.0 ships today. Apache-2.0, one ~50 MB Go binary. The substrate is done: six LLM providers plus a deterministic code-js provider, 19 built-in tools with Claude Code parity, MCP on both sides, A2A on both sides, multi-replica HA on Postgres LISTEN/NOTIFY (no Redis dep), /snapshot/resume even mid-run and across instances (RFC X both phases), per-run credentials never reach the agent's view of its credentials map, a redact plugin in the run-loop that scrubs secrets before the model sees them, scheduled autonomous runs, signed inbound webhooks, content-addressed forkable AgentDefs with lineage. Production-grade validation: 8-hour stability soak (1.27M circuits, 3.8M agent runs, 100% completion across 468 waves, zero leaks) plus a 133-minute autonomous run on local Qwen3.6:27b through ollama-local after the v0.34.3 to v0.37.0 robustness pass. Seven reproducible experiments in the repo (exp1 to exp7). Paca integration confirmed: direct agreement with the Paca maintainer (Apache-2.0 AI-native Scrum / Trello / ClickUp alternative, 954 stars). The Paca maintainer is implementing the integration over gRPC - Paca's agent service calls loomcycle's gRPC surface directly to spawn runs, stream events, and route per-task agent credentials. Post-v1.0 plans: the context-compress plugin (RFC Z Phase 2, LLMLingua-style); SQL Memory (RFC AA, per-scope SQL databases the runtime hosts for sandboxed agents); capability-based memory interface with mem0 as the first MemoryLayer backend (RFC K). Companion projects (4): loomcycle, n8n-nodes-loomcycle, claude-code-plugin-loomcycle, and the Paca integration in flight. v1.0 is the first portable, durable, hardened version of the substrate. Everything from here is composition.
Why 88% of Agent Pilots Die: The Infrastructure Readiness Gap Nobody Talks About