Separate `hero_lib` `osis` and relavant crates to a separate `hero_rpc` project #105

New issue

Closed

opened 2026-02-16 17:18:14 +00:00 by timur · 1 comment

timur commented

2026-02-16 17:18:14 +00:00

Owner

Currently, we have all our OpenRPC server - client generation from OSchema specifications in hero_lib. This is problematic for a few reason. Crowds hero_lib with a bunch of libraries only used for this purpose. Also we have hero_osis which is the OSIS server for hero_zero, and the OSIS code generation library has become more than a object storage and indexing system. Finally it would be easier for ai to know all relavant code is in the same project, especially since now the approach is to port existing backend's to OSchema generated servers.

Currently, we have all our `OpenRPC` server - client generation from `OSchema` specifications in hero_lib. This is problematic for a few reason. Crowds `hero_lib` with a bunch of libraries only used for this purpose. Also we have `hero_osis` which is the OSIS server for `hero_zero`, and the OSIS code generation library has become more than a object storage and indexing system. Finally it would be easier for ai to know all relavant code is in the same project, especially since now the approach is to port existing backend's to OSchema generated servers.