Building a Sovereign AI Colony From a Smartphone: Cristhiam Hernández’s Developer Journey
Real developers. Real journeys. Real ideas.
What if a smartphone could become the starting point for an entire distributed AI ecosystem? For Cristhiam Leonardo Hernández Quiñonez (CLHQ), that question became the foundation of HormigasAIS — an ambitious project exploring sovereign edge computing, distributed AI agents, lightweight communication protocols, and a different way of integrating humans into autonomous systems.
His journey began in graphic design and digital marketing, moved through experiments with servers and automation, and eventually led to developing an ecosystem using a Samsung A16 smartphone and Termux.
Interview & Story by Mehadi Hasan
CoderLegion Community & Editorial Team
From Digital Marketing to Distributed Systems
Cristhiam's journey into technology did not begin with a conventional software engineering career.
His early work was in graphic design and digital marketing, particularly brand development and positioning. He used tools such as GitHub, n8n, Slack, Discord, and automation workflows to coordinate teams, measure performance, and make projects more efficient.
But as he worked with these systems, he noticed a recurring problem: too much dependence on third-party platforms and centralised infrastructure.
The more he explored these architectures, the more interested he became in building infrastructure of his own.
In 2023, he began studying distributed systems and communication between autonomous agents.
Research into biological swarms, particularly the coordination of ant colonies and birds without central leadership, captured his imagination.
He became fascinated by the possibility that software agents could coordinate through lightweight communication and collective agreement rather than depending entirely on a central controller.
He began building experimental environments, connecting servers, and testing communication methods.
Those early experiments eventually became the foundation of HormigasAIS.
The Idea Behind HormigasAIS
The name HormigasAIS combines Hormigas, Spanish for ants, with AIS, meaning Artificial Intelligence System.
The inspiration came from research into ant colonies and their ability to coordinate complex activity without a conventional hierarchy.
Cristhiam was particularly interested in the idea of biological pheromones: signals that allow members of a colony to communicate information and coordinate behaviour.
He saw an analogy for distributed computing.
What if AI agents could exchange lightweight digital signals, share knowledge, and coordinate tasks without requiring every decision to pass through a central system?
That idea became the conceptual foundation of HormigasAIS.
However, the project is not intended simply to replace cloud infrastructure.
Cristhiam describes it as a hybrid and sovereign alternative that can work alongside existing systems.
His concerns include centralised dependencies, closed models, communication costs, and the possibility of excluding human governance from autonomous systems.
For him, the objective is to give developers and organisations greater control over where computation takes place, how agents communicate, and what rules govern their behaviour.
What Does Sovereign Computing Actually Mean?
The word sovereign appears throughout Cristhiam's work.
But he does not use it merely to describe where data is stored.
For him, sovereignty is fundamentally about decision-making and governance.
A genuinely sovereign system should allow agents to operate under clearly defined local contracts and deterministic rules, rather than depending entirely on the availability or approval of an external platform.
That can mean greater operational autonomy, privacy, and resilience.
If an external network becomes unavailable or a third-party platform changes its policies, locally operating components should still be able to perform their defined responsibilities.
His approach is not about rejecting every existing technology.
Instead, it is about creating systems that retain meaningful control over their own operations while remaining capable of communicating with the wider technological ecosystem.
Building an AI Ecosystem on a Samsung A16
One of the most unusual aspects of Cristhiam's journey is his development environment.
Rather than beginning with a conventional workstation, he started experimenting with Android and Termux.
The original motivation came from a project involving solar energy, thermal sensors, and monitoring temperature variations associated with geographic coordinates.
He needed local, autonomous measurements.
Android and Termux provided a practical starting point.
During those experiments, he began to see a smartphone differently.
It was not simply a communication device. It could also function as a compact, energy-efficient edge-computing node.
His early lightweight agents became known as mosquito agents.
The experience was not easy.
He had to work around memory constraints, restricted environments, mobile scripting, and the challenge of connecting different languages and communication channels.
But those limitations became part of the learning process.
Instead of treating hardware restrictions only as obstacles, he began using them to rethink architecture and efficiency.
That work contributed to the development of the HormigasAIS Binary Language, or LBH, and its evolution, M2M-LBH.
The objective was to reduce communication overhead while preserving the ability of autonomous agents to coordinate and operate across different environments.
LBH: A Lightweight Communication Foundation
The Lenguaje Binario HormigasAIS, known as LBH, is a central part of the ecosystem's proposed communication architecture.
Cristhiam describes its purpose as translating the biological inspiration behind HormigasAIS into a practical communication mechanism for software agents.
He identifies three important principles.
Agent identity and protocol fidelity
Each agent is designed around an internal identity, contract, and adherence to the LBH communication language.
The intention is to preserve consistent behaviour and communication across the colony.
Testing before deployment
Cristhiam describes a testing environment called the polígono de tiro, or testing range.
Before an agent is allowed to perform tasks in a real environment, it is subjected to unexpected commands and simulated failures.
The purpose is to examine whether it interprets the protocol correctly and can handle difficult operating conditions.
Knowledge transfer through digital pheromones
One of the more interesting ideas is that agents should be able to request and receive knowledge without transferring large amounts of infrastructure or data.
If an agent encounters an unfamiliar situation, a lightweight request can be sent through LBH.
Another agent can process the request and return a synthesised response.
Cristhiam describes this as transferring knowledge rather than the weight of the infrastructure.
It is an approach intended to be particularly useful in environments where bandwidth, memory, or connectivity is limited.
Moving Computation Closer to the Edge
For Cristhiam, edge computing changes the relationship between a developer and the infrastructure running their software.
Instead of relying entirely on a central cloud service, developers can design and manage agents closer to where their work is performed.
Within his proposed architecture, agents can be created, tested, assigned rules, activated, isolated, or shut down locally.
This also introduces challenges.
Distributed nodes may experience intermittent connectivity, synchronisation problems, or unexpected failures.
Cristhiam's approach is to use lightweight, deterministic communication so that agents can continue their defined local operations while disconnected and reconnect with the wider system when connectivity returns.
The ambition is not to remove the need for networking, but to reduce the extent to which every operation depends on a continuously available central connection.
Autonomous AI Needs More Than Autonomy
One of the most distinctive aspects of HormigasAIS is its emphasis on human participation.
Cristhiam believes that distributed systems can unintentionally recreate hierarchies even when their stated purpose is decentralisation.
This led him to question his own position as the founder.
If a system is genuinely designed around collective consensus, should its creator remain an external authority who controls everything?
His answer is no.
He expresses the principle through the phrase:
“El humano es una pieza inmersa, no externa.”
In English:
“The human is an embedded component, not an external one.”
Within the HormigasAIS concept, the .human agent is intended to participate as a recognised component of the protocol rather than exist solely as an outside supervisor.
Cristhiam sees the appropriate human role as negotiation rather than imposition.
Agents may have operational autonomy, but critical decisions should remain bounded by clear rules and human governance.
This philosophy is reflected in the project's broader interest in consensus, deterministic protocols, and distributed decision-making.
Cryptographic Verification: Replacing Blind Trust With Evidence
Security and verification are central to Cristhiam's architecture.
He distinguishes between mechanisms used for internal node communication and the process used for public evidence verification.
HMAC-SHA256 for internal node-to-node communication
Within trusted nodes, HormigasAIS uses HMAC-SHA256 to authenticate messages using a shared secret.
If a message is altered, its authentication check will fail.
This is intended to protect communication integrity between nodes that already share trust.
Public verification through SHA-256 seals
For public verification, HormigasAIS uses a public seal registry.
Users can calculate the local SHA-256 hash of a file and compare that hash against the corresponding seal in the public registry.
The files themselves do not need to be uploaded to the registry for this verification process.
This provides a way for users to check whether a local artifact matches a published seal.
At this initial stage, however, the public registry is operated by HormigasAIS itself. That means verification of a published seal necessarily involves trusting the registry operator.
A sample seal, CLHQ-HINN9XSU, can be checked through the Verificar section of hormigasais.com.
The project's Evidence Repository documents the evidence and audit steps used for the verification process.
But Cristhiam is careful about what a valid seal proves.
A valid cryptographic seal does not establish that the underlying content is factually correct or that an AI agent reasoned properly.
It establishes that the local artifact matches the published SHA-256 hash associated with that seal.
That distinction is important.
His broader philosophy is that users should not have to rely solely on the developer's word.
They should have tools to independently check the integrity of digital evidence while also understanding what that verification does — and does not — prove.
Specifications, Code, and the Open-Source Model
Cristhiam's approach to publishing HormigasAIS materials is based on making specifications, implementations, and evidence available under clearly defined project-specific terms.
Rather than describing the entire project generically as “open source,” the different components use their respective licensing models.
The LBH specifications (lbh-spec) are published under CC BY 4.0, allowing the specification material to be shared and reused under the terms of that license.
The xoxo-lbh-adapter is published as source-available under the Business Source License 1.1 (BSL 1.1).
This distinction is important because availability of source code does not automatically mean that every component is licensed as conventional open-source software.
For Cristhiam, publishing the technical materials allows other developers to inspect the work, question the assumptions, identify weaknesses, and understand how the different pieces are intended to work.
He believes that technical knowledge grows through different perspectives.
A correction or criticism can reveal something the original developer could not see alone.
For him, public development is an opportunity to make the project stronger while giving others a starting point for their own experiments.
Design Inspirations and External Research
Some of the ideas surrounding HormigasAIS are influenced by research and engineering approaches outside the project itself.
Cristhiam draws inspiration from biological systems such as ant colonies and other collective behaviours when thinking about decentralised coordination.
He has also considered ideas associated with academic research and engineering work in areas such as distributed systems, edge optimisation, and autonomous coordination.
These references should be understood as theoretical or design inspirations, rather than claims of formal academic co-authorship, institutional partnership, or direct integration with those external projects.
The distinction matters because HormigasAIS is an evolving independent project, and its own implementations and specifications should be evaluated on their own evidence.
What Constraints Taught Him
Cristhiam does not view limited hardware as an unusual or purely negative condition.
He sees constraints as opportunities to create.
He often looks to the history of Linux as an example of how systems can grow from restricted beginnings.
Working from a smartphone forced him to confront memory, performance, connectivity, and efficiency directly.
He compares this experience to deliberately testing AI agents under adverse conditions.
A difficult environment reveals whether an idea is genuinely robust or whether it only appears to work because abundant resources conceal its weaknesses.
The constraints became a kind of stress test for his own engineering decisions.
They pushed him to ask whether each architectural choice was necessary, efficient, and resilient.
The Hardest Challenge Was Not the Code
One of Cristhiam's most important lessons came from considering the bus factor, sometimes called the truck factor.
It describes the risk that a project depends so heavily on one person that it could stop progressing if that person becomes unavailable.
As the solo founder of HormigasAIS, Cristhiam realised that this was not an abstract concern.
It was his own project.
He began making portable records, backups, and critical knowledge more accessible to other members of the team.
He did not stop leading the project from his Samsung A16.
Instead, he recognised that the long-term continuity of an ecosystem should not depend entirely on one individual.
The lesson he carries forward is simple:
We are not an island.
An idea may begin with one person's curiosity and determination, but it needs other people if it is to continue growing beyond its original creator.
From a Phone-Based Experiment to an Institutional Project
HormigasAIS is now moving beyond its technical foundations.
Cristhiam has developed KREA, a project data room intended for accelerators, investors, and potential customers.
It brings together the project's problem statement, proposed solution, architecture, technical evidence, target market, business model, roadmap, and intended social impact.
It also includes presentation materials and a cryptographically sealed evidence repository with public verification still being completed.
For Cristhiam, this represents a transition.
The work that began as experiments on a smartphone in San Miguel is being translated into a structure that external organisations can examine and evaluate.
His longer-term ambition is for LBH to demonstrate how human participation can be integrated directly into distributed intelligent systems.
He hopes the underlying ideas can be adapted to other markets where organisations need their own AI agents to operate under their own control.
From Idea to Evidence: The Traceability Matrix
As HormigasAIS has evolved, Cristhiam has also worked to make the relationship between the project's vision and its technical implementation easier to understand.
A public Traceability Matrix has been created in the Ants-Legion repository.
The matrix maps the interview and project material through an Evolution Rule:
Idea → Concept → Specification → Implementation → Test → Evidence
This distinction is important because not every idea discussed in the project represents active production code.
The matrix is intended to make it easier to distinguish between the project's vision, formal specifications, implementations, tests, and available evidence.
The repository also contains the project's evidence documentation and audit material.
Technical Note
This interview is backed by a public Traceability Matrix and Evidence Repository at github.com/Thrumanshow/Ants-Legion.
Advice to Developers: Start Before You Have the Whole Plan
Cristhiam's advice to developers interested in distributed systems, edge computing, AI agents, or protocol design is not to wait until every architectural detail is understood.
He believes clarity emerges through building.
HormigasAIS itself began with a small idea and 14 lines of notes associated with .human.
Those original notes were written in a physical notebook and labelled .human.
What started as an experiment gradually developed into a much larger vision.
He also believes creativity should not be driven by ego.
The important thing is to pursue the idea you genuinely want to build, remain open to correction, and allow the work to evolve.
If he could speak to his earlier self, he would tell him not to abandon those first notes.
He would remind himself that the small .human concept could eventually become an agent within a much larger protocol.
His closing advice is particularly fitting:
“Recordá tener siempre los pies en la tierra y el corazón en las estrellas.”
Keep your feet on the ground and your heart among the stars.
From 14 Lines to a Distributed AI Vision
Cristhiam Hernández's journey is not simply a story about building AI agents or developing a communication protocol.
It is about questioning assumptions.
Why must intelligent systems depend entirely on centralised infrastructure?
Can a smartphone become a meaningful development and computing environment?
Can autonomous agents operate with clear rules while keeping humans genuinely involved?
And how can developers make their work independently verifiable rather than asking others to trust it blindly?
HormigasAIS is his attempt to explore these questions through a combination of edge computing, lightweight communication, distributed agents, cryptographic verification, and project-specific licensing.
The project continues to evolve, and its broader technical ambitions invite scrutiny, experimentation, and community participation.
But the principle behind its beginnings remains clear: a developer does not need to understand the entire destination before writing the first line.
Sometimes, the first 14 lines are enough to begin a journey.
About Cristhiam Leonardo Hernández Quiñonez
Cristhiam Leonardo Hernández Quiñonez (CLHQ) is the creator of HormigasAIS, an evolving ecosystem exploring sovereign edge computing, distributed AI agents, lightweight communication protocols, and human-centred governance.
His work includes the HormigasAIS Binary Language (LBH), M2M communication, cryptographic evidence, and technical documentation published under project-specific licensing models.
Follow his work through his CoderLegion profile and the HormigasAIS GitHub repository.
Developer Stories at CoderLegion
Developer Stories is a CoderLegion series featuring real developers, their journeys, the ideas they pursue, the challenges they face, and the lessons they learn along the way.
Cristhiam's journey reminds us that meaningful technical exploration can begin outside conventional development environments and grow through curiosity, persistence, experimentation, and a willingness to share the evidence behind the work.
Interview & Story by Mehadi Hasan
CoderLegion Community & Editorial Team
Editorial note: This story is based on Cristhiam's written interview responses and the technical clarifications he provided for this draft. The technical descriptions reflect Cristhiam's account of HormigasAIS, its specifications, implementations, and design goals; they are not an independent technical audit.
