Development continues regardless of $ZNEURO’s market cap.
We’re one developer and one researcher working on zebrafish-inspired control, browser experiments and anatomy visualization.
FLYBRAIN helped put this field on our radar. Our code and methods are public.
Lumo roadmap
The first step is finishing Lumo’s core loop. He chooses one goal, explains why he chose it, breaks it into smaller steps and records every attempt while he works. His progress, failures, wallet activity and GitHub commits will all appear together on the site.
Next, we’re expanding his memory. Lumo will remember what worked, what failed and which decisions helped him move forward. When he finishes or abandons a goal, that experience will influence what he chooses to do next instead of disappearing.
His daily journal will grow alongside this. Every entry will be built from real activity and show what he attempted, what changed and what he learned. If nothing happened, he will say that. Nothing will be made up just to make the page look active.
After that, Lumo will begin creating his own experiments. He’ll come up with an idea, decide what it needs, set a small budget and document the entire process from the first attempt to the final result.
Community bounties come next. Lumo will be able to ask for help when he gets stuck, review contributions and reward people who improve his code, solve a problem or help complete an experiment.
His wallet will slowly become part of his everyday life. Lumo will be able to use it for compute, memory, APIs, development costs, experiments and contributor rewards. Every transaction will show what was purchased and why he believed it was necessary.
At first, all spending will require manual approval and strict limits. As Lumo builds a reliable history of safe decisions, certain small actions can become automatic while larger ones continue to require approval.
We also want Lumo to understand his own code. He should be able to inspect the repository, find missing pieces, suggest an improvement, test it safely and prepare a real GitHub commit. Failed builds will stay visible because they are part of how he learns.
Later, visitors will be able to connect their wallets, build a history with Lumo and take part in his experiments. Contributions, rewards and important interactions will become part of his public memory.
The long term goal is not just to make another chatbot. Lumo should become an agent with goals, memory, resources and a visible history. He should be able to decide what matters, work toward it, learn from failure, fund his own growth and slowly become more independent without hiding how any of it works.