From 7c7733bc645374ec1cf3095eee382e0061fdfd91 Mon Sep 17 00:00:00 2001 From: dan Date: Sun, 11 Jan 2026 21:24:13 -0800 Subject: [PATCH] docs: clarify VPS deployment goal for skills Co-Authored-By: Claude Opus 4.5 --- .../005-dual-publish-plugin-architecture.md | 11 ++++++++++- docs/research/plugin-systems-comparison.md | 19 ++++++++++++++----- 2 files changed, 24 insertions(+), 6 deletions(-) diff --git a/docs/adr/005-dual-publish-plugin-architecture.md b/docs/adr/005-dual-publish-plugin-architecture.md index 546a6f1..a4535e6 100644 --- a/docs/adr/005-dual-publish-plugin-architecture.md +++ b/docs/adr/005-dual-publish-plugin-architecture.md @@ -105,12 +105,21 @@ The repo root has: ## Deployment Environments +**Current:** + | Environment | Issue Tracker | Plugin System | |-------------|---------------|---------------| | **Local** (skills, dotfiles) | beads | Our dual-publish | | **Remote** (ops-jrz1 VPS) | tissue | emes ecosystem | -We use beads locally, tissue on the remote. They coexist by environment. +**Goal:** Deploy our cross-agent skills to ops-jrz1: + +| Environment | Issue Tracker | Plugin System | Agents | +|-------------|---------------|---------------|--------| +| **Local** | beads | Our dual-publish | Claude, Gemini, OpenCode | +| **Remote** (ops-jrz1) | tissue | **Our dual-publish** | Claude, Gemini, OpenCode | + +The VPS becomes a "skills for all agents" environment - same cross-agent portability we have locally. tissue handles issue tracking, skills are ours. ## Related diff --git a/docs/research/plugin-systems-comparison.md b/docs/research/plugin-systems-comparison.md index 312ac76..a56ae10 100644 --- a/docs/research/plugin-systems-comparison.md +++ b/docs/research/plugin-systems-comparison.md @@ -121,12 +121,21 @@ skills/my-skill/ ## Deployment Strategy -| Environment | Issue Tracker | Plugins | Notes | -|-------------|---------------|---------|-------| -| **Local** (skills, dotfiles) | beads | Our dual-publish | Familiar, cross-agent | -| **Remote** (ops-jrz1 VPS) | tissue | emes ecosystem | First deployment target | +**Current state:** -We use beads locally, tissue on the remote server. Not replacing one with the other - they coexist by environment. +| Environment | Issue Tracker | Plugins | +|-------------|---------------|---------| +| **Local** (skills, dotfiles) | beads | Our dual-publish | +| **Remote** (ops-jrz1 VPS) | tissue | emes ecosystem | + +**Goal:** Deploy our cross-agent skills to ops-jrz1. + +| Environment | Issue Tracker | Plugins | Agents | +|-------------|---------------|---------|--------| +| **Local** | beads | Our dual-publish | Claude, Gemini, OpenCode | +| **Remote** (ops-jrz1) | tissue | **Our dual-publish** | Claude, Gemini, OpenCode | + +The VPS should support "skills for all agents" - same cross-agent portability we have locally. tissue handles issue tracking there, but skills are ours. ## Open Questions