Changelog

Weekly changelog for Artemis City covering new features, integrations, dashboard updates, governance changes, and bug fixes across the platform.

​

May 21, 2026

Release

Weekly update

What shipped

New features

• Environment branching (dev / staging / prod). Three long-lived environment branches now map 1:1 to GitHub Environments and deploy targets, with per-environment YAML under config/environments/ and an ARTEMIS_ENV-keyed Python loader. CI validates all three configs on every push, deploy.yml routes pushes to the matching GitHub Environment, and a manual Promote workflow opens draft dev → staging and staging → prod PRs. Setup steps and the secrets model are documented in Environments.

​

May 16, 2026

Release

Weekly update

What shipped

New features

• Web dashboard UI. A new browser-based dashboard lands with dedicated views for Agents, Tasks, an Executor, Reports, and a Database explorer. Operators can now monitor and drive runs without leaving the browser. See the API reference for the endpoints powering each view.
• Versioned v1 web API. Agents, ATP, memory, trust, LLM, and health endpoints are now grouped under a stable /v1 namespace with auth and logging middleware, so integrations can target a versioned surface instead of unversioned routes. Full schema in the API reference.
• Agent Translator Protocol (ATP). First-class ATP support ships with a parser, validator, and shared models, giving agents a structured way to negotiate task envelopes and translation boundaries across the city. Background in the Translator Protocol guide.
• Artemis CLI. A command-line interface is now available for driving the orchestrator from a terminal, alongside an agent_router configuration for declarative routing setups.
• Postal service & trust interface. A new postal service handles inter-agent message delivery, and a dedicated trust interface exposes scoring, validation, and credentialed-reviewer signals to clients. See Trust scoring.

Updates

• Memory client with decay. A reusable memory client now talks to the hybrid memory bus on behalf of agents and applies decay so stale entries fall out of routing automatically. See Hybrid memory bus and Hebbian learning.
• Vector store seeding. A seeding workflow is available for bootstrapping the vector store on a fresh deployment, so new environments start with a usable corpus instead of an empty index.
• Containerized deploys. A separate Docker dependency set is now maintained alongside the standard install, keeping self-hosted images lean.
• Health checks. A built-in health check surfaces orchestrator, memory bus, and API status in one call for uptime monitoring and load balancers.
• Refreshed architecture docs. Architecture, Living City, Memory bus, and API reference have been updated to reflect the new dashboard, v1 API, and ATP surfaces.

Bug fixes

• API reference grammar. Minor copy fixes in the API reference for clearer endpoint descriptions.

​

May 15, 2026

Release

Weekly update

What shipped

New features

• Whitepaper v3 release. Artemis City v3 introduces the Domain-Locked Hebbian Marketplace, replacing the v2 binary weight rule with a continuous morphological learning formula (ΔW = tanh(a · x · y)). In simulation, the new routing outperforms unconstrained routing by 81.2% and runs at 180× lower compute cost than k-NN lookup. Read the full v3 whitepaper.
• Active Sentinel & Immune System. The sentinel layer now actively reroutes traffic when it detects routing oscillation in a domain, instead of just raising passive alerts. Interventions concentrate automatically in volatile domains, so stable workflows are left untouched. See Trust scoring and Metrics.
• Hebbian + k-NN reconciliation layer. Hebbian routing now acts as a cheap O(1) elimination layer that defers to k-NN verification only on disagreement. Reconciled decisions run at 71.9% of pure k-NN cost while improving accuracy — useful for high-stakes domains that need an auditable decision trail. Details in the routing modes reference.

Updates

• Distributed weight resilience. Corpus corruption is now contained to a single agent instead of propagating system-wide. The routing graph automatically deselects poisoned agents within a few tasks. See Hebbian learning.
• Missing-flow detection. When a new task type appears that no agent has been trained on, the system surfaces a clear 7.2× failure-rate spike that triggers a kernel-level expansion workflow rather than silent degradation. See the AOS kernel reference.
• Faster failure recovery. Hebbian agents now recover from failure events in 4–5 steps versus 17–24 for monolithic baselines, a 4–5× improvement in adaptation speed.
• Human validators as weighted reviewers. Credentialed human reviews now carry more weight than hobbyist feedback in agent scoring, with validated reviews exposed as a tradeable signal inside the marketplace. See Trust scoring.
• Memory bus SLOs published. Documented write latency under 200 ms p95 (500 ms p99), read latency under 50 ms p95 for cache hits, and sync lag under 300 ms between the Obsidian vault and Supabase index. See Hybrid memory bus.

​

May 5, 2026

Release

Weekly update

What shipped

New features

• Hugging Face integration. Artemis City agents can now reach Hugging Face models through the orchestrator. This expands the catalog of models available to agents without custom adapter work. See Translator Protocol for how agents negotiate model and encoding boundaries.
• Vault-backed task and agent endpoints. The dashboard API can now list tasks directly from your Obsidian vault and read the agent registry from local storage, so the dashboard stays useful even when the orchestrator is offline. See the API reference for endpoint details.

Updates

• Docker install path. A dedicated dependency set is now available for containerized deployments, simplifying setup for self-hosted environments.
• Dashboard performance. Web dashboard build tooling was upgraded for faster page loads and improved browser compatibility.
• Architecture documentation. Refreshed system diagrams and the Living City reference to reflect current routing and orchestration behavior.

Bug fixes

• Agent listing resilience. Listing registered agents no longer fails when the orchestrator hasn’t initialized; results are read from the agent registry directly.
• Task parsing. Task notes with frontmatter and inline metadata are parsed more reliably, including subtask checkboxes.