AgenticNetOS 2.43.0

The governed-autonomy release: Agentic-Nets positions as a domain-general backend for designing, operating, observing, and continuously improving governed autonomous processes. Two shipped packages carry the story — a Safe Product Team worked example and a domain-neutral Model Steward whose authority is enforced by capability profile, not prompt hope.

Added

• Safe Product Team is now a complete MCP/Desktop worked example. MCP adds the start-safe-product-team playbook and agenticnets://docs/safe-product-team; the token-free dev-team template now includes repository/product context, decisions, reviewed lessons, structured status, and the Protocol place. The playbook stages a Product Manager, Architect, Developer, Reviewer, Release Guardian, and Chronicle around deterministic hand-offs, explicit repository policy, approval-gated external effects, and an evidence-backed smoke test without defining the product's domain boundary.
• Starter-pattern catalog and provider-free CLI reviewer. MCP now teaches a library of composable concept starters instead of treating one team as the universal entry point. The new headless-cli-reviewer template demonstrates safe MAP → CommandToken → COMMAND → durable result execution through read-only Claude Code or Codex on an executor; dynamic task text travels via environment data rather than shell interpolation.
• Agent Hub now ships Safe Product Team and Model Steward contracts. The versioned safe-product-team package is singleton per model so it writes to canonical p-protocol; it installs stopped with typed product/repository and approval schemas and reasoning-only authority. The domain-neutral model-steward package performs focused or scheduled evidence reviews of any model's nets/processes and can write only its review outputs and Protocol summaries. MCP adds review-current-model plus bundled Model Steward guidance, with an honest connected-client fallback when no server provider is configured.

Changed

• Desktop Lite documentation leads with persona teams and observability. The tray manual, Desktop operator guide, MCP README, and public README now teach the event trail (complete evidence), structured status (analysis), and Protocol (readable narrative) as the product loop; forums/chats are optional adapters rather than the team's source of truth. The same material explains MCP playbooks versus starter templates, versioned Agent/NetHub packages, context/tool-net packages, and the provider requirement of built-in runtime agents.

Fixed

• readiness no longer calls an unusable LLM provider READY (agentic-net-mcp). Provider health checks reachability and model presence, not usability: a cloud model outside the account's plan answers the model list fine and then rejects every inference on billing — a staging model ran 380 consecutive failures over a week while every diagnostic stayed green. When health reports READY, readiness now cross-checks the recent event line; if the last llm/agent fires all failed with zero successes, it reports llm.usable:false with the raw provider error, flips capabilities.llmLanes off, and lists a blocking problem naming the repair. For a product whose stated USP is honest observability, health-as-reachability was the one place the claim was untrue.
• Windows update no longer ends in silence (agentic-net-desktop — SelfUpdater). The tray update spawned a bare interactive msiexec /i from a process that had just quit: the wizard routinely opened behind other windows, so the user watched AgenticNetOS shut down and then saw nothing at all — and even when the install ran to completion, the script simply ended, relaunching nothing (field report from a 2.40.1 install). The installer now runs /passive (progress bar, no clicks) with a verbose log beside the downloaded msi, relaunches the app on success (including exit 3010, success-wants-reboot), and on failure opens the log in Notepad — a visible artifact instead of silence. The tray manual's troubleshooting table explains the older-version behavior and its recovery.

---

AgenticNetOS Desktop Lite

The fast local creator/operator profile: node, deterministic master, gateway,
executor, encrypted local credential vault (no OpenBao), MCP endpoint, and
Studio — supervised by a tray app on bundled Java/Node runtimes. No Docker,
host Java/Node installation, API key, or server-side LLM is required. Connect
an MCP client and let its model build, schedule, inspect, and execute nets.
This loopback-only profile is not the recommended production deployment.

macOS: open the .dmg, accept the license, drag AgenticNetOS to Applications.
First launch of this unsigned build: right-click the app and choose "Open", or allow
it under System Settings → Privacy & Security → "Open Anyway". Verify the download
against SHA256SUMS.txt first.

Linux (Debian/Ubuntu): sudo apt install ./AgenticNetOS-<version>-linux-<arch>.deb,
then run /opt/agenticnetos/bin/AgenticNetOS. An
.rpm is provided for Fedora/RHEL. On servers without a desktop the app runs headless;
the tray is optional.

Windows: run AgenticNetOS-<version>-windows-x64.msi (unsigned; SmartScreen may
warn on first run). Upgrades install over the old version in place; the upgrade path
is CI-tested against the previous published release. Data in ~/.agenticos is never
touched by the installer, including by a failed one.

Build it yourself: agentic-net-desktop/scripts/build.sh (or build-windows.ps1)
in the repository bundles an installer for your machine from this release's
standalone binaries (agentic-net-node-*.jar, agentic-net-master-*.jar,
agentic-net-gui-*.zip below — EULA applies), no Docker needed.

Connect an MCP client: the tray copies a ready Codex config.toml block,
Claude Code command, or generic MCP URL + bearer token. Studio: tray menu →
"Open Studio" signs you in automatically (a single-use link exchanges the admin
secret server-side; it never reaches the browser).
Server-run AI lanes can be enabled later, but fresh installs use
llm.provider=disabled, so new AI lanes default to MCP external fires and need
no server model.

Data lives in ~/.agenticos/ and survives updates. The bundled node, master and
gui binaries are covered by the EULA shown at install (also in the app dir);
everything else is BSL 1.1.