Changelog
All notable changes to loci. Format follows Keep a Changelog. The canonical changelog lives in the repository: huximaxi/loci.
v0.6.0-beta (2026-07-02)
The 0.6 open beta. The desktop app, the CLI, and the template shelves ship on one version line for the first time. Methodology line: loci-core 1.6-candidate.
Added
- Desktop cockpit: the dashboard grows a tab strip. One Operations view (the native dashboard) plus one tab per instrument your palace generates for itself (self-contained HTML pages with an embedded data payload, discovered by convention). Instruments render through path-validated embedding; traversal and symlink escapes are rejected.
- Tools gate-ledger: palaces that record tool verdicts in
palace-map.jsonget a "Tool shelf · gate ledger" section on the dashboard. One card per external tool with its quarantine verdict (admitted, admitted-escorted, deferred, held-conditional, or rejected). The shelf lists; it never loads. No ledger, no change. loci-cli/: a terminal-native CLI for reading the palace. Five commands (status,crystals,read,handover,init), all read-only. No network, no inference, no daemons. Install withcargo install --path loci-cli.templates/personas/: a shelf of four filled persona examples: an orchestrator (the one you are meant to rename), a security and sysadmin dyad, and a design persona.templates/skills/: three portable disciplines with stated triggers, procedures, and kill conditions: quarantine, session close, and insight consolidation.templates/eval-framework.md: a two-phase growth instrument. A Foundation Scorecard (12 axes, 0 to 5, lock at ceiling), a Growth Scorecard (G1 to G7, 1 to 10, no ceiling), and a Frontier Section.- Memory lifecycle doctrine: the crystal and garden lifecycle named as one doctrine (keep what surprised you, let the rest decay on its tier's own clock, keep all of it inspectable). Ships as
templates/memory-lifecycle.mdplus the methodology update. - Palace audit, 6th dimension: "Tracker integrity" walks
tracker.jsonfor broken references, stale versions, and unreferenced drafts. Read-only. Total score moves to /30. templates/.lociignore: scopes the audit scan so vendored trees do not swamp it.- Two operating rules in
CLAUDE-master.md: confirm against disk before asserting state or absence, and quarantine foreign processes. docs/RELEASING.md: how a change ships. Ordered release gates, version-anchor semantics, tagging rules, and a rollback table.
Changed
- Palace detection accepts two layouts. Both the desktop app and the CLI now load the original rooms-inside-
_palace/shape and the rooms-at-root shape. Palaces ported from older organic layouts load directly. - The job table has one owner. When a palace ships instrument tabs, the native dashboard keeps the KPI header and the automation instrument owns the cron list. Palaces without instruments keep the native table as fallback.
v0.1.0-beta.1 (2026-06-09)
First public beta of the template kit and the CLI line.
Added
- Plain-markdown palace setup via the
templates/kit. No build required. FIRST-SESSION.mdandAGENT-SETUP.mdguided onboarding.SETUP-GUIDE.mdfull walkthrough.ARCHITECTURE.mdsystem overview and design rationale.PALACE-METHODOLOGY.mdprotocol reference (the check-for-updates anchor).PALACE-UPDATE.mdupdate protocol.packages/core, the core Node.js package.discoveries/community findings folder.CONTRIBUTING.mdcontribution guide.
Notes
- At this point desktop (Tauri) releases were tagged separately under
desktop/vX.Y.Z. The v0.6.0-beta release unified them onto one version line. - The markdown-only path was stable from day one; the CLI surface was still in active development.
Versioning
Two version lines, on purpose:
- Product releases (templates, desktop app, CLI) follow a beta line:
v0.1.0-beta.1,v0.6.0-beta. Since v0.6.0-beta all three run modes ship together on one version. - The methodology (
loci-core) carries its own version anchor insidePALACE-METHODOLOGY.md, currently 1.6-candidate. The update protocol reads this anchor to build the delta between your palace and the published methodology.