docs: describe the release workflow now that it is merged
The architecture guide, AGENTS.md and the threat model said releases were built by hand or Windows-first; ADR-0009 still listed the release workflow as future work. The Windows build guide named the missing Settings > API Keys tab.
This commit is contained in:
@@ -1,9 +1,9 @@
|
||||
# Waggle OS — Threat Model
|
||||
|
||||
Waggle OS is a **workspace-native AI agent platform with persistent memory**. The current
|
||||
launch scope is a Windows-first Tauri desktop binary with a bundled Node.js sidecar;
|
||||
macOS packaging and certification remain roadmap work. This document states the trust
|
||||
boundary and the controls that enforce it.
|
||||
Waggle OS is a **workspace-native AI agent platform with persistent memory**. The community
|
||||
edition ships a Tauri desktop app for Windows, macOS and Linux and a headless server
|
||||
installer, both running the same Node.js sidecar on a bundled Node runtime. This document
|
||||
states the trust boundary and the controls that enforce it.
|
||||
|
||||
> Status: living document. The controls below are implemented and cited to source.
|
||||
> Known gaps are open and honestly listed.
|
||||
|
||||
Reference in New Issue
Block a user