System monitor

observe-only · can start & stop, nothing else
Memory
21.4 / 24 GB
CPU
38% · 24 cores
Compartments
6 live
Browser untrusted
MEM
25.1 / 32 GB
CPU
weight 20
Dev trusted
MEM
5.4 / 16 GB
CPU
weight 40
Agent runtime scoped
MEM
2.1 / 4 GB
CPU
weight 30
Network system · micromer
MEM
96 / 512 MB
CPU
weight 10
The cap tick shows each compartment's memory ceiling — its bond's contract. A runaway app is throttled at its cap, never the whole machine.

A monitor that can watch and stop — nothing else. It observes usage and holds exactly two powers: adjust a compartment's resource contract, and stop it. Each memory bar shows usage against that compartment's cap (the tick) — the ceiling written into its bond, so a browser tab that eats 25 GB is throttled at its own 32 GB limit and never starves the machine. CPU is a weight, not a hard percent — share under contention. "Suspend all to disk" is the calm exit (sealed snapshot, resume later); "Emergency stop" is the presence-gated panic that signals terminate into every compartment at once. Concept render in the PolymerOS design language.