Shelvia
ConceptAvailable

Project Memory

Project memory is not a vector dump. It is structured rows that humans approve and tools retrieve, decisions, sources, prompts, next steps, open questions, and constraints, each with provenance.

INPUTSAI chatsFilesLinksPromptsNotesReview queueHumans approveProject memoryDecisions · sources · promptsAPI/MCP

The memory rows

  • Decisions, durable, source-linked, reversibility tracked.
  • Sources, URL + canonical URL + source-type + extraction excerpt.
  • Prompts, saved with best-tool routing.
  • Next steps + open questions + constraints, string arrays under project_memory.

Workspace scope is enforced

Every read is workspace-scoped at every layer. Cross-workspace retrieval is impossible by query construction.

Provenance on every read

Every API and MCP response carries provenance, workspace_id, token_id, project_ids, api_version, generated_at. Downstream tools can verify the source of every claim without parsing the body.

For runnable code samples and the developer reference, see /developers. For the trust model in depth, see /security.