mosaicstack/stack
1
0
Fork 0
Code Issues 31 Pull Requests Actions Packages Projects Releases 15 Wiki Activity

docs(fleet): consolidate north-star doctrine (budget + control plane + identity) #629

Merged
jason.woltje merged 2 commits from feat/north-star-doctrine into main 2026-06-22 21:08:42 +00:00
Conversation 0 Commits 2 Files Changed 3 +8 -6
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 9cb0f33696 - Show all commits

14
docs/fleet/north-star.md
View File

@@ -67,9 +67,10 @@ One **definition** is the source of truth; the **session** is how it runs.
| **Budget / spend governance** | **per-tenant budget policy** ingested by the orchestrator + routing layer | none today (spend is unmetered) | usage-vs-limit feedback ingested; spend auto-paced to the limit window; per-provider/per-account/concurrency/API-$ budgets enforced | | **Budget / spend governance** | **per-tenant budget policy** ingested by the orchestrator + routing layer | none today (spend is unmetered) | usage-vs-limit feedback ingested; spend auto-paced to the limit window; per-provider/per-account/concurrency/API-$ budgets enforced |
> **PoC socket hygiene:** the PoC fleet runs on the **default tmux socket** (no `-L`). > **PoC socket hygiene:** the PoC fleet runs on the **default tmux socket** (no `-L`).
> `mosaic-factory` is just a named socket for production isolation — not a product or > The named production-isolation socket is **`mosaic-fleet`** (matches the product brand);
> component — and an absent roster `socket_name` means the default socket everywhere > an absent roster `socket_name` means the default socket everywhere (spawn, `fleet ps`,
> (spawn, `fleet ps`, onboarding cheat-sheet). > onboarding cheat-sheet). The legacy dogfood canary still runs on the old `mosaic-factory`
> socket pending migration.
## Operating model (inherited, not reinvented) ## Operating model (inherited, not reinvented)
@@ -330,9 +331,10 @@ re-evaluate if isolation or write-volume demands it.
user-facing identity and CLI surface. **forge** is the Fleet's **internal** delivery/orchestration user-facing identity and CLI surface. **forge** is the Fleet's **internal** delivery/orchestration
engine (not a separate product); the control-plane **Postgres register is the Fleet's register**; engine (not a separate product); the control-plane **Postgres register is the Fleet's register**;
workers/runtime are the **Fleet substrate**. **"factory" is RETIRED as a product term** — it was workers/runtime are the **Fleet substrate**. **"factory" is RETIRED as a product term** — it was
only ever the software-factory concept (which forge implements) and the `mosaic-factory` tmux socket only ever the software-factory concept (which forge implements) and the old `mosaic-factory` tmux
name; `mosaic-factory` remains **just a socket name** (production isolation), not a product/component, socket name. The production-isolation socket is now **`mosaic-fleet`** (matches the product brand);
and may be renamed later. **Code stays layered** (forge + fleet + control-plane as internal layers); the legacy dogfood canary remains on the old `mosaic-factory` socket pending migration. **Code stays
layered** (forge + fleet + control-plane as internal layers);
only the **identity + CLI surface unify under Fleet.** only the **identity + CLI surface unify under Fleet.**
- **Role-based session naming (Jason, 2026-06-22):** agent tmux sessions are named by **role** - **Role-based session naming (Jason, 2026-06-22):** agent tmux sessions are named by **role**
(`orchestrator`, `enhancer`, `research`, `coder0-0`, …), not by persona. **Persona lives in (`orchestrator`, `enhancer`, `research`, `coder0-0`, …), not by persona. **Persona lives in