pub struct CityAnswer {
pub runs: Vec<RunSummary>,
pub active: u64,
pub frozen: u64,
pub buildings: Vec<BuildingProgress>,
pub pursuits: Vec<PursuitLine>,
pub halted: Vec<HaltScope>,
pub proved: Option<Seq>,
}Fields§
§runs: Vec<RunSummary>Every active run and the latest frozen few, in RunId order;
frozen counts every frozen run, listed or not.
active: u64§frozen: u64§buildings: Vec<BuildingProgress>One entry per building whose roadmap the city could read.
pursuits: Vec<PursuitLine>The standing goals this city is working towards, if any.
halted: Vec<HaltScope>The scopes shut by halt and not yet released, in the shape a
halt frame names them. A page that has just opened has no
other way to learn that the city is stopped.
The same type the command carries, not the ledger’s string form:
a reader that had to take building:<addr> apart would be
writing a second copy of a grammar that already has one, and the
first client to get it wrong reported every shut building as
running.
proved: Option<Seq>The last record of a history proved whole, when the proof has
found it so; absent while a served city is still proving it, or
after the proof found it broken (crates/wire/spec/Answer.lean §8-63).