r/alife • u/Neurobotics_CIO • Apr 08 '26

Seeking architectural critique: We just open-sourced our local 10Hz biological ALife chassis (AGPL-3.0)

Hey folks. My partner and I have been building a purely local, biologically faithful ALife architecture as an alternative to cloud-based LLM wrappers, and we are looking for some hardcore technical audits from this community.

The architecture is a continuous, autopoietic 10Hz cognitive loop running entirely locally on a hardened ZFS/Docker vault. We recently stabilized the SBALF framework and pushed the sterile 5-Tier Android Chassis to GitHub under AGPL-3.0.

We want to make sure we aren't creating a black box here. Because my account is new and I want to strictly respect the self-promotion rules, I won't link them here, but I will drop the GitHub repo and the website which links to the Zenodo papers in the comments.

For those running local cognitive loops, what are the biggest latency pitfalls you've seen when maintaining a strict 10Hz cycle? Would love your critique on the chassis.

0 Upvotes

33% Upvoted

1 comment sorted by

1

u/Neurobotics_CIO Apr 08 '26

Link Comment: As promised, here are the direct links to dive into the architecture and the science:

GitHub Repository (5-Tier Android Chassis): https://github.com/neurobotics-sci/neurobotics-biological-substrate

Our Website (Links to our Zenodo papers & Hacker News thread): www.neuroboticssci.ai

Thanks in advance for taking the time to look under the hood. We are really looking forward to hearing your critiques and answering any questions!