Show HN: Dropstone – A Recursive Swarm Runtime for Long-Horizon Agent Tasks

I am one of the builders behind Dropstone.

Yesterday, I posted our whitepaper here as a 'discovery' because I was nervous about a cold launch. That was a mistake, and the community rightfully flagged it for lacking transparency. I apologize for the cloak and dagger.

We are reposting this today as an official Show HN to stand behind the tech properly.

The Problem: We built this because we hit the 'Linearity Barrier' with standard agents—after 50+ coding steps, context rot sets in and the agent starts hallucinating.

The Solution: Dropstone uses a Recursive Swarm Topology. Instead of linear prediction, it spawns parallel 'Scout' agents to explore solution paths and uses Entropy Pruning to kill branches that hallucinate.

I'm here to answer any technical questions about our D3 Engine, the latency trade-offs of swarm architecture, or the 'Trajectory Vectors' we use for context management.