hero_planner

Business planning & execution backend — SWOT → conditions → requirements → stories → deliverables → milestones → cost centers → costs → resources.

Components

Crate	Binary	Socket	Purpose
hero_planner_server	hero_planner_server	~/hero/var/sockets/hero_planner/rpc.sock	JSON-RPC backend (OpenRPC)
hero_planner_admin	hero_planner_admin	~/hero/var/sockets/hero_planner/admin.sock	Admin dashboard (Askama)
hero_planner_web	hero_planner_web	~/hero/var/sockets/hero_planner/web.sock	End-user web app (Bootstrap)
hero_planner_lib	—	—	Shared planner core library
hero_planner_sdk	—	—	Generated OpenRPC client SDK

Lifecycle

Per ADR-0001, lab owns the full build / install / start / stop / status pipeline on top of hero_proc. There is no Makefile, no bash scripts, and no service_<name>.nu module.

# Build + install + register + start all three binaries
lab build --install --start --no-upx

# Stop
lab build --stop

# Status
lab build --status

Smoke test

SOCK=~/hero/var/sockets/hero_planner/rpc.sock

curl -s --unix-socket $SOCK http://localhost/health | jq .
curl -s --unix-socket $SOCK http://localhost/openrpc.json | jq '.methods[].name'
curl -s --unix-socket $SOCK http://localhost/.well-known/heroservice.json | jq .