6b8c3c5d3a
All checks were successful
ci/woodpecker/push/ci Pipeline was successful
Post-review refinements to the DRAFT PRD set (decisions D1–D12 unchanged): - R1: PRD-permission-relay is now self-contained — its cited design source (guard-rails-capability-permissions.md) is absent from origin/main, so the essential model (prepare-freely/execute-with-approval, permission levels, resource:action grants) is folded in as the authoritative spec. - R2: Phase-1 conversation channel is tmux/CLI via the f4 Phase-1 tmux connector (operator issues /remote-control); Matrix room (J5/K1) is Phase 2. - R3: Jarvis is a Level-0 orchestrator (delegation + subagents, never executes coding/infra); AC-NS-8 latency isolation is a separate-model-capacity guarantee, not just a separate process (NS-10, AC-NS-8, ASM-5). - R4: jarvis-brain reframed as the P0 (prototype) Mosaic Stack; tenant-1 migration targets the proper stack storage layer (vector DB + enhanced memory + flat-file backends). Agent memory/runbooks migrate live into the memory subsystem and are NOT frozen; repo retires read-only only after both PA data and agent memory are verified migrated (X2/X-R7). - R5: homelab→USC promotion is an explicit owner sign-off gate, not an automated metric (X deployment-scope). - R6: verified K1 is covered by f4-matrix-connector.md Phase 2 (no new doc). - R7: clarified always-available Opus ≠ standing cost (idle = no bill) (J-R2). - Also normalized PRD-backlog-providers.md and PRD-webui-fleet-control.md with prettier (whitespace-only) — they were non-conformant as originally pushed and would have re-broken repo-wide format:check on merge. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RMoEx7hfdFGjUiCHuN1RRi
Mosaic Platform PRD — Jarvis HMI + Hermes Decommission (DRAFT for ratification)
Date: 2026-07-09 · Author: proto-Jarvis session with Jason · Status: Decisions D1–D12 ratified (fixed inputs); implementing PRD structure DRAFT — refined 2026-07-09 post-review
Target home: mosaicstack/stack → docs/fleet/ (NORTH_STAR.yaml additions + per-phase PRDs)
For the homelab orchestrator: D1–D12 below are settled constraints, not open questions — do not reopen them. What is under review is only the implementation (workstreams, goals, sequencing) that realizes them. Execution: hand to the homelab orchestrator as orchestrated missions once ratified (D12). Land in
docs/fleet/fromorigin/main— the/src/mosaic-stackclone 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 (verified present onorigin/main; Phase 1 already ships the tmux-default connector that serves the P1 CLI channel per J-R14a). K2 (mautrix bridges) is additive infra.- F6 (webUI hooks) in
PRD-fleet-suite.md: realized by workstream W (verified present onorigin/main). docs/3-architecture/guard-rails-capability-permissions.md: original design snapshot for workstream P — not present onorigin/main(lives only in the stale/src/mosaic-stackclone). Its essential model is therefore folded intoPRD-permission-relay.md, which is now the self-contained authoritative spec for P; the old path is cited as historical origin only.