feat: add swarm-common obsidian vault
Add Obsidian vault to the swarm-common virtiofs share for access from zap VM and other VMs. Contains agent memory, notes, and infrastructure documentation. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
101
swarm-common/obsidian-vault/zap/memory/projects.md
Normal file
101
swarm-common/obsidian-vault/zap/memory/projects.md
Normal file
@@ -0,0 +1,101 @@
|
||||
# Projects
|
||||
|
||||
Lightweight registry of active multi-session work.
|
||||
|
||||
## Status legend
|
||||
- active
|
||||
- paused
|
||||
- blocked
|
||||
- done
|
||||
- watch
|
||||
|
||||
## Projects
|
||||
|
||||
### OpenClaw reliability and ops
|
||||
- Status: active
|
||||
- Goal: keep the local OpenClaw setup stable, safe, and low-friction for daily use
|
||||
- Current threads:
|
||||
- improve subagent / ACP reliability
|
||||
- maintain memory hygiene and retrieval quality
|
||||
- keep backups, search, and messaging paths healthy
|
||||
- Related memory:
|
||||
- `memory/incidents/`
|
||||
- `memory/ops/`
|
||||
- `memory/tasks.json`
|
||||
|
||||
### Daily brief / calendar direction
|
||||
- Status: watch
|
||||
- Goal: build a useful low-noise daily brief flow, likely calendar-first
|
||||
- Current state:
|
||||
- direction chosen on 2026-03-10
|
||||
- no calendar backend configured yet
|
||||
- next decision depends on which calendar backend Will actually uses
|
||||
- follow-up task added on 2026-03-11 to set up calendar access/backend
|
||||
- Related memory:
|
||||
- `memory/2026-03-10.md`
|
||||
- `memory/tasks.json`
|
||||
|
||||
### Local service expansion
|
||||
- Status: watch
|
||||
- Goal: gradually fill the most useful remaining LAN/local capability gaps without adding junk infra
|
||||
- Candidate additions:
|
||||
- calendar access/backend
|
||||
- email/inbox access
|
||||
- broader personal document/search corpus
|
||||
- more homelab observability/status endpoints
|
||||
- stronger GitHub tooling
|
||||
- Google Workspace access
|
||||
- local OCR / PDF extraction
|
||||
- notes-system connector
|
||||
- carefully scoped secret-manager integration
|
||||
- Home Assistant / smart-home integration
|
||||
- structured data connectors where useful
|
||||
- local code indexing
|
||||
- alert ingestion
|
||||
- local docs/manuals RAG
|
||||
- Related memory:
|
||||
- `memory/tasks.json`
|
||||
|
||||
### Workflow quality and trust improvements
|
||||
- Status: watch
|
||||
- Goal: improve signal routing, trust, repeatability, and operational quality as capabilities expand
|
||||
- Candidate additions:
|
||||
- meeting-prep / briefing pipeline
|
||||
- better notification routing
|
||||
- external action audit log
|
||||
- safer sandboxed execution helpers
|
||||
- package/update intelligence
|
||||
- lightweight decision log
|
||||
- standard operating playbooks
|
||||
- dependency / credential inventory
|
||||
- eval / regression harness
|
||||
- optional people-context layer
|
||||
- Related memory:
|
||||
- `memory/tasks.json`
|
||||
|
||||
## Current roadmap focus
|
||||
|
||||
### Now
|
||||
- subagent reliability
|
||||
- eval / regression harness
|
||||
- calendar access/backend
|
||||
- alert ingestion
|
||||
- standard operating playbooks
|
||||
|
||||
### Soon
|
||||
- email/inbox access
|
||||
- meeting-prep / briefing pipeline
|
||||
- notification routing
|
||||
- local docs/manuals RAG
|
||||
- broader personal doc search
|
||||
- local code indexing
|
||||
- external action audit log
|
||||
|
||||
### Later
|
||||
- broader integration and tooling expansion from `memory/tasks.json`
|
||||
- lower-priority workflow polish and optional context layers
|
||||
|
||||
## Notes
|
||||
- Use this file for cross-session project state humans may want to skim quickly.
|
||||
- Keep detailed steps/checklists in `memory/plans/`, `memory/tasks.json`, or `memory/roadmap.md`.
|
||||
- Don’t create a project entry for every tiny task; this is the bigger-picture map.
|
||||
Reference in New Issue
Block a user