No description
| README.md | ||
Home
Central issue tracker and coordination hub for the Hero OS Suite.
This repo contains no code. It is used for cross-repo issues, project planning, and deployment coordination.
Repositories
| Repo | Purpose |
|---|---|
hero_os |
Hero OS shell, Dioxus WASM desktop environment, styles.css, theme engine |
hero_archipelagos |
WASM island components, forms, viewers, editors (Dioxus 0.7) |
hero_osis |
OSIS data layer, server, seed data, schema definitions |
hero_services |
Service orchestration, Dockerfile, zinit configs, deployment |
hero_lib |
Shared Rust library, AI, crypto, OS, text, OSIS packages |
hero_rpc |
OpenRPC framework, JSON-RPC server/client, Unix sockets |
hero_auth |
Authentication service |
hero_indexer |
Full-text search server |
hero_embedder |
AI embedding service |
hero_redis |
Redis integration |
hero_inspector |
Service discovery and MCP gateway |
Branching Model
All repos use development as the default branch.
development: default, always deployabledevelopment_{name}: feature branches for fast-paced AI-assisted developmentmain: releases (when ready)
One branch, one commit, one issue
AI-assisted development generates many commits fast. To keep history clean and traceable, we follow a strict rule:
- Each feature branch (
development_{name}) is squashed into one commit before merging todevelopment - That commit message links to the issue, e.g.:
https://forge.ourworld.tf/lhumina_code/home/issues/8 — Differentiate Identity Seed Data per Context - One branch = one commit = one issue on
development
This means every commit on development represents a complete, reviewed piece of work and links directly to the issue that describes it.
Workflow
- Branch
development_{name}from latestdevelopment - Work on
development_{name}(as many commits as needed) - Merge
developmentintodevelopment_{name}periodically (never rebase) - When ready, squash into one commit with the issue URL as the commit message
- Merge
development_{name}intodevelopment