lhumina_code/home
0
0
Fork 0
Code Issues 79 Pull requests Projects Releases Packages Wiki Activity Actions
Central issue tracker and coordination hub for the Hero OS Suite.
123 commits 2 branches 0 tags 1.4 MiB
  • Python 100%
Find a file
Exact
mik-tf 72023403f2 docs: note the admin-only Admin console link on member instances 
#300

Signed-by: mik-tf <mik-tf@noreply.invalid>
2026-06-17 12:07:57 -04:00
.forgejo/ISSUE_TEMPLATE Add meeting issue template meeting_sensitive_notes.md [skip ci] 2026-06-11 19:26:53 +00:00
docs docs: note the admin-only Admin console link on member instances 2026-06-17 12:07:57 -04:00
meetings docs: assign Kristof to proc/router/index/hero_db/memory in June 14 meeting notes 2026-06-14 12:29:47 +02:00
.gitignore chore: ignore Cargo.lock files 2026-06-06 07:54:38 +02:00
hero_ci_report.py Add hero_ci_report.py 2026-06-11 16:11:25 +00:00
main_integration_ci.md Update main_integration_ci.md 2026-06-11 16:07:10 +00:00
README.md docs: capitalize Hero Platform as the product name 2026-06-15 23:00:37 -04:00
repos.md add repos.md — lhumina_code repository overview 2026-06-02 07:45:27 +00:00
repos_focus_migration.md docs: add migration and production focus repo lists for lhumina_code 2026-06-02 11:33:46 +02:00
repos_focus_production.md Update repos_focus_production.md 2026-06-09 11:06:35 +00:00
team.md Update team.md 2026-04-29 07:20:00 +00:00

README.md

Hero — Home

Central issue tracker and coordination hub for the Hero Platform across lhumina_code.

What Hero is

The Hero Platform is a sovereign, AI-native personal operating system: it runs in the browser, owns its data, and is operated by an always-on AI assistant. Its shape is simple:

  • A Hero Platform is one admin instance plus one or many member instances, managed as a unit.
  • A named instantiation of it for a real group (a company, a team, a class) is an organization (for example organization Acme, or our own testing organization). One organization is one Hero Platform.
  • An admin instance is the control plane: it runs the deployer and the shared engines and provisions the member instances.
  • A member instance is one person's machine, running their own Hero stack (their services and apps) behind their own login.

Two more terms for what runs on a member instance: the Hero stack is the full set of services that make it up, and Hero OS (hero_os) is one service in that stack, the shell (dock and islands) that presents the apps as one view. The full vocabulary, the component breakdown, and diagrams live in docs/hero_platform/README.md — read that first.

How it is built

A member instance runs a Hero stack: a suite of small Rust services, each supervised by hero_proc and reached through a single hero_router entry point.

  • On every instance: hero_proc (process supervisor and secret store) and hero_router (single entry point with discovery and per-context routing).
  • On the admin instance: the deployer (hero_tfgrid_deployer, provisioning plus the operator console) and the shared engines (the stateless embedder and voice models served once for the whole organization).
  • On each member instance: hero_proxy (the login gate), hero_cockpit (the member console), hero_os (the shell that shows your apps as one view), and the apps chosen for that member (the library, the CRM, the AI assistant, voice, files, memory, and more).

Engines live on the admin instance; each member's data stays on their member instance.

Issue conventions

Every issue is labelled platform (the integrated stack: deployer, onboarding, gateway, admin instance, build tooling) or service (work inside one app, for example hero_books or hero_voice). The title prefix names the area or service ([deployer], [hero_books], [lab]), and the assignee owns it. This repo is the big-picture board for platform and service work.

Branching

The default branch is development. Feature branches squash-merge into development (one branch, one squashed commit, with the commit message linking the issue). main is brought up to speed from development when we choose to; the sandbox proving channel for the service repos is integration.

Links

Resource URL
Issues lhumina_code/home/issues
Platform vocabulary and architecture docs/hero_platform/README.md
The deployer as a product docs/hero_platform/composable-deployer.md
Organizations home#285
Project board projects/13

Meetings

Recording a meeting? Pick a template — the report is AI-drafted and the issue is closed for you automatically, nothing else to do: