dan/skills
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

docs: clarify VPS deployment goal for skills

Browse source 
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
dan 2026-01-11 21:24:13 -08:00
parent b13109e8e0
commit 7c7733bc64
2 changed files with 24 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
docs/adr/005-dual-publish-plugin-architecture.md
View file

@ -105,12 +105,21 @@ The repo root has:
## Deployment Environments ## Deployment Environments
**Current:**
| Environment | Issue Tracker | Plugin System | | Environment | Issue Tracker | Plugin System |
|-------------|---------------|---------------| |-------------|---------------|---------------|
| **Local** (skills, dotfiles) | beads | Our dual-publish | | **Local** (skills, dotfiles) | beads | Our dual-publish |
| **Remote** (ops-jrz1 VPS) | tissue | emes ecosystem | | **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 ## Related

19
docs/research/plugin-systems-comparison.md
View file

@ -121,12 +121,21 @@ skills/my-skill/
## Deployment Strategy ## Deployment Strategy
| Environment | Issue Tracker | Plugins | Notes | **Current state:**
|-------------|---------------|---------|-------|
| **Local** (skills, dotfiles) | beads | Our dual-publish | Familiar, cross-agent |
| **Remote** (ops-jrz1 VPS) | tissue | emes ecosystem | First deployment target |
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 ## Open Questions