Multi-Source Local Knowledge Base Integration

[goforu]

[RFC] Multi-corpus workspace for fragmented local knowledge bases

Background:
Users typically have knowledge scattered across multiple local folders:

• ~/projects/backend/ - Codebase A
• ~/projects/frontend/ - Codebase B
• ~/papers/research/ - Academic papers
• ~/notes/meetings/ - Meeting notes & screenshots

Currently, Graphify processes one folder at a time, producing isolated graphs. Users need a way to query across all these local sources as a unified knowledge base.

Proposed Solution: Workspace Mode

# Initialize workspace
graphify workspace init

# Add local corpora to workspace
graphify workspace add ./backend --name "backend-api"
graphify workspace add ./frontend --name "frontend-app"
graphify workspace add ~/papers --name "research"
graphify workspace add ~/notes --name "meeting-notes"

# List all corpora
graphify workspace list
# → backend-api (last synced: 2h ago)
# → frontend-app (last synced: 1d ago)
# → research (last synced: 5m ago)
# → meeting-notes (last synced: 3h ago)

# Query across all corpora
graphify query "authentication implementation" --workspace

# Query specific corpus
graphify query "React hooks" --corpus "frontend-app"

# Find cross-corpus connections
graphify connect "JWT" --from "backend-api" --to "research"
# → Found: JWT implementation in backend-api ↔ JWT paper in research

Use Cases:

• Full-stack developers with separate frontend/backend repos
• Researchers with code + papers + notes
• Teams with multiple microservices codebases
• Personal knowledge management across projects

[tuanquynet]

It's very helpful feature.

[tuanquynet]

Can you support ignored files as well.