d1f69bfd37
Some checks failed
ci/woodpecker/push/ci Pipeline failed
Ratification draft (Jason, 2026-07-09) extending NORTH_STAR.yaml with NS-10..NS-13 and workstreams J/K/W/P/Q/X. Written against origin/main's fleet suite (F4/F6 anchors, H2 profiles, native backlog per ASM-1). Homelab is the trial environment (D12); USC/web1 adopts post-trial. See proposals/mosaic-platform-prd/README.md for the full decision record D1-D12. Not yet merged into NORTH_STAR.yaml — landing and card decomposition are the homelab orchestrator's mission. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Mosaic Platform PRD — Jarvis HMI + Hermes Decommission (DRAFT for ratification)
Date: 2026-07-09 · Author: proto-Jarvis session with Jason · Status: DRAFT — awaiting Jason ratification
Target home: mosaicstack/stack → docs/fleet/ (NORTH_STAR.yaml additions + per-phase PRDs)
Execution: hand to the homelab orchestrator as orchestrated missions once ratified (D12). Land in docs/fleet/ from origin/main — the /src/mosaic-stack clone on web1 is 5 months stale and must not be the base. The USC/web1 environment is out of scope for the trial; its cutover (workstream X applied to web1's Hermes + mos-claude) is a post-trial phase.
Ratified decisions (Jason, 2026-07-09)
| # | Decision |
|---|---|
| D1 | Jarvis conversation channel is Matrix-first — no #jarvis Discord channel is ever created. |
| D2 | Mosaic absorbs all four Hermes functions before decommission: messaging bridge, Kanban/task board, permission relay, multi-platform reach. |
| D3 | Task handoff: native Mosaic Backlog is the record; Gitea/GitHub/local-kanban attach as bidirectional sync adapters (upholds ASM-1). |
| D4 | Jarvis executes PA ops directly (email, calendar, tasks, knowledge, tickets, research); all code/infra/fleet work is delegated to Mos via the backlog. |
| D5 | Mosaic Stack is a product from day one — multi-user, Authentik tenancy, per-workspace isolation. |
| D6 | Multi-platform reach via Matrix + mautrix bridges (telegram/signal/whatsapp/slack/discord); agents only ever speak Matrix. |
| D7 | webUI builds on the existing mosaicstack/stack monorepo (apps/web), realizing the already-scoped F6 phase. |
| D8 | PRD first, then Mos runs it as orchestrated missions. |
| D9 | jarvis-brain flat-file data migrates into the product as tenant #1 (workspace = Jason); brain.py/flat files retire after cutover. |
| D10 | PRD form: extend NORTH_STAR.yaml + per-phase docs in docs/fleet/ (NS-1 compliant). |
| D11 | Jarvis runs Opus; Fable stays exclusive to Mos per the standing cost directive. Model tier is a persona/profile field. |
| D12 | Trial in the homelab (the proper mosaic-fleet deployment, built by the homelab agents from origin/main), NOT at USC. The USC/web1 environment runs the primitive-era implementation (mos-claude.service, Hermes, jarvis-brain boards) and adopts only after the homelab trial validates. Jason relays this PRD to the homelab agent for implementation. |
Artifacts in this draft
| File | Content |
|---|---|
north-star-additions.yaml |
Proposed NORTH_STAR.yaml merge: NS-10…NS-13, workstreams J/K/W/P/Q/X, goal cards with DAG |
PRD-jarvis-main-agent.md |
Workstream J — the HMI main agent |
PRD-permission-relay.md |
Workstream P — human-in-the-loop approvals |
PRD-webui-fleet-control.md |
Workstream W — tmux pop-in + top-down view (realizes F6) |
PRD-backlog-providers.md |
Workstream Q — provider sync adapters |
PRD-hermes-decommission.md |
Workstream X — parity checklist, tenant-1 migration, cutover |
Workstream K (Matrix connector + mautrix bridges) intentionally has no new PRD doc: it extends the existing docs/fleet/f4-matrix-connector.md; its deltas are captured as K-goals in the YAML additions and referenced from the J/P/X PRDs.
Relationship to existing upstream work
- Fleet CLI, persona library, system-type profiles (H1–H4), supervisor/dispatch (B), native backlog (A): already exist or in flight upstream — not re-specified here.
f4-matrix-connector.md: K1 = its Phase 2 implementation; K2 (mautrix bridges) is additive infra.- F6 (webUI hooks) in
PRD-fleet-suite.md: realized by workstream W. docs/3-architecture/guard-rails-capability-permissions.md(old snapshot): design source for workstream P.