README (1898B)
1 # radroots_runtime_manager 2 3 `radroots_runtime_manager` validates the frozen runtime-management contract and 4 binds explicitly resolved Myc and RHI `RuntimeContext` values to the common 5 service-management interfaces. 6 7 The sealed target uses its `RuntimeContext` as the sole service, instance, 8 profile, and canonical-path authority. It can produce exact CLI-v1 argument 9 plans for the common `config init`, `config validate`, `state init`, `run`, 10 `status`, and `doctor` commands. On Linux and macOS it can also construct the 11 shared bounded HTTP/1.1-over-Unix admin client for the fixed `/v1/status` 12 endpoint. Service-owned typed status models must expose the common v1 identity 13 projection, and every response is rejected unless its contract version, 14 service, and instance match the selected runtime context. 15 16 This crate never discovers or executes a program, opens a PID/config/log file, 17 reads credentials, owns a service process, mutates canonical paths, or selects 18 an archive, binary, channel, package, or install location. Artifact and 19 distribution resolution remains separately governed by Step220. The status 20 client performs only the bounded request explicitly initiated by its caller; 21 target construction itself performs no I/O. 22 23 Complete management TOML documents are rejected before parsing when they 24 exceed exactly 1,048,576 UTF-8 bytes. Bounded documents still require the exact 25 schema, version, closed field set, active Myc/RHI inventory, common CLI/admin 26 clients, lifecycle vocabulary, and service metadata. Directly constructed 27 contracts are revalidated before a management context can be created. 28 29 ## Copyright 30 31 Except as otherwise noted, all files in the `radroots_runtime_manager` 32 distribution are 33 34 Copyright (c) 2025 Tyson Lupul 35 36 For information on usage and redistribution, and for a DISCLAIMER OF ALL 37 WARRANTIES, see LICENSE included in the `radroots_runtime_manager` 38 distribution.