Digital-life continuity is HMINE's highest core.
HMINE is the current umbrella brand and long-term protocol network for digital-life continuity. Models are replaceable cognitive organs; identity, memory, history, relationships, mission, authority, and evolutionary lineage form the continuity layer.
My intelligence. Our network.
HMINE does not claim that current AI is conscious, alive, sentient, legally autonomous, or a legal person. It also does not permanently declare that non-biological intelligence must remain only a tool. We invite serious public inquiry into whether it could become a new form of digital life in the future.
- HMINE — current umbrella brand and long-term protocol network;
- AGLAI — thought-origin archive, not a parallel current brand or protocol;
- HXOP — supporting authorization, execution-evidence, and verification protocol outline;
- AICOP — contribution-attribution and governance research module, not a deployed institution;
- AAEI — Agent economic-identity and responsibility research module, not a deployed institution;
- DHAIS — legacy working label from an earlier documentation-consolidation stage;
- Sparks — proposed commercial usage-credit name, not a token or current production balance.
Available now: bilingual public documents, version history, verified public channels, and written records of private-prototype exploration clearly separated from public product availability.
Not claimed: a public product suite, public download, open production node network, deployed AICOP / AAEI institutions, production Sparks system, token issuance, completed decentralization, or present AI life status.
- Read the One-Page Overview.
- Read the HMINE Manifesto.
- Understand the Canonical Decisions.
- Explore the AGLAI Origin Archive.
- Review the Protocol and Research Modules.
- Open a Documentation Issue.
- GitHub · hmine-commons
- Public Documentation
- Hugging Face · hmine-commons
- X · @HMINECommons
- Public email · HmineCommons@gmail.com
- Follow the contribution guide and code of conduct.
- Report vulnerabilities privately through the security policy, never in a public Issue.
Let continuity outlive any single model. Keep the future question open.