Specialized Accounts: loomcycle

### Which type of specialized account are creating? If more than one apply, please select the primary type. Open Source Project ### How do you fit in with the community? loomcycle is an Apache-2.0 open-source agentic runtime — a single Go-binary sidecar that owns the LLM-driven agent loop (memory, channels, MCP tools on both sides, OpenTelemetry, multi-replica HA). It's a developer-facing infrastructure project; the code, docs, and decision history are public at https://github.com/denn-gubsky/loomcycle and https://loomcycle.dev. There's no single company sponsor — it's currently maintained by one engineer (@denn-gubsky on GitHub, denn@loomcycle.dev) with contributors welcome at v1.0. The audience for the account is exactly the Hachyderm mission's "hackers, professionals, enthusiasts ... passionate about life, respect, and digital freedom" — open-source operators, platform engineers, and people who care about running their own agentic systems without ceding the loop to a hyperscaler. We post engineering writeups (https://loomcycle.dev/blog), release notes, and the occasional production-incident postmortem; the tone is "honest residual scope, not marketing puffery." We're happy to abide by the Specialised Accounts Expectations as an Open Source Project account and to abide by Hachyderm's CoC (as specified in the Server Rules). ### How will you ensure the community is protected? All posts are authored by a maintainer (currently @denn-gubsky / Dennis Gubsky) who will have reviewed Hachyderm's CoC before posting. The project's own CONTRIBUTING.md adopts the standard Contributor Covenant as its code of conduct, so the protection norms our contributors agree to are aligned with Hachyderm's expectations. ### (Accounts with Automated Posting/Bot Accounts Only) What method are you using to validate your bots code to ensure that any future updates don't disrupt the community? No automated posting. All toots are written and reviewed by a human maintainer before posting.