docs: clarify deployment strategy (beads local, tissue remote)
Local (skills, dotfiles): beads + our dual-publish Remote (ops-jrz1 VPS): tissue + emes ecosystem They coexist by environment, not replacing each other. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
dan
parent
8a76f4e9cb
commit
a198b31add
|
|
@ -18,6 +18,7 @@
|
|||
{"id":"skills-4yn","title":"Decide on screenshot-latest skill deployment","description":"DEPLOYED.md shows screenshot-latest as 'Not yet deployed - Pending decision'. Low risk skill that finds existing files. Need to decide whether to deploy or archive.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-11-30T11:58:33.099790809-08:00","updated_at":"2025-12-28T20:55:18.515543619-05:00","closed_at":"2025-12-28T20:55:18.515543619-05:00","close_reason":"Decided to deploy - low risk, useful for avoiding path typing. Added to dotfiles claude.nix."}
|
||||
{"id":"skills-53k","title":"Design graph-based doc discovery","description":"How does doc-review find and traverse documentation?\n\nApproach: Start from README.md or AGENTS.md, graph out from there.\n\nDesign questions:\n- Parse markdown links to find related docs?\n- Follow only relative links or also section references?\n- How to handle circular references?\n- Depth limit or exhaustive traversal?\n- What about orphan docs not linked from root?\n- How to represent the graph for chunking decisions?\n\nConsiderations:\n- Large repos may have hundreds of markdown files\n- Not all .md files are \"documentation\" (changelogs, templates, etc.)\n- Some docs are generated and shouldn't be patched\n\nDeliverable: Algorithm/pseudocode for doc discovery + chunking strategy.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-04T14:02:13.316843518-08:00","updated_at":"2025-12-04T16:43:58.277061015-08:00","closed_at":"2025-12-04T16:43:58.277061015-08:00"}
|
||||
{"id":"skills-5hb","title":"spec-review: Add Prerequisites section documenting dependencies","description":"SKILL.md and process docs assume orch is installed, prompt files exist, models are available, but none of this is documented.\n\nAdd:\n- orch install instructions/link\n- Required env vars and model availability\n- Prompt file locations\n- Expected repo structure (specs/ convention)\n- Troubleshooting section for common failures","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-15T00:23:23.030537501-08:00","updated_at":"2025-12-15T01:12:36.457092612-08:00","closed_at":"2025-12-15T01:12:36.457092612-08:00"}
|
||||
{"id":"skills-5kv","title":"Document beads vs tissue split during emes testing","description":"During emes testing on ops-jrz1:\n- Local dev: beads (skills repo, dotfiles, etc.)\n- ops-jrz1: tissue (emes ecosystem testing)\n\nNeed to document:\n- Which tracker for which repos\n- How to context-switch mentally\n- Whether to bridge or keep separate\n- Exit criteria: when do we converge?","status":"open","priority":3,"issue_type":"task","created_at":"2026-01-09T16:03:45.493255636-08:00","created_by":"dan","updated_at":"2026-01-09T16:03:45.493255636-08:00"}
|
||||
{"id":"skills-5tq","title":"LSP diagnostic harvest → auto-create beads","description":"Periodic/nightly headless LSP scan that:\n- Gathers diagnostics (unused vars, type errors, deprecations, lint warnings)\n- Groups by subsystem/module\n- Auto-creates beads with severity thresholds\n- Enables 'refactor quests' - parent bead with children per symbol\n\nRun via CI or cron, feed results back into beads automatically.","status":"open","priority":3,"issue_type":"feature","created_at":"2025-12-24T02:29:56.191762416-05:00","updated_at":"2025-12-24T02:29:56.191762416-05:00","dependencies":[{"issue_id":"skills-5tq","depends_on_id":"skills-gga","type":"blocks","created_at":"2025-12-24T02:30:06.471853411-05:00","created_by":"daemon"}]}
|
||||
{"id":"skills-5v8","title":"Replace SKILL.md with upstream version","description":"Upstream has 644 lines vs our 122. Missing: self-test questions, notes quality checks, token checkpointing, database selection, field usage table, lifecycle workflow, common patterns, troubleshooting","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-03T20:15:53.025829293-08:00","updated_at":"2025-12-03T20:16:20.470185004-08:00","closed_at":"2025-12-03T20:16:20.470185004-08:00","dependencies":[{"issue_id":"skills-5v8","depends_on_id":"skills-ebh","type":"discovered-from","created_at":"2025-12-03T20:15:53.027601712-08:00","created_by":"daemon","metadata":"{}"}]}
|
||||
{"id":"skills-5vg","title":"spec-review: Add context/assumptions step to prompts","description":"Reviews can become speculative without establishing context first.\n\nAdd to prompts:\n- List assumptions being made\n- Distinguish: missing from doc vs implied vs out of scope\n- Ask clarifying questions if critical context missing","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-15T00:23:25.681448596-08:00","updated_at":"2025-12-15T14:06:15.415750911-08:00","closed_at":"2025-12-15T14:06:15.415750911-08:00"}
|
||||
|
|
|
|||
|
|
@ -103,6 +103,15 @@ The repo root has:
|
|||
- **CI validation**: Check files are identical
|
||||
- **Documentation**: `docs/emes-conversion-guide.md`
|
||||
|
||||
## Deployment Environments
|
||||
|
||||
| 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.
|
||||
|
||||
## Related
|
||||
|
||||
- **skills-6x1**: Epic for emes plugin architecture
|
||||
|
|
|
|||
|
|
@ -119,12 +119,22 @@ skills/my-skill/
|
|||
|
||||
**Rationale:** Cross-agent support is important. Gemini can't use Claude plugins (skills-bo8).
|
||||
|
||||
## 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 |
|
||||
|
||||
We use beads locally, tissue on the remote server. Not replacing one with the other - they coexist by environment.
|
||||
|
||||
## Open Questions
|
||||
|
||||
1. Should we adopt tissue or stick with beads?
|
||||
1. ~~Should we adopt tissue or stick with beads?~~ → Both, by environment
|
||||
2. How much of emes philosophy (mechanical enforcement) should we adopt?
|
||||
3. Can we make lenses work as Claude plugin hooks?
|
||||
4. Should skills output JSON for machine consumption?
|
||||
5. How do beads and tissue sync/interop? (or do they?)
|
||||
|
||||
## References
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue