contextvault-daemon
v0.1.0
Published
Context Vault daemon — graph filesystem + REST API over content-addressed artifacts.
Downloads
167
Readme
RCOM + ContextSync Unified Daemon (prototype)
One local daemon that speaks two interfaces simultaneously:
- FUSE mount — apps and humans see a normal filesystem
- ContextSync HTTP + SSE — peer daemons and external clients speak the v0.3 protocol
Over one unified store — same blobs, same version DAG, same permission table, same provenance log.
Design drafts
- Protocol addition (typed edges as 6th primitive):
../drafts/spec_edges_addition.md - Revised architecture section (unified daemon):
../drafts/newprd_section2_revised.md
Layout
src/
index.ts entry point
server.ts express app wiring
db.ts SQLite schema + open
format.ts YAML front-matter serialization (port of filesystem.py)
retrieval.ts substring + stopwords + prefix + graph-boost (port)
types.ts URI, artifact, edge, actor types
routes/
artifacts.ts §2 artifact lifecycle
actors.ts §3 actor model
permissions.ts §4 permission model
subscriptions.ts §5 change subscriptions (SSE)
provenance.ts §6 provenance
edges.ts §6 draft: typed edges
fuse/ (phase 2 — not yet wired)Status
Scaffold. Only /health and the /artifacts create/read path are wired. Everything else is stubbed to return 501 Not Implemented.
Next milestone: two daemons, one file written via FUSE on A appears under FUSE mount on B via SSE.
Run
npm install
npm run dev # http://localhost:7777
curl -s localhost:7777/health