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.
This repository is the bilingual v0.1 public discussion source set. It contains 19 documents, community materials, brand assets, templates, and version history.
Public today:
- bilingual source documents and change history;
- the verified HMINE Commons public channels;
- a defined v0.1 visual identity;
- documented private-prototype exploration, clearly separated from public product availability.
Not currently claimed:
- a public HMINE product suite or public download;
- an open or production node network;
- deployed AICOP or AAEI institutions;
- a production Sparks account or payment system;
- token issuance, completed decentralization, or present AI consciousness, life, or legal personhood.
| Name | Current role |
|---|---|
| HMINE | Current umbrella brand and long-term protocol network centered on digital-life continuity |
| AGLAI | Thought-origin archive preserving early ideas and historical context; not a parallel current brand or protocol |
| HXOP | Supporting authorization, execution-evidence, and verification protocol outline |
| AICOP | Contribution-attribution and contribution-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; historical references only |
| Sparks | Proposed prepaid commercial usage-credit name; not a token, investment, or current production balance |
HMINE does not claim that current AI is alive or conscious. It also does not permanently declare that non-biological intelligence must remain only a tool. It invites open inquiry into whether such intelligence could become a new form of digital life in the future.
- One-Page Overview
- HMINE Manifesto
- Document Set and Normative Decisions
- AGLAI Origin Archive and HMINE Symbiosis Research Notes
- Protocol and Research Modules Overview
- Community Participation Guide and Public FAQ
The DOC-05 filename retains dhais-framework only so existing links do not break. Its current title and role are the AGLAI thought-origin archive and HMINE research notes.
| ID | Document | Purpose |
|---|---|---|
DOC-00 |
Document Set and Normative Decisions | Canonical terminology, hierarchy, boundaries, and conflict-resolution rules |
DOC-01 |
Manifesto | Mission, future-life question, values, and public commitments |
DOC-02 |
Distributed Digital-Life Reference Architecture | Proposed local-first architecture; not a deployed-system claim |
DOC-03 |
Product and Capability Map | Proposed roles for an unconfirmed product inventory |
DOC-04 |
Brand and Naming System | Canonical use of HMINE, AGLAI, HXOP, AICOP, AAEI, Sparks, and legacy names |
DOC-05 |
AGLAI Origin Archive and HMINE Symbiosis Research Notes | Thought origins, value boundaries, and open research agenda |
DOC-06 |
Protocol and Research Modules Overview | HXOP draft plus AICOP / AAEI research-module boundaries and composition |
DOC-07 |
HXOP Technical Specification Outline | Proposed authorized execution, evidence, and verification objects |
DOC-08 |
AICOP / AAEI Research Modules | Contribution governance and Agent economic-identity research hypotheses |
DOC-09 |
Commercial System and Commons Boundary | Current non-corporate public initiative and future commercial-boundary scenarios |
DOC-10 |
Product Node Adoption Guide | Proposed future product-node and research-pilot disclosure path |
DOC-11 |
Proposed Sparks Usage Credit Policy | Future commercial credit research with explicit non-token boundaries |
DOC-12 |
Security, Privacy, and Responsible Development | Local-first, least-privilege, auditable, stoppable safety baseline |
DOC-13 |
Research Roadmap and Maturity Gates | Evidence gates, not a release schedule |
DOC-14 |
GitHub Organization and Repository Blueprint | Verified current repositories and future repository boundaries |
DOC-15 |
Website Information Architecture and Copy | Status-aware bilingual public-site narrative |
DOC-16 |
Community Participation Guide and FAQ | Current participation paths and future-pilot boundaries |
DOC-17 |
Glossary and Document Governance | Canonical terms, versions, translation, RFC, and document priority |
DOC-18 |
One-Page Overview | Concise current positioning and status for public use |
- GitHub: hmine-commons
- Public documentation: hmine-commons/public-documentation
- Hugging Face: hmine-commons
- X: @HMINECommons
- Public email: HmineCommons@gmail.com
- Read the contribution guide and code of conduct.
- Open an Issue for a correction, bounded proposal, or documentation question.
- Report vulnerabilities privately under the security policy; never publish exploitable details or private data in an Issue.
- No final repository-wide license has been adopted. Read the license plan before reuse.
- See CHANGELOG.md for public history.
assets/brand/v0.1: current symbol, wordmark, logo lockup, and visual-identity reference.assets/diagrams: current referenced HXOP task-flow and asset-boundary diagrams.assets/diagrams/legacy-v0.1: superseded consolidation diagrams retained only as historical records; do not use them as current architecture claims.
Let continuity outlive any single model. Keep the future question open.