LOCI v0.1.123 (Date: 19 Aug 2026)
LOCI's live cockpit ships for the first time in this release, alongside a new way to set and check bounds, a timing model that finally accounts for loops, and two fixes.
New
loci cockpit— A live, terminal-only view of what LOCI is doing on this branch, no browser or sign-in required. The default view streams every skill run the moment it happens — skill, function, verdict, and the delta that drove it (for example, "post-edit: worst path +340 ns — FAIL"). Four focused views are one flag away: the functions costing the most time, energy, and stack (--altitude hotspots); the regressions Plan Guard and Save Guard caught before they merged (prevented); the analysis time LOCI spent versus the runtime measurement it replaced (time-saved); and every bound in your Contract Envelope next to its latest measurement (contract).Contract Envelope (
contract) — Set explicit bounds for any function, in plain language: "capISR_Handlerat 200 B of stack," "fail the build ifprocess_frame()regresses past 5%." LOCI drafts the entry from your request; you review and apply it — one committed file (.loci/contract.yaml) holding every bound your repository requires. Plan Guard and Save Guard verdicts are now judged against these bounds where they exist, not only against the previous build.
Improved
One verdict vocabulary, everywhere — Plan Guard and Save Guard now both close on the same three words —
PASS,CAUTION,FAIL— instead of two different sets. If you were used to readingGOOD/ADJUST PLAN/STOPorOK/CAUTION/FLAG, that's what changed; the underlying judgment is the same, just consistent now.Timing predictions now account for loops — Save Guard and Plan Guard used to price a loop's body once, the same as a straight-line block, understating the true worst-case cost of anything that runs more than once per call. Timing now multiplies each loop's cost by its actual iteration count, so the number you see is the number that actually runs.
Fixed
Plugin updates no longer break the
lociCLI — A lock file left behind by an interrupted install could block every future CLI install, even after a restart, if the operating system reused the old process ID. LOCI now checks that the process holding the lock is genuinely still doing the work it claims before trusting it.Cockpit's contract panel shows minimum bounds correctly — Fixed a display bug where a bound set as a floor (a minimum) could render incorrectly in the
contractpanel.
Questions or feedback? loci@auroralabs.com
Last updated
Was this helpful?
