Every Monomer declares one runtime tier. The tier describes the execution environment, not the trust level of the workload and not the authority it may receive.
| Tier | Environment | Intended use |
|---|---|---|
micromer-minimal | Bare-metal Rust appliance | Small policy, key-custody, attestation, and logging roles built from the Micromer library. |
tamago-minimal | Bare-metal TamaGo Go appliance | Small Go appliance roles, including hardware-oriented targets. |
hermit-middle | Hermit unikernel | Services that need more runtime support than a minimal appliance without a full Linux guest. |
linux-full | Full Linux VM | Browsers, desktops, development environments, containers, and agent runtimes. |
Runtime tier does not imply permission. Network, device, secret, and lifecycle authority remain separate policy decisions. A smaller tier can still process hostile input, and a linux-full Monomer can still run without network access.
See Micromer and Monomer for the source and VM boundaries.