Slice-based VM compute manager for the Hero Ecosystem, built on hero_rpc OSIS framework
- Rust 70%
- JavaScript 17.1%
- HTML 11.2%
- CSS 1.7%
8cda13c866
All checks were successful
Test / test (push) Successful in 5m53s
Lets a second my_compute_zos_server run on the same admin VM serving a different TFGrid chain, without disturbing the default daemon: - Configurable hero_proc config context (HERO_COMPUTE_CONFIG_CONTEXT env, default `core`): the daemon reads TFGRID_MNEMONIC / TFGRID_NETWORK and all its config from that context, so a second daemon holds its own wallet + chain under e.g. `compute_main`. - Chain-scoped on-disk node/VM store (cloud_db_path): `core` keeps the original compute_tfgrid/data/root/cloud path (no migration), other contexts get their own subtree, so each per-chain daemon only lists nodes registered on its own chain. Both default to the original single-daemon behaviour byte-for-byte. Signed-by: mik-tf <mik-tf@noreply.invalid> |
||
|---|---|---|
| .deepseek | ||
| .forgejo/workflows | ||
| .hero | ||
| crates | ||
| docs | ||
| schemas | ||
| .env.example | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| PURPOSE.md | ||
| README.md | ||
hero_compute
Multi-platform compute management for the Hero ecosystem.
A user, agent, or HeroOS application uses one clean compute interface. The platform routes workloads transparently to either ZeroOS (ThreeFold Grid 3) or MyceliumOS nodes.
Full specification: docs/architecture.md
Layers
Layer 1 — HeroOS
hero_compute_server User-facing compute API
hero_compute_sdk Client library for apps and agents
hero_compute_admin End-user / HeroOS admin UI (talks to hero_compute_server)
Layer 2 — Mycelium Compute Services
my_compute_explorer_server Central aggregation, node registry, routing
my_compute_explorer_sdk Client SDK for the explorer
my_compute_explorer_admin Infrastructure operator dashboard
my_compute_zos_server Compatibility adapter for ThreeFold Grid 3 / ZeroOS
my_compute_zos_sdk Client SDK for the ZOS adapter
my_compute_zos_admin ZOS / Grid 3 debug and operations UI
Layer 3 — Compute Execution (per node)
my_compute_mos_server Local agent running on each MyceliumOS node
my_compute_mos_sdk Client SDK for the MOS agent
my_compute_mos_admin MOS node-local debug and operations UI
Crates
| Crate | Layer | What it is | Status |
|---|---|---|---|
hero_compute_server |
HeroOS | User-facing compute API server | skeleton |
hero_compute_sdk |
HeroOS | Client library for apps and agents | skeleton |
my_compute_explorer_server |
Mycelium | Node registry, fleet aggregation, RPC routing | implemented |
my_compute_explorer_sdk |
Mycelium | Client SDK for the explorer | skeleton |
my_compute_explorer_admin |
Mycelium | Infrastructure operator dashboard | implemented |
my_compute_zos_server |
Mycelium | ThreeFold Grid 3 / ZeroOS adapter | implemented |
my_compute_zos_sdk |
Mycelium | Client SDK for the ZOS adapter | skeleton |
my_compute_zos_admin |
Mycelium | ZOS / Grid 3 debug UI | skeleton |
my_compute_mos_server |
MOS Node | Local node agent, talks to local hypervisor | implemented |
my_compute_mos_sdk |
MOS Node | Client SDK for the MOS agent | skeleton |
my_compute_mos_admin |
MOS Node | MOS node-local debug UI | skeleton |
Operating systems
| Name | Short | Meaning |
|---|---|---|
| ZeroOS | ZOS | Existing OS used by ThreeFold Grid 3 nodes |
| MyceliumOS | MOS | New OS for next-generation nodes (Ubuntu + ZeroOS4) |
| HeroOS | HeroOS | User-facing environment where apps and agents run |