Project memory concepts and developer references.
Shelvia turns scattered AI chats, files, sources, decisions, and prompts into reviewed project memory. Humans can search it. Tools and agents retrieve it through API, MCP, and SDK. This is the navigation hub. Pick a concept, a reference, or a planned surface below.
Get oriented
How project memory works
Reviewed decisions, sources, prompts, next steps, and constraints inside one workspace.
Read moreAI-generated, imported, and agent-proposed memory enters review before it becomes trusted. Human-approved project edits are audit logged.
Read moreRanked context for the next session. Source-backed and health-aware.
Read moreStale, conflicted, low-confidence, and missing-source memory surfaced with explicit verdicts.
Read moreGitHub, Notion, and Google Drive / Docs feed the review queue with cost guardrails.
Read moreHybrid keyword + vector search across approved memory, workspace-scoped at every layer.
Read moreDeterministic compression of older approved memory into durable project state.
Read moreUser-initiated capture from ChatGPT, Claude, Perplexity, Gemini, and NotebookLM, routed through review.
Read moreRecipes, candidate-write APIs, MCP tool exposure, SDK helper, and observability logging. Agent, API, and MCP writes enter review before becoming trusted memory.
Read moreBuild on Shelvia
Workspace tokens and OAuth 2.0 with PKCE.
Read moreRead memory, generate context packs, create review candidates, log continuations.
Read moreModel Context Protocol endpoint that honors the same review-before-save contract as REST.
Read moreTyped client wrapping projects, search, candidates, context packs, summaries, and webhooks.
Read moreSigned outbound delivery on candidate creation, context-pack generation, and handoffs.
Read moreVerification gates
What changed
For runnable code examples, go to /developers. For the trust model in depth, see /security.