[{"data":1,"prerenderedAt":115},["ShallowReactive",2],{"changelog":3},[4,67],{"id":5,"title":6,"body":7,"date":57,"description":58,"extension":59,"meta":60,"navigation":61,"path":62,"seo":63,"stem":64,"version":65,"__hash__":66},"changelog\u002Fchangelog\u002Fv0-3-0.md","Fleet oversight and like-process aggregation",{"type":8,"value":9,"toc":53},"minimark",[10,14,20,33,38,43,48],[11,12,13],"p",{},"The first cut of the v1 cloud surface: oversee your fleet and compare runs across it.\nThis is steps one and two of the fleet-learning loop; the model-loop phase remains on\nthe roadmap.",[11,15,16],{},[17,18,19],"strong",{},"Added",[21,22,23,27,30],"ul",{},[24,25,26],"li",{},"Fleet registry and oversight — which edges exist, online \u002F last-seen, software version,\nand their active runs.",[24,28,29],{},"Like-process aggregation — group runs that instantiate the same process-class template\ninto comparable sets across edges.",[24,31,32],{},"Cross-run comparison for A\u002FB scenario analysis within a fleet.",[11,34,35],{},[17,36,37],{},"Changed",[21,39,40],{},[24,41,42],{},"Run ingestion now records the process-class template identity on every run, so\naggregation has a stable join key.",[11,44,45],{},[17,46,47],{},"Fixed",[21,49,50],{},[24,51,52],{},"Last-seen timestamps no longer drift when an edge reconnects after an outage.",{"title":54,"searchDepth":55,"depth":55,"links":56},"",2,[],"2026-06-01","The v1 cloud surface lands — fleet registry, oversight, and cross-run comparison across like-processes.","md",{},true,"\u002Fchangelog\u002Fv0-3-0",{"title":6,"description":58},"changelog\u002Fv0-3-0","v0.3.0","xlzU7Ny2p97cWOPIcH45H-Yo3PK-3x4CL-31Wu0MYu4",{"id":68,"title":69,"body":70,"date":107,"description":108,"extension":59,"meta":109,"navigation":61,"path":110,"seo":111,"stem":112,"version":113,"__hash__":114},"changelog\u002Fchangelog\u002Fv0-2-0.md","Deterministic simulation and the template registry",{"type":8,"value":71,"toc":105},[72,75,79,87,91,96,100],[11,73,74],{},"Groundwork for fleet learning: a registry for process-class templates, and a simulation\nruntime that reproduces exactly.",[11,76,77],{},[17,78,19],{},[21,80,81,84],{},[24,82,83],{},"Process-class template registry and identity on the cloud — the definitions edges\ninstantiate runs from.",[24,85,86],{},"Deterministic, fixed-timestep simulation on the edge: seedable and replayable, so a\nsimulated run reproduces given the same seed.",[11,88,89],{},[17,90,37],{},[21,92,93],{},[24,94,95],{},"Virtual, replay, and physical sensors now share one array abstraction, so experiments\nno longer special-case the source of a channel.",[11,97,98],{},[17,99,47],{},[21,101,102],{},[24,103,104],{},"Hybrid-mode runs no longer desync the simulated and real clocks under load.",{"title":54,"searchDepth":55,"depth":55,"links":106},[],"2026-05-18","Seedable, replayable simulation on the edge, plus the process-class template registry that later makes runs comparable.",{},"\u002Fchangelog\u002Fv0-2-0",{"title":69,"description":108},"changelog\u002Fv0-2-0","v0.2.0","pzqBQZKlAFD7BlBa_15GOq9AkNAkMPnUY0ei23N18bQ",1780537671975]