"El brazo ejecutor del ecosistema HormigasAIS"
HormigasAIS-Engine es el brazo ejecutor del ecosistema HormigasAIS. Este repositorio implementa la lógica técnica necesaria para que los principios, contratos y límites definidos en el núcleo conceptual del sistema puedan ejecutarse en entornos reales (Edge, Android y nodos distribuidos). El Engine transforma definición en acción, sin alterar el significado del sistema.
- Ejecutar lógica distribuida conforme al protocolo LBH
- Operar como motor técnico en entornos Edge / Android
- Gestionar puentes de comunicación entre nodos
- Validar acciones según contratos y límites de soberanía
- Garantizar ejecución coherente, observable y trazable
HormigasAIS-Engine no es el núcleo conceptual del sistema. Su rol es estrictamente ejecutor. Ninguna definición fundacional, filosófica o protocolar nace aquí. El Engine actúa únicamente sobre lo que ha sido definido en el núcleo.
- Lógica de ejecución distribuida
- Adaptadores de comunicación entre nodos
- Validadores de pulsos y estados
- Infraestructura de compilación y despliegue
- Ejecución bajo soberanía
- Observabilidad antes de acción
- Respeto estricto a contratos
- Separación entre definición y ejecución
El código fuente de este repositorio se distribuye bajo la: Apache License, Version 2.0
Esta licencia:
- Permite uso comercial y redistribución
- Incluye protección explícita frente a litigios de patentes
- Obliga a conservar avisos legales y archivo NOTICE
- No concede derechos sobre nombres, identidad o marcas
La autoría intelectual del sistema HormigasAIS no se transfiere mediante esta licencia.
El origen intelectual, el lenguaje LBH, el protocolo HormigasAIS y los principios fundacionales están definidos en: 📄 FOUNDATION.md
Este repositorio debe interpretarse siempre como una implementación técnica subordinada a dicho documento.
Autor original: Cristhiam Leonardo Hernández Quiñonez (CLHQ)
HormigasAIS-Engine is the execution arm of the HormigasAIS ecosystem. This repository implements the technical logic required to execute the principles, contracts, and boundaries defined in the system’s conceptual core across real environments (Edge, Android, and distributed nodes). The Engine turns definition into action without redefining meaning.
- Execute distributed logic according to the LBH protocol
- Operate as a technical engine in Edge / Android environments
- Manage communication bridges between nodes
- Validate actions against sovereignty and execution contracts
- Ensure coherent, observable, and traceable execution
HormigasAIS-Engine is not the conceptual core of the system. Its role is strictly executive. No foundational, philosophical, or protocol-level definitions originate here.
- Execution under sovereignty
- Observability before action
- Strict contract compliance
- Clear separation between definition and execution
The source code of this repository is distributed under the: Apache License, Version 2.0
The intellectual origin, LBH language, HormigasAIS protocol, and foundational principles are defined in: 📄 FOUNDATION.md
Original author: Cristhiam Leonardo Hernández Quiñonez (CLHQ)
Within the HormigasAIS ecosystem, entities are classified according to their role, authority scope, and interaction surface, rather than by their implementation form. Entity classification serves to:
- Define responsibility boundaries
- Constrain capability propagation
- Prevent implicit trust assumptions Classification does not imply disclosure.
Certain entities operate under conditions of intentional non-disclosure. Restricted entities may:
- Exist outside the repository scope
- Be instantiated dynamically
- Operate under execution contexts not observable from public artifacts The absence of implementation detail is by design and shall not be interpreted as incompleteness.
Identity within HormigasAIS is a prerequisite for action, not a byproduct of execution. Authority is derived from validated origin, alignment with governing contracts, and adherence to defined sovereignty boundaries.
This document establishes a clear boundary between what is declared, what is implemented, and what is intentionally withheld. Omissions related to activation sequences or defensive responses constitute a security control.
The presence of abstract security descriptions does not grant the right to replicate the full security posture of HormigasAIS. Replication of code does not imply replication of authority or legitimacy.
This security model reflects the current declared posture of the HormigasAIS Engine. It defines the conditions under which defense exists, not how the system defends itself.