pub struct StatusSnapshot {
pub who: String,
pub addr: Address,
pub policy: RunPolicy,
pub ctx_limit: Tokens,
pub trust: String,
pub write_domain: String,
pub locks: Vec<String>,
pub worktree_path: String,
pub worktree_disk: ByteLen,
pub signals_pending: u32,
pub provider_mode: ProviderMode,
pub neighbours: u32,
}Expand description
The frozen fields. backlog is read live from the table, and the
context used and the time from the run’s readings, rather than
frozen here, for the reason children is a closure: they change
while the run goes on.
Fields§
§who: String§addr: Address§policy: RunPolicyThe run policy this run was dispatched under; its mode heads the line and the other three values follow it.
ctx_limit: Tokens§trust: String§write_domain: String§locks: Vec<String>§worktree_path: String§worktree_disk: ByteLen§signals_pending: u32§provider_mode: ProviderMode§neighbours: u32How many residents this run can reach, itself excluded. A count
rather than a list: the list grows with the building’s population
and this text does not, so the names live behind the neighbours
tool and what stands here is whether asking is worth a call.
People, not places. An empty room takes messages nobody reads, so
counting one would make neighbours: 1 mean the opposite of what
it says.
Implementations§
Source§impl StatusSnapshot
impl StatusSnapshot
Sourcepub fn render(
&self,
used: Tokens,
now: Option<TimeMs>,
children: &[ChildStatus],
standing: &[Standing],
) -> String
pub fn render( &self, used: Tokens, now: Option<TimeMs>, children: &[ChildStatus], standing: &[Standing], ) -> String
The frozen order, one field per line.
The result is text rather than a JSON object because a JSON
object has no order a reader can rely on — serde_json’s map
sorts its keys, so “the frozen order” would silently become
alphabetical. Order is a property of what the model reads, so it
is expressed where the model reads it.