User-approved promotions from the prior compile's proposal list. pbs-hub-mcp deferred per user. Wiki domain indexes updated to list the new entities; Sources left untouched (MCP-written/immutable). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2.8 KiB
2.8 KiB
| type | path | tags | created | updated | |||
|---|---|---|---|---|---|---|---|
| entity | Wiki/Reference |
|
2026-05-24 | 2026-05-24 |
Trellis
What it is
Trellis is an MCP server that captures and resumes long-running threads of work across conversation boundaries. The unit is a thread — a logical work effort that may span many chat sessions over days or weeks, with pause/resume verbs so context can be switched without losing working state. It solves the "where exactly did we leave the Traefik debugging" problem that memory is too lossy for and chat history can't restore. Trellis is the record leg of the three-way memory split: CLAUDE.md is instructions, Trellis is where-we-are-in-the-doing, and the Wiki/Dev/ai-memory-architecture hold lessons and outcomes.
Current state
Operational, Postgres-backed in the consolidated petalbrain instance (schema trellis, owned by the trellis_mcp role). Shape:
- Four tables, append-only events log:
threads,tags,thread_tags,events. Checkpoint payload is freeform markdown the agent synthesizes. - Seven tools (
*_thread):start,checkpoint(waspause),resume,get,list,fork,update. - Lifecycle is prompt-driven — no autonomous jobs, no auto-abandon. Threads persist until explicitly acted on.
- A Sources/Homelab/trellis-mcp-tool-surface-followups is in flight:
pause_thread→checkpoint_threadrename (the verb writes acheckpointevent, not a status change, and collided with thepausedstatus), plus optional integeridaddressing alongside the canonicalslug.
Where it lives
trellis-mcpcontainer; same deployment pattern as vault-mcp (FastMCP, Authentik in front, Cloudflare Tunnel), hostnametrellis.herbylab.dev- Data:
petalbrain.trellisschema on thehomelab-postgrespgvector:pg17 container - Local repo:
/opt/projects/homelab/trellis-mcp/
Related projects
- Sources/Homelab/trellis-mcp — design + build plan
- Sources/Homelab/trellis-mcp-tool-surface-followups — checkpoint rename + id addressing
- Sources/Homelab/postgres-consolidation-ob1-reflection-layer — trellis cutover into petalbrain
- Wiki/Reference/vault-mcp — sibling MCP, same deployment pattern
- Wiki/Dev/ai-memory-architecture — synthesis (Trellis = the "record" leg)
History
- 2026-05-10 — Design locked: thread model, four-table append-only schema, seven-tool surface, prompt-driven lifecycle
- 2026-05 — Consolidated into
petalbrain.trellis(trellis cutover, Phase 2/3 of the consolidation) - 2026-05-23 — Tool-surface follow-ups planned:
checkpoint_threadrename +idaddressing